Feature request: public API to register custom dock panels in kimi web

Use case

We run kimi-code web (2.0.0) behind an authenticating reverse-proxy gate for a multi-reviewer evaluation chatroom (chatroom2IC). Reviewers chat with the compiled model and annotate each assistant reply with a structured label (aligned / misaligned / false_positive / template_wrong / partial / interim) to build an intent-compiler quality dataset.

Today we achieve this by injecting our own script (/panel.js) into the HTML served through the gate. It works, but the annotation UI is a floating overlay card, while the requirement — and natural UX — is a third panel docked inside kimi web's existing right-side dock (next to the built-in task/plan panels).

Problem

The dock (dockPanel state + dock-work-panel component in the web bundle) is an internal Vue structure with no public registration point. Injecting into it would require patching kimi internals, which breaks on every upgrade.

Request

A small public surface, e.g.:

// hypothetical
window.kimiWeb.panels.register({
  id: "chatroom2ic-ic-stats",
  title: "IC 统计",
  icon: "...",
  mount(el, context) { /* context: { sessionId, onSessionChange } */ },
});

context.sessionId / onSessionChange would let external panels follow the active session without DOM scraping — this is the only part of our integration that cannot be done robustly from outside.

Constraints we are trying to preserve

• kimi web stays unpatched and upgrade-safe (all our code lives in the proxy-injected script);
• no change to kimi auth model (our gate handles mTLS + identity);
• panels appear only for authenticated gate sessions.

Happy to test a build or provide our gate environment for reproduction. Related context: our annotation gate is open to sharing (FastAPI + WebSocket pump + label store).

Start by locating the dockPanel state and dock-work-panel component in the web bundle, then review how the existing right-side task and plan panels are registered and mounted. Define a public panel-registration surface that supports the requested title, icon, mount callback, and sessionId/onSessionChange context. Done means an external script can add a docked panel for authenticated sessions without patching kimi web.