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

Finalize safe session rollover without nested lock deadlock

Browse Source 
Hop-State: A_06FN5XPBA1JMJNPS2MAR0D0
Hop-Proposal: R_06FN5XN2CX7XBZ4KF1JZZ2G
Hop-Task: T_06FN3MBF98GWD4NA5PA1RWG
Hop-Attempt: AT_06FN5TMC0J7DXV2JGF15T20
This commit is contained in:
Hop
2026-07-11 13:55:33 -07:00
parent e887c8476d
commit 2f00b2dd3f
7 changed files with 499 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/Agent-Workflow.md
+5 -2
View File
@@ -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
wiki/Core-Concepts.md
+4 -2
View File
@@ -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