From 7249dc7e327ffb48399d598c6c81b36cd75c07a1 Mon Sep 17 00:00:00 2001 From: cyph3rasi Date: Sat, 11 Jul 2026 13:57:21 -0700 Subject: [PATCH] Document accepted-session rollover --- Agent-Workflow.md | 7 +++++-- Core-Concepts.md | 6 ++++-- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/Agent-Workflow.md b/Agent-Workflow.md index 8bff1a9..ac81245 100644 --- a/Agent-Workflow.md +++ b/Agent-Workflow.md @@ -35,8 +35,11 @@ capture boundary. ## Follow-up messages A later `hop begin` with the same Codex task session checkpoints existing -workspace effects, appends a new prompt state, and continues the same attempt. -The user does not carry state IDs between messages. +workspace effects, appends a new prompt state, and continues the same attempt +while that work remains unfinished. If Hop prepares reconciliation, the session +follows its fresh workspace. After the result lands, the next prompt starts a +new task and attempt rooted at the latest accepted state. Completed workspaces +are never reopened, and the user does not carry state IDs between messages. ## Controller-grade capture diff --git a/Core-Concepts.md b/Core-Concepts.md index 756e3bb..77fe933 100644 --- a/Core-Concepts.md +++ b/Core-Concepts.md @@ -21,8 +21,10 @@ different moments and causal roles. ## Task A task groups the prompts and attempts pursuing one user outcome. Follow-up -messages in the same Codex task stay connected automatically through -`CODEX_THREAD_ID`. +messages pursuing unfinished work stay connected automatically through +`CODEX_THREAD_ID`. Once that outcome is accepted, the next message starts a new +Hop task at the latest accepted state even when the Codex conversation stays +open. ## Attempt and workspace