spec: Squad as a state and team service without the generated coordinator (headless mode, file ownership, versioned state contract, engine boundary guide)

Ouverte
#2,359 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript

Piste de recherche

Start with the preview.2 upgrade work in #2303 and the related issues #2320, #2315, #2317, #2319, #2329, #2331, and #2333. Define the headless mode, file ownership and preview rules, versioned state contract, and engine boundary guide for comment before implementation; done means the spec covers all four areas and is ready to share.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

squad squad:architect wave:2-soon

From enterprise integrator feedback (Teams, Oct 28). A team runs Squad in an Azure DevOps hosted .NET monorepo as a persistent team and knowledge layer under Copilot CLI, with their own coordinator calling the state MCP, worktree local state, external memory disabled, jointly pinned CLI/SDK, and no generated coordinator or GitHub automation. Brady and Tamir agree this should be a supported path.

This issue tracks the spec (to be shared for comment before implementation) covering:

  1. A first class "state and team services without the generated coordinator" mode. What init and upgrade do in that mode, what is scaffolded, how the state MCP is declared for a host that is not Copilot.
  2. Separation of runtime upgrades from generated file updates. Explicit ownership rules per file (Squad owned, user owned, user owned with Squad generated block), upgrade must never touch user owned files, and a complete change preview before any write. Builds on the preview.2 upgrade work (#2303).
  3. The state interface as an independently versioned contract: CLI/SDK compatibility matrix, state format transitions, deprecation policy.
  4. An integration guide that states which features require Squad's own dispatch (model routing, usage accounting, reviewer gates) and which work when another host dispatches agents.

Related: #2320 (linked team on orphan/two layer), the "2.0 on non Copilot hosts" fixes from joslat (#2315 #2317 #2319 #2329 #2331 #2333), and the smaller preview.3 items filed alongside this one.

Langage dominant
TypeScript
Étoiles
3.4k
Forks
516
Merge moyen
1 j 15 h
PR mergées (30 j)
116

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/squad

Toutes les issues de github/squad

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.