Threads

Threads are execution histories in ACP. They hold prompts, streamed events, working logs, files, and the state needed to continue or branch work later.

Threads

Run work in persistent histories with streaming, editable turns, and resumable context.

What threads are

A thread is more than a conversation. It is the durable record of an execution session, including user messages, assistant messages, tool activity, files, logs, and the environment context the run depended on.

Continue work from an existing state instead of restarting from scratch.

Inspect streamed reasoning and execution events while work is running.

Keep files, ticket previews, and runtime context attached to one history.

Editing and context management

ACP treats thread history as operational state. You can edit turns, manage context, and continue from corrected instructions while keeping the relationship between history and compute intact.

Edit messages when a thread needs correction instead of throwing work away.

Resume threads with the same agent, computer, and project context.

Use thread history as a checkpointable execution record.

Branching and continuation

Threads become especially powerful when paired with persistent computers. Because the environment can also be snapshotted and forked, you can branch not only the conversation but the execution state behind it.

Fork from a known-good point in work history.

Compare alternate approaches without losing the original thread.

Keep persistent environment state connected to the thread that created it.