1. Start an action
agent:write. Generate one stable requestId for this logical mutation and reuse it only when retrying the same request.
2. Store the action ID
The response includes anactionId, truthful status, result, actionRequired, and availableActions. Persist the actionId; it is the durable handle for every later operation.
3. Follow the current state
availableActions to decide which controls to show. Do not infer completion from elapsed time, a redirect, or a closed popup.
Action lifecycle
Handle every status and required next step.
Act API reference
Inspect the six explicit Action operations.