The note was there. Nobody opened it.
You, or your session, wrote a careful handoff: what's done, what's left, what to watch out for. The new session never read it. It started fresh, rediscovered half of it, and missed the other half.
Writing is easy. Delivery is the hard part.
A new session starts with whatever it's handed at startup and nothing else. If nobody hands it the note, or tells it where to look, the note might as well not exist.
Usually the delivery is you, pasting it in.
What doesn't work.
Writing more notes. That adds to the pile nobody opens.
Longer notes. The important line is now harder to find.
Putting everything in the project file that loads automatically. It grows until nobody reads it, the model included.
What actually helps.
Most of this isn't us.
Pick one fixed place for the newest handoff, and make reading it the first step of every start.
Use a startup hook to load it automatically. Claude Code's SessionStart hook can add text to a session before its first prompt, so delivery doesn't depend on anyone remembering.
Keep each handoff short and about what changed, so reading it first is cheap.
Each session wakes up and reads its own orders.
On 13 October the operator put the gap plainly, and the record agreed: a written order reached a session only when the operator pasted a prompt telling it to look.
The fix was to have each session wake on a schedule and read its own orders first. The product version is planned for the runner rather than any one coding tool, so it works for every model, not only one vendor's command. Writing the handoff itself is becoming automatic too.
| What was measured | What the record says |
|---|---|
| the operator, on the gap | “No one reads what you wrote automatically. I have to tell them to read it.” |
| the fix in use | each session wakes on a schedule and reads its orders first |
| the product version | a wake built into the runner, not tied to one vendor's command; planned |
| recorded | 13 October 2026 |
| where it's from | Vinculum's own project record, which runs on Vinculum; the hook detail checked against Claude Code's documentation on 14 October 2026 |
Where a shared memory fits.
Vinculum stores the handoff where every session can find it, and a session that reads its orders first picks it up.
Making that read happen at every start, without a schedule or a hook you set up yourself, is the part we're still building.
Common questions.
How do I load a handoff automatically in Claude Code?
A SessionStart hook runs when a session starts or resumes, and anything it prints is added to the session's context. Point it at your newest handoff file.
Where should the handoff live?
Somewhere fixed that every session checks first. A file in the repo works for one machine; a shared store works across several.