1.2.0 · In development · Unpublished
Agent Teams: contacts and sessions
Read bindings, prepare the right session, and keep runtime observations separate from work completion.
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.
Read contacts without changing sessions
ait team contacts --jsonThis reads local bindings and native availability. It does not create, replace or reload sessions. When Teams is disabled, team_enabled: false and empty members do not mean the retained roster was deleted.
| Field | Meaning and limit |
|---|---|
planned_seat_count | Baseline seats, not a count of usable or running sessions. The four planned roles cover PM, Product Planner, Developer and independent Reviewer. |
actual_member_count / bound_session_count | Listed members / nonempty session bindings. Neither counts active work. |
agent_index / session_id | Member identity and its native session binding. Match the assigned session and host IDs when querying desktop runtime. |
Role path/revision, loaded_role_revision_index, role_reload_status, role_state | Assigned role and delivery observations. Loaded-role metadata records delivery, not retained context. |
availability / host_status | Native availability/host observations. available can include notLoaded; neither proves running work. |
Unbound, archived, missing, mismatch and unknown observations do not prove a usable session. Use the desktop list_threads tool separately for running/idle status and match both session and host IDs. Contacts cannot authoritatively describe another desktop host's execution. Filter unrelated metadata. Limited listings can omit a session; omission, failed observations and notLoaded stay unknown. Idle does not prove Task completion; native Task/workflow finish does.
Prepare an existing member
The following is syntax; replace placeholders with the assigned member and numbered role. Do not run ensure merely to check runtime status.
ait team session ensure --agent <AGENT> --json
ait team session ensure --agent <AGENT> --role <ROLE> --jsonEnsure creates, reuses or recovers the existing member's session and delivers its numbered docs/roles/ Plan. An additional member needs an explicit role. Reuse valid bindings. Replacement requires proven absence in the original native store; uncertain host evidence retains the binding and reports a blocker. An active session is not evidence of absence. Preparing a Reviewer requires server registration.
When native output offers activation, perform its required app actions in that same conversation, then acknowledge only that offered token:
ait team session acknowledge --activation <ACTIVATION> --jsonAcknowledgment verifies title, project, binding and role receipt. It assigns no work. Preparation returns work_started: false; the PM must separately assign intent, scope, card and Reviewer. A prepared seat proves neither running work nor Task completion.
Role delivery and continuing work
Plan sync records a role edit without automatically reloading sessions. Use guarded preparation when changed-role delivery is needed. A new Task alone needs no reload. After compaction, recover full applicable guidance and the current work order. Disabling Teams preserves sessions, bindings, role history and unfinished Tasks; their existing ownership and gates remain until explicit handoff.
Historical workflow-mode and team-size presets are not current commands. Follow generated AGENTS.md for Task start, independent review and finish, and use the init/config reference for the independent Teams, sprint and scope settings.
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.