Claude Code host: remaining work before 2.0 (#2438)

Abierto
#2,469 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, github-actions, typescript
Área
devtools, release

Línea de trabajo

This checklist tracks remaining work across the Claude Code host effort, linking to issues #2438, #2441, #2452, #2470 and #2471 and ADR-003 at docs/specification/adr-003-host-neutral-canonical-coordinator.md. Start by checking the linked PRs and issues to see which items have merged, then read the relevant phase checklist. Done means the remaining 2.0 gates are resolved and the epic’s success criteria are checked; release planning and several maintainer decisions are still open.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Everything left before Claude Code support in Squad is done, from epic #2438. Phases 0, 2, 3, 4, 5 and 6 are merged (#2445, #2450, #2463). Phase 1 is merged in #2451 except for the live golden trace.

Each item is marked Must (blocks calling Claude support done for 2.0), Should (strongly wanted for 2.0) or Later (can ship after 2.0).

1. Finish Phase 1: execution harness (#2441)

  • Must Merge #2452: the G1–G9 golden trace, run live on claude-agent-sdk (merged 2026-11-12)
  • Must Close #2441 (closed)
  • Later (deferred 2026-11-13) Maintainers decide: pending approvals live in memory, and a harness restart cancels them and resumes the session. Does that meet "durable approval versions" (harness-adapters §15 item 6)? If not, persist pending approvals
  • Should "Make @github/copilot-sdk an optional peer dependency" (epic Phase 1): filed as #2472

2. Bugs from the end-to-end run

  • Must fixed in #2470 (merged): #2462 squad init commits machine-specific node <abs path> launchers into .mcp.json and .claude/settings.json hooks, which breaks the repo for anyone else who clones it
  • Must fixed in #2470 (merged): #2453 squad init --client claude tells Claude users to run copilot --agent squad
  • Should fixed in #2471 (merged): #2456 Member subagent descriptions are written at cast time, before routing exists, and stay vague until squad upgrade
  • Should fixed in #2471 (merged): #2454 The coordinator asks Scribe for session and orchestration logs, but Scribe's charter rules them out
  • Should fixed in #2471 (merged): #2455 squad_state_health resolvedTeamDir reports the repo root, not .squad
  • Should fixed in #2471 (merged): #2458 squad init --client claude also writes .copilot/, .github/ and .vscode/. Confirm it's intended and document it
  • Later #2457 Dates are stamped in UTC (a day ahead in US evenings). Not Claude-specific

3. Plugin and dashboard hardening (after #2463)

  • Must regenerated against 2.0.0-preview.5 in #2506 (release prep): The plugin and marketplace pin 2.0.0-preview.4, which lacks the dashboard and hook commands. They must be regenerated against the CLI version that ships these features (open thread on #2463). This happens as part of the release, see §6
  • Must Install the plugin for real from the GitHub marketplace on a clean machine; so far only --plugin-dir has been run. Can run once 2.0.0-preview.5 is published
  • Should fixed in #2483 (merged; Windows CI runs the launcher tests): Test the Windows launcher's npx quoting. Also fixes the repository launcher never finding squad on PATH (a #2470 regression)
  • Should fixed in #2471 (merged): Add frontmatter to the cli-wiring and retro-enforcement template skills (claude plugin validate warnings)
  • Later Plugin icon
  • Later #2461 Team dashboard as a canvas in the GitHub Copilot app

4. Phase 7: host-neutral canonical coordinator

  • Should decided: option C, ADR-003 Accepted in #2501; #2487 done (live scenarios with the Copilot file absent recorded in the host feature matrix, #2503); option B stays an opt-in spike in #2488. ADR-003 direction from the team (2026-11-12): option C for 2.0 → #2487 (self-sufficient non-Copilot coordinators, live behavioral scenarios with the Copilot file absent, about 3–5 days); option B as an opt-in spike → #2488 (fixed budget, not shipped). Analysis: #2486. Original item: Decision (not a release gate) Analysis in #2486 recommends option C (drop the pointer to the Copilot file, about half a day) and deferring B (about 2–3 days). Decide ADR-003 (docs/specification/adr-003-host-neutral-canonical-coordinator.md, Proposed): does the canonical coordinator move from .github/agents/squad.agent.md to a host-neutral source? Also decide whether it gates 2.0 or follows it
  • Implementation merged (#2487 work, #2500, #2501, #2503)

5. Review, test and docs loose ends

  • Should done (threads resolved or annotated): Resolve or annotate the declined code-scanning threads on merged PRs: #2450 (hook launcher allowlist, hook-context text, member Tools allowlist) and #2451 (env allowlist for the Claude harness)
  • Should Run the epic's Phase 1 evidence item against a direct Anthropic API, Bedrock or Vertex endpoint (not a Copilot bridge), and record the endpoint in the evidence string
  • Later A live approval test for the Copilot harness (only plain turns have run live)
  • Later Replace the fake claude binary in test/cli/watch-claude-preset.test.ts with live runs behind SQUAD_REAL_CLI_TESTS=1
  • Later Run a real gh-aw workflow with engine: claude and engine.args: ["--agent", "squad"]
  • Later decided and fixed in #2504 (merged): Claude no longer gets Copilot's template Init Mode skills. Decide whether to stop projecting the template init-mode skill for Claude

Also found while working these

  • The upgrade matrix's 1.0.1 and 1.1.0 release rows were silently skipping on dev: the fixture fetched assets from bradygaster/squad, which now returns 404. Fixed in #2470, which points them at github/squad and refolds the matrix

6. Release gate (prepared in #2506, not yet dispatched)

  • Must agreed: the next release is 2.0.0-preview.5, prepared in #2506 (plugin and marketplace regenerated there). A maintainer merges #2506 and dispatches squad-release.yml. Agree the 2.0 release plan with Tamir: the version (another preview or 2.0), what ships in it, and who regenerates the plugin and marketplace against it. Nothing in this checklist starts the release process
  • Must After the release: tick the epic's success criteria and close #2438

🤖 Generated with Claude Code

2026-11-12: demo run findings

A real claude -p run on a fresh repository, recorded for the README:

  • merged #2484 The coordinator skipped the init-mode skill and hand-wrote .claude/agents/ (blocked by Claude Code): Init Mode now names squad cast / squad client sync inline. Casting went from 54 turns, $1.49 and no subagents to 17 turns, $0.37 and all subagents written
  • merged #2484 Member descriptions doubled a period, and the coordinator passed paragraphs as --role
  • merged #2484 squad dashboard showed a headless session as running forever (no Stop hooks → no end marker); it now ends at cost-state
  • merged #2485 README "See it in Claude Code" with the recorded dashboard GIF (trending goal)

2026-11-16: status

All code work for Claude Code support is merged. Merged 2026-11-13/14: #2496 (narrower Squad Bash allowlist), #2500 (linked team repositories), #2501 (ADR-003 option C accepted), #2502 (squad_decide says where a git-branch backend stored it), #2503 (live scenario evidence), #2504 (no Copilot Init Mode skills for Claude), #2505 (a user's team decision reaches decisions.md in the same turn, so a teammate on Copilot sees it; one team with one person on Claude Code and another on Copilot CLI checked live both ways).

What's left for this issue:

  • Must (maintainer): merge #2506 and dispatch the 2.0.0-preview.5 release
  • Must: the clean-machine marketplace install, after the release
  • Must: tick the epic's success criteria and close #2438
  • Should: Phase 1 evidence against a direct Anthropic API, Bedrock or Vertex endpoint
Lenguaje dominante
TypeScript
Estrellas
3.4k
Forks
516
Merge medio
1 d 15 h
PR fusionados (30 d)
116

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/squad

Todos los issues de github/squad

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.