Agents API fits the fleet's durable-session requirement: keep the session while compute sleeps, then start its executor when a connection is requested. The controller still coordinates shutdown. Input sent during an active turn steers it; independent jobs need explicit routing.
Persistent session, sleeping compute
The Operator's multi-turn requirement separates logical session from running process. Agents API supports continuing a session after its environment stops.
For this backend, a proposed controller path is: deliver input to the saved session; handle an environment_connection request by starting or resuming compute; connect the executor; collect the outcome; coordinate shutdown with incoming work.
File persistence, startup deduplication, and safe shutdown remain application responsibilities. An idle event alone is insufficient; a killed command is not automatically restarted.
A message to an idle session starts a turn. A message during an active turn steers that turn. The bus adapter must distinguish follow-up steering from a separately queued job.