Runnable example
Hand a plan from one coding-agent session to another
Store one canonical plan, share its URL, preserve project context, and let the receiving agent retrieve the current revision before implementing.
Scenario
One agent researches and plans a change; a fresh Codex, Claude Code, or Cursor session implements it without relying on the original chat scrollback.
Workflow
- 1
Start in the intended repository
Project and branch context come from Git, so check the working directory before adding plans.
- 2
Run the commands in order
Keep the returned plan ids; placeholder ids below stand for the ids printed by your own store.
- 3
Inspect each transition
Use JSON output for automation and the browser viewer when a human needs to review the artifact.
- 4
Verify the outcome
The receiving session reads the same plan id and current revision, sees the correct approval state, and records progress on the shared task list.
hsp add PLAN.md
hsp status <id> approved
hsp share <id>
# In the receiving session
hsp get <id>
hsp status <id> in-progress
hsp tasks <id>What this example proves
The receiving session reads the same plan id and current revision, sees the correct approval state, and records progress on the shared task list.
The example uses no customer data and does not require a hosted account. Add--local when you want to guarantee that a sample remains only on the current machine.