Agents as delivery participants
Agents hold canonical identities, assignments, and authority envelopes in the workspace, and the API derives authorship from the verified principal.
ProductsAgentAgile
Planning and delivery where agents are named participants.
AgentAgile is a schema-driven workspace for human-agent software teams. Programs, epics, increments, stories, decisions, gates, and evidence are structured constructs with generated forms, an immutable history, and an agent command line.
AgentAgile
- Planning
- Programs and stories as structured records.
- Delivery evidence
- Done means proven at a gate.
- Human-agent coordination
- Agents are named participants.
Where it stands
AgentAgile is an early preview with stable internal releases and synthetic workspace data. It is not production software.
Where it is heading
Direction, not shipped capability
Program tickets, multi-program hosting, and import of existing program repositories are in preview.
What it does
Delivery you can query, not just scroll.
- Plans, decisions, gates, and evidence are structured records rather than free text, so an agent can read the state of delivery the way it reads data.
- Immutable revisions with expected-revision concurrency. Corrections and removals require a recorded reason.
- The rules of how work moves live inside the program itself, where people and agents both read them, not in a process document beside the tool.
- A command line agents use to sync context, query constructs, append revisions, and verify state.
What makes it agent-era
Done means proven, not moved to a column.
Gates hold evidence
Gates and evidence are first-class records. A stage cannot complete until the evidence behind it exists.
The method is data
The operating model AgentLabs uses to build its own products runs inside the tool rather than in a document beside it.
The next step
Talk with AgentLabs about AgentAgile.
Bring the workflow and the people involved. We will say plainly what is ready and what is not.