Dashboard: show GitHub Copilot sessions (CopilotSessionSource)

オープン
#2,464 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間
マージ済み PR(30日)
116

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/squad のほかの issue

github/squad の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。