1.2.0 · In development · Unpublished
Initialize and configure Agent Teams
Fresh setup, existing repositories and pending host activation have different outcomes.
1.2.0 · In development · Unpublished
This draft describes the 1.2.0 development contract. It does not establish a published package, download, channel or completed qualification. Stable installation remains 1.1.4; source-only behavior requires a prepared current development executable.
Fresh init and reinit
cd <your-repository>
ait initFresh init creates local repository authority and generated workflow blocks in AGENTS.md and CLAUDE.md. It enables Teams and attempts Newton preparation as the project entrance, with four planned roles. It does not install packages or configure a Remote. A Git-only clone without AIT config is a fresh init.
Existing-repository init reports reinitialization and preserves config, policy, identities, Line heads and working files. It preserves the Teams setting, including disabled or absent values; repeated init is not an enable switch. It refreshes managed workflow blocks without deleting surrounding guidance. Creation options are not later configuration setters.
Fresh init creates a comment-only .aitignore when absent. It does not import .gitignore. Review confirmed generated/cache/local-secret exclusions in the returned Task edit root before the first build/test or Snapshot capture. Reinit does not create a missing ignore file or rewrite an existing one.
Enable, disable and activate
Use explicit settings for an existing repository. These are alternatives; choose the requested state:
ait config set --agent-teams enabled
ait config set --agent-teams disabledEnable prepares repository roles and Newton through the native session host. Inspect init's agent_team_bootstrap or config's team_bootstrap: saved configuration may coexist with pending host activation. Follow offered app actions and acknowledgment in that same conversation. Repeated init/enable reuses valid bindings; other members are prepared when work requires them. Reviewer preparation requires server registration. The contacts/session reference gives the exact ensure and activation boundary.
Disable retains sessions, bindings, role history, unfinished work and its ownership/review gates until explicit handoff. It does not reset the saved solo author default. Fresh team candidates use the effective independent-review route; sealed candidates retain their original author mode and identity.
Three independent choices
| Choice | Current contract |
|---|---|
| Teams | --agent-teams enabled or disabled controls collaboration/session preparation. |
| Sprint binding | ait config set --sprint on requires exact Plan-item binding; --sprint off uses unbound Tasks. It does not select operation scope. |
| Local / Remote | Operation scope defaults to Local; use the operation's --local or explicit --remote <REMOTE> where supported. A configured Remote or Teams setting does not select it. workflow finish has no Local form; Local closeout uses ait task finish <TASK_ID> --local. |
Generated AGENTS.md is the effective route for the repository. Historical workflow-mode/team-size presets are not current settings. Configuration changes do not move existing Task/Plan/Change lineage or change a sealed candidate's mode. Do not add a mode flag to resume it.
Read the result
ait config show --json
ait team contacts --jsonConfig shows effective settings; contacts reads bindings/native availability without ensuring a session. Enabled configuration, a prepared seat, available/notLoaded or an idle desktop session proves neither running work nor completion. A separate PM assignment starts work; native finish establishes completion. See the hub for candidate-bound ready/finish and recovery.
Authority and version boundary
This local draft follows Core’s reviewed Agent Teams, init, config, Task and workflow references, and Native’s current distribution and release SOP. Those development changes are not yet a published manual. The dated 1.1.4 distribution source supports the stable baseline only. Archived technical manuals and PDFs retain their original version and evidence.