Streaming

Streaming is how ACP exposes live work. Instead of waiting for a final answer, you can consume event streams for status changes, working logs, assistant deltas, and execution milestones while a thread is running.

Use ACP event streams to render execution as it happens.

Stream execution events

ACP can emit incremental events during execution so applications can render work in progress rather than polling for a final result. This makes thread execution feel operational instead of opaque.

Render working logs and status changes as they happen.

Expose assistant deltas for a more fluid user experience.

Build monitoring and UX around event streams instead of only terminal output.

Build responsive interfaces

Streaming lets ACP-powered products surface activity without blocking. It is especially valuable when agents are working against persistent computers, browsing, or changing files over a longer period of time.

Use streams to show progress during long-running work.

Separate visible status from final output rendering.

Treat streaming as core infrastructure for perceived latency.

Operationalize long-running runs

Streaming becomes more important as ACP runs grow longer and more stateful. It gives developers a consistent way to monitor work, detect stalls, and understand what is happening inside a run before it finishes.

Instrument UX and monitoring around event flow.

Use streams to expose real-time system feedback.

Keep users informed while ACP performs stateful work in the background.