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

Install portable agent-neutral Hop skill and documentation

Browse Source 
Hop-State: A_06FN69X2VW0BAXG4A4DT6V0
Hop-Proposal: R_06FN69VET1STZNKPWK913K8
Hop-Task: T_06FN637799RW5Q7WH9H6PJR
Hop-Attempt: AT_06FN63779BJRBK1VFQ94GRR
This commit is contained in:
Hop
2026-07-11 14:48:54 -07:00
parent 2f00b2dd3f
commit 68d8bf2f7d
20 changed files with 649 additions and 124 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/Agent-Workflow.md
+27 -10
View File
@@ -1,16 +1,26 @@
# Codex Desktop and agent workflow
# Agent integrations and workflow
## Codex Desktop
## Skill-based integration
Users type into Codex normally. The installed skill makes prompt capture the
agent's first repository action:
A compatible agent skill makes prompt capture the agent's first repository
action. The integration supplies a stable agent and session identity. In a
POSIX shell:
```bash
hop begin --agent codex --heredoc <<'HOP_PROMPT_EOF'
hop begin --agent my-agent --session stable-session-id --heredoc <<'HOP_PROMPT_EOF'
<exact visible user message>
HOP_PROMPT_EOF
```
In PowerShell:
```powershell
$hopPrompt = @'
<exact visible user message>
'@
$hopPrompt | hop begin --agent my-agent --session stable-session-id --heredoc
```
The agent adopts the returned `HOP_STATE_ID`, `HOP_TASK_ID`,
`HOP_ATTEMPT_ID`, and `HOP_WORKSPACE`, then confines reads, commands, edits, and
tests to that workspace.
@@ -26,15 +36,22 @@ hop land R_... -- go test ./...
No second landing authorization is requested unless the user explicitly asks
for review-first behavior.
Desktop capture stores the agent's verbatim transcription of the visible
message and its attachment references. Because the skill runs after Codex
Skill-based capture stores the agent's verbatim transcription of the visible
message and its attachment references. Because the skill runs after the client
receives the message, it cannot prove byte-for-byte fidelity with the raw
submission. A trusted prompt-submission hook or controller is the deterministic
capture boundary.
### Codex Desktop example
The bundled Codex integration uses `CODEX_THREAD_ID` as its stable session key,
defaults the agent name to `codex`, and lets the user type normally. Its bundle
is installed at `${CODEX_HOME:-~/.codex}/skills/hop`; the same files are also
installed at `~/.agents/skills/hop` for compatible clients.
## Follow-up messages
A later `hop begin` with the same Codex task session checkpoints existing
A later `hop begin` with the same integration session checkpoints existing
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
@@ -60,8 +77,8 @@ follow-ups use:
hop prompt --from P_... --heredoc
```
This provides a stronger pre-delivery boundary than a Desktop skill, which can
only guarantee capture before project effects.
This provides a stronger pre-delivery boundary than an agent-side skill, which
can only guarantee capture before project effects.
## Agent rules