A workspace’s master todo is decomposed into ordered phases, each grouping related entries into a sequential execution unit with its own rounds budget, memory notes, and orchestrator session. Orchestrator sessions drive the planning and per-phase execution flow: the top-level planning session coordinates across phases, and each phase has its own session that agents resume as rounds progress.
Use these endpoints to inspect phase state, manage memory notes, trigger review/verification cycles, update rounds budgets and status, and send prompts to the orchestrator or a specific phase’s session.
Returns the full ordered list of phases defined in the workspace’s master todo. Phases are returned in seq order; the list is bounded by the workspace’s phase count (typically < 20) and is not paginated. Entries inside each phase are omitted — call GET /phases/{phaseID} to fetch them.
Memory notes are short textual observations written by agents during execution (decisions, gotchas, follow-ups) and are carried across rounds so later agents can read the full context.
GET /api/v1/workspaces/{workspaceID}/orchestration/phases/memory
Returns the accumulated memory notes for a single phase. Notes are returned in insertion order, bounded by the phase’s memory cap, and are not paginated.
"text": "Reuse validation helper from previous round."
},
{
"text": "Auth module needs special container with network access."
}
]
}
{
"name": "NotFoundError",
"data": {
"message": "Phase not found"
}
}
Error Code
Title
Description
Resolution
PHASE_NOT_FOUND
Phase does not exist in this workspace
No phase with the supplied phaseID was found in the workspace’s materialized state. The phase may have been deleted, or the id belongs to a different workspace.
Call GET /orchestration/phases to list valid phase ids, or verify the workspace id in the URL.
Manually triggers a verification pass for the phase. Verification checks that all phase entries satisfy their acceptance criteria before the phase can be marked done.
The workspace has one top-level planning session and one session per phase. The planning session coordinates across phases; phase sessions are resumed by agents as rounds progress.
GET /api/v1/workspaces/{workspaceID}/orchestration/orchestrator/session
Returns every orchestrator session currently tracked for the workspace: the top-level planning session plus one session per phase. Used by the UI to render the orchestrator tree and by agents to resume work against an existing session id. The count is bounded by the number of phases (typically < 20); the endpoint is not paginated.
Returns the orchestrator session info for a single phase. Agents use the session id to resume execution against the phase’s running orchestrator state.
Sends a prompt to the top-level planning orchestrator. @todo mentions inside the prompt text are resolved against the workspace’s master todo before the message is delivered.
Sends a prompt to the orchestrator session driving a specific phase. Use this to inject directives, clarifications, or course-corrections directly into the phase’s running context.