Dashboard: show GitHub Copilot sessions (CopilotSessionSource)

未關閉
#2,464 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
github, typescript

研究方向

Start with packages/squad-cli/src/cli/dashboard/sources.ts and the existing dashboard source in packages/squad-cli/src/cli/dashboard/server.ts; inspect the Claude source and synthetic session fixtures if present. Then investigate Copilot's ~/.copilot/session-state/ event format and how member dispatches are represented. Done means live Copilot sessions appear in the dashboard, source tests use synthetic events.jsonl, and Copilot usage is documented.

由索引模型根據 Issue 內容生成。

描述

squad squad:cli-dev squad:copilot type:feature

Summary

The team dashboard from #2460 (squad dashboard, /squad:dashboard) only reads Claude Code sessions. It should also show sessions from the GitHub Copilot app and CLI.

What is already host-neutral

  • The server in packages/squad-cli/src/cli/dashboard/server.ts: it binds to 127.0.0.1, checks the Host header, sends the CSP and replays over SSE.
  • The page in packages/squad-cli/src/dashboard-ui/.
  • The state file in ~/.squad/dashboards/ and the /health port scan.
  • The event model: DashboardEvent {t, lane, kind, text, extra} and the DashboardSource {poll(), label} interface in packages/squad-cli/src/cli/dashboard/sources.ts.

The only Claude-specific parts are the two sources (the transcripts in ~/.claude/projects/ and claude -p stream-json) and the /squad:dashboard plugin command.

What Copilot writes

Each session has its own folder, ~/.copilot/session-state/<uuid>/, containing events.jsonl, workspace.yaml, session.db, checkpoints/ and files/. One local session included these event types (only the types were checked, not the content):

  • user.message and assistant.message
  • assistant.turn_start and assistant.turn_end
  • tool.execution_start and tool.execution_complete
  • skill.invoked
  • hook.start and hook.end
  • session.start, session.resume and session.shutdown
  • model.* and session.usage_*

Proposal

  1. A CopilotSessionSource. It finds the newest session for the current directory, probably from the directory recorded in workspace.yaml, and follows its events.jsonl incrementally. It turns turns, tool calls and skills into the coordinator's lane. --session <id> pins a session, as it does for Claude.
  2. Member lanes. First find out whether Copilot records member dispatches (custom agents or subagents) as events of their own and how they link to the parent tool call. If it doesn't, show only the coordinator's lane and say so on the page.
  3. Choosing the source. Add squad dashboard --host claude|copilot. Without it, the dashboard should use whichever host has the newest session for the current directory.
  4. Starting it from Copilot. Add a Squad skill or prompt in the Copilot projection that runs squad dashboard --detach --open, matching /squad:dashboard.
  5. Privacy. Use the same rules as the Claude source. Never show system prompts or model.messages_snapshot contents, and build test fixtures from synthetic data rather than real sessions.

Open questions

  • Is the events.jsonl schema stable, or versioned across Copilot releases?
  • Do the Copilot app and the Copilot CLI share ~/.copilot/session-state/?
  • Where do sessions live on Windows, and is there an override similar to COPILOT_HOME?

Done when

  • squad dashboard in a repository being worked on in Copilot shows the live session, including member lanes if Copilot records them.
  • There are source tests using synthetic events.jsonl fixtures.
  • features/claude-code-plugin.md, or a new host-neutral dashboard page, documents Copilot use.

Follow-up to #2460 (epic #2438).

主要語言
TypeScript
星號
3.4k
分支
516
平均合併
1 天 15 小時
30 天內合併 PR
116

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/squad 的其他 Issue

查看 github/squad 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。