Document accepted-session rollover
+5
-2
@@ -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
|
||||
|
||||
|
||||
+4
-2
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user