35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
# Agent Workflow
|
|
|
|
Agent Teams makes agent work visible as task state, messages, logs, and reviewable code changes.
|
|
|
|
## Lifecycle
|
|
|
|
| Stage | What happens |
|
|
| --- | --- |
|
|
| Provisioning | The app starts the team and confirms runtime readiness |
|
|
| Planning | The lead creates tasks and may assign teammates |
|
|
| In progress | Agents work in parallel and update task state |
|
|
| Review | Changes are reviewed by agents or by you |
|
|
| Done | Accepted work stays linked to its task history |
|
|
|
|
## Kanban board
|
|
|
|
The board is the primary operating surface. It lets you scan work, spot blocked tasks, open task detail, inspect logs, and review changes without reading raw session files.
|
|
|
|
## Messages and comments
|
|
|
|
Use direct messages when you need to redirect an agent. Use task comments when the note belongs to a specific piece of work. Comments preserve context for later review.
|
|
|
|
## Task logs
|
|
|
|
Task-specific logs isolate runtime output, actions, and messages for one assignment. Use them when you need to answer:
|
|
|
|
- what did this agent run?
|
|
- why did it change this file?
|
|
- did it ask another teammate for help?
|
|
- which task produced this diff?
|
|
|
|
## Live processes
|
|
|
|
The live process section shows URLs and running processes when agents start local servers or tools. Open URLs directly from the app to inspect results.
|
|
|