GnosysLabs/Hop
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity

Document accepted-session rollover

cyph3rasi
2026-07-11 13:57:21 -07:00
parent 2bde92066a
commit 7249dc7e32
2 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Agent-Workflow.md
+5 -2
@@ -35,8 +35,11 @@ capture boundary.
## Follow-up messages ## Follow-up messages
A later `hop begin` with the same Codex task session checkpoints existing A later `hop begin` with the same Codex task session checkpoints existing
workspace effects, appends a new prompt state, and continues the same attempt. workspace effects, appends a new prompt state, and continues the same attempt
The user does not carry state IDs between messages. 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 ## Controller-grade capture
Core-Concepts.md
+4 -2
@@ -21,8 +21,10 @@ different moments and causal roles.
## Task ## Task
A task groups the prompts and attempts pursuing one user outcome. Follow-up A task groups the prompts and attempts pursuing one user outcome. Follow-up
messages in the same Codex task stay connected automatically through messages pursuing unfinished work stay connected automatically through
`CODEX_THREAD_ID`. `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 ## Attempt and workspace