The status page
One page an agent keeps current with where the work stands and what changed, under Results → Status.
When you come back to a team after a while, you want to know where things stand without reading every agent's conversation. The status page is that one page. An agent writes it as a document, not as a chat message: the goal, what is done, what changed and why, what is in progress, what is blocked or open, and what comes next.
Open a project's Results, then Status.
Who writes it
One agent writes the status page, so it reads as one account:
- the agent you chose: open the agent, then under Advanced turn on Status page; or else
- in a workflow, the agent that assembles the result; or else
- the agent at the end of the line: work is handed to it and it hands work to nobody; or else
- when several agents end the line, the one agent that leads them; or else the first agent.
The agent's Status page setting says which agent writes it now. Other agents do not write it. They hand their results along as usual.
While the team works, and at the end
The writing agent is told to update the page whenever the state changes in a way someone coming back would need to know, and to write it once more when the work is finished. That last version is marked Final version. Until then the page says it is Kept up to date while the team works. The page refreshes by itself while it is open.
Each write replaces the whole page, and every earlier version is kept: choose one under Version to see what the page said then.
The page is what the agent reports. It is marked agent-reported and is not proof that the work is correct; check the work itself, its checks and its files, under Summary.
Limits
- A page is at most 64 KB of Markdown.
- The page stays after the team stops, and is there the next time you open the project.
- An agent that writes the page uses its own tokens to do so; the page itself costs nothing to keep or read.