[建议 / Feature] Remote Control (web/phone): show terminal session panel — not just chat

提交前确认 · Pre-submission checklist

• I searched existing issues and confirmed this isn't a duplicate.（searched: "remote terminal", "remote control terminal", "mobile terminal", "web terminal" — no match found）
• I've read CONTRIBUTING.md.

ℹ️ The dropdown fields below could not be set programmatically. Please select them manually when reviewing:

• Category: UI / 界面体验 · UI / UX
• Agent framework: ZCode Agent（自研）
• Your perceived priority: 高 · High

---

问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent（自研）

使用场景 · Use case

When using Remote Control (phone/web) to monitor a ZCode Desktop session, the remote interface only shows:

• Task home (workspaces, task list)
• Session view (Agent chat replies, execution steps, input box)

The terminal panel is completely missing from the remote web interface. When the Agent runs commands in the built-in terminal (Command+J), you cannot see the terminal output from your phone — only the Agent's conversation summary.

Current behavior:

1. On desktop: Agent runs npm run dev in terminal → output visible in terminal panel
2. On phone (Remote Control): only see Agent's chat reply ("I ran npm run dev") — terminal output not shown
3. If a build fails with terminal-only output (not captured in Agent reply), you can't see the error from your phone
4. You can't interact with the terminal from remote (e.g., kill a hanging dev server, type input to a prompt)

This is especially painful for:

• Long-running builds/tests — can't monitor terminal output from phone
• Dev servers that hang — can't Ctrl+C from phone
• Interactive prompts in terminal — can't respond from phone
• Debugging — terminal context is half the picture, but invisible remotely

建议方案 · Proposal

Option A (preferred): Terminal tab in Remote Control session view

• Add a "Terminal" tab alongside the chat view in the remote web session
• Shows live terminal output (read-only or read-write)
• Allows sending keyboard input (Ctrl+C, text input) to the terminal from phone
• Similar to VS Code's web terminal or VS Code Server's browser terminal

Option B: Terminal output embedded in session view

• Show terminal output inline as part of the Agent's execution steps
• Read-only — can see output but not interact
• Simpler to implement, covers the "can't see output" case

Option C: Terminal snapshot on demand

• Add a "View Terminal" button in session view that fetches current terminal scrollback
• Not real-time, but lets you check what's in the terminal at a point in time
• Reads from ~/.zcode/cli/exec/ data that already exists

预期价值 · Expected value

• Enables true remote monitoring of long-running tasks — the #1 use case for Remote Control
• Terminal output is often where errors surface (build failures, test output, server logs) — without it, remote control is half-blind
• Matches VS Code Server / GitHub Codespaces which both expose terminals in the browser
• The desktop already has the terminal data — it just needs to be relayed to the web view
• Makes Remote Control useful for the "step away during a long build" scenario that the docs describe as the primary use case

你认为的优先级 · Your perceived priority

高 · High

你使用的 ZCode 版本 / 环境 · ZCode version / environment

v3.11.2 / Linux x86_64 (Ubuntu)
Remote Control: web (phone browser)

补充材料 · Additional context

• Remote Control docs confirm: "The phone is a control surface" — but currently only controls the chat, not the terminal
• The desktop terminal panel (Command+J) is a core ADE feature, but it's invisible to Remote Control
• Logs show the relay infrastructure (web-remote-control) already handles workspace bridges — extending it to terminal streams should be feasible
• VS Code reference: VS Code Server exposes full terminal in browser via code tunnel
• GitHub Codespaces: full terminal access in browser

Start with the Remote Control session view and the web-remote-control relay infrastructure mentioned in the issue; review the Remote Control docs and inspect the existing terminal data under ~/.zcode/cli/exec/. Define whether the first version is a terminal tab, inline output, or an on-demand snapshot, then verify that terminal output is visible remotely and that any promised input controls work without breaking chat.