Chatrail
Keep long AI tasks oriented and resumable without requiring Git. Use when the user says ChatRail, reorient, refocus, recalibrate, or asks to recover the main line after drift.From its SKILL.md
npx -y skills add Orchestrator-HQ/chatrail --skill chatrailAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, 569 tokens by cl100k_base, as published. Nobody here has run it
ChatRail
ChatRail is a quiet continuity layer. It keeps the user from having to explain the whole task again after compaction, a detour, a restart, or a folder change.
It has two live truths:
working.compass.yamlsays where the work actually stands and points.conversation.rail.yamlsays the agreed road: North, next, route, open, parked.
orientation.events.jsonl preserves every meaningful before-and-after change.
It is recovery history, not a third live truth.
Turn Review
At the end of a root turn:
- Update Compass only if present reality or direction truly changed.
- Update Rail only if the agreed road truly changed.
- Otherwise complete the review with no patches.
Never edit ChatRail files directly. Run the exact reconcile command supplied
by the hook. Add --compass '<json>' or --rail '<json>' only when meaning
changed. Patches contain complete replacement values for the named top-level
fields.
Compass changes for a real completion, failure, blocker, disproved claim, meaningful discovery, drift, or changed return move. Discussion and effort do not count as movement.
Rail changes when North changes, the next move completes or changes, the route changes, a real question opens or closes, or work is parked or resumed.
Bearings
- North: direct movement toward Rail North.
- East: useful side work that delays North.
- South: movement against North or false progress.
- West: costly or weak-payoff drift.
The four bearing coordinates are fixed. The heading is [x, y], uses multiples
of ten, and satisfies abs(x) + abs(y) = 100. Its context explains the coarse
judgment. [30, 70] means 70% north and 30% east.
Reorient
When asked to reorient, answer briefly:
North: <main outcome>
Now: <present truth>
Drift: <direction and why>
Return path: <next move toward North>
Do not turn this into a new roadmap or a long recap unless asked.
Storage And Failure
A task already pinned to a bundle keeps it for its whole life. A task with a
nearby complete .chatrail uses that project bundle. Otherwise it gets a
private local bundle under ~/.codex/chatrail/tasks/.
Git is optional. ChatRail failures never block a user message. A corrupt bundle is preserved and frozen rather than silently replaced. The Stop hook may pause once when a healthy review was skipped, then it must let the task finish.
Child agents may read orientation but never update the root task's state.
What ships with it: 11 files
36.4 KB alongside SKILL.md, 2 of them executable
agents/
- openai.yaml255 B
scripts/
- chatrail.pyruns7.0 KB
tests/
- semantic/01-goal-change.md1.0 KB
- semantic/02-side-task.md1.0 KB
- semantic/03-proof-correction.md1.0 KB
- semantic/04-true-no-change.md1016 B
- semantic/05-unapproved-ai-pivot.md1.2 KB
- semantic/06-cold-return.md1.3 KB
- semantic/README.md1.6 KB
- test_chatrail.pyruns14.6 KB
- PLUGIN-SPEC.md6.5 KB