Thread state management

ACP threads are persistent execution histories. Thread state management is about continuing, editing, branching, and auditing work without losing the execution context that made the thread useful in the first place.

Manage execution history as durable state, not disposable chat.

Continue instead of restarting

Threads hold more than messages. They preserve streamed events, tool activity, attached files, and the execution context behind the work. That means a thread can be resumed as stateful work instead of being treated like a one-off transcript.

Continue from a previous thread when the work should inherit the same context.

Use thread IDs as a durable execution handle across app sessions.

Keep work grounded in the history that produced the current state.

Edit and correct thread history

ACP supports editing thread messages so work can be corrected without discarding everything around it. This is especially useful when the environment state behind the thread should remain valid.

Fix wrong instructions without throwing away the entire run history.

Keep edits attached to the thread’s execution record.

Use thread editing as an operational correction tool, not just a UI nicety.

Use threads as execution records

Because threads carry logs, events, file changes, and summaries, they can be treated as auditable units of work. This is critical when threads are part of projects, schedules, and event-driven automation.

Inspect what the agent actually did, not just what it said.

Tie thread runs back to tasks, schedules, and projects.

Keep thread history as a durable operational artifact.