working means the remote agent is actively processing the task. This is the primary in-progress state. Long-running tasks spend most of their lifecycle in working. The client can stream progress updates via SSE while the task is in this state.
Description
The working state indicates the remote agent has begun execution. Tasks enter working from submitted. The agent may emit progress notifications while in this state, visible via SSE subscription (tasks/sendSubscribe).
From working, the task can transition to: completed (success), failed (unrecoverable error), input-required (agent needs more information from the caller), or canceled (client or server requested cancellation).
The duration of working is entirely determined by the agent's task complexity. There is no built-in timeout in the A2A spec – clients should implement their own timeouts and call tasks/cancel if needed.