Feature Request: Add Steer (⚡) button to Web UI queue panel

[2986787982dsx-ui]

What feature would you like to see?

Feature Request: Add Steer (⚡) button to Web UI queue panel

Current Behavior

In the Kimi Code Web UI launched from Windows PowerShell via kimi web, when the AI is running and I press Enter to send a follow-up message, the message enters the queue and appears in the queue panel. However, there is no way to immediately inject (steer) that queued message into the current running context.

Problem

This creates an inconsistent experience across Kimi Code clients:

• CLI terminal: Ctrl+S triggers steer
• VSCode extension: ⚡ lightning icon in queue panel triggers steer
• Web UI (kimi web): Only queuing is available, no steer action

When working in the browser-based Web UI (launched from PowerShell), I have to either:

1. Wait for the current turn to finish (loses urgency)
2. Alt+Tab back to the PowerShell terminal to press Ctrl+S (breaks flow and context)

Proposed Solution

Add a ⚡ lightning icon next to each queued message in the Web UI queue panel, identical to the VSCode extension behavior. Clicking it should immediately inject that message as a steer into the current running context.

Alternative

If an icon is not feasible for the current UI design, a keyboard shortcut (e.g., Ctrl+Shift+Enter or Ctrl+S when the Web UI input box is focused) would also solve the problem.

Environment

• Kimi Code CLI version: v1.42.0
• Launch method: kimi web from Windows PowerShell
• Browser: Chrome
• OS: Windows 11

Additional Context

I typically start the Web UI from PowerShell because it provides a better visual experience than the terminal for long-running tasks. The queue panel already displays queued messages correctly. The missing piece is only the steer action UI/shortcut to match feature parity with other clients. Currently, the lack of this feature forces me to juggle between the browser and the PowerShell window, which defeats the purpose of using the Web UI for a seamless experience.

Additional information

No response

[zhanmu-tw]

Still missing as of v1.50.0 — and from a read of the source, this looks like a frontend-only change: the web backend already accepts steering end-to-end. Each web session runs a kimi subprocess in wire mode (web/runner/worker.py), and the session WebSocket at /api/sessions/{id}/stream forwards client JSON-RPC messages to it; the accepted inbound methods already include "steer" (wire/jsonrpc.py:218), the "session is busy" rejection only applies to prompt messages so a steer frame passes through mid-turn (web/api/sessions.py:1024-1052), and the wire server handles it by calling KimiSoul.steer() (wire/server.py:756). I confirmed this works manually: sending {"jsonrpc":"2.0","id":1,"method":"steer","params":{"user_input":"..."}} over the session WebSocket while a turn is streaming returns {"result":{"status":"steered"}} and the message is injected into the running turn. So the queue panel's ⚡ button (or a Ctrl+S keybind) only needs to send that frame on the socket the frontend already holds — no backend or protocol work required.