Driving
Handing over
Sessions end; the project does not. Three conventions carry what was learned across the gap, so the next session does not re-ask what this one settled.
A coding-agent session has no memory of the last one. The method compensates with three write-it-down conventions, all of them already wired in by rcf init. Your part as the driver is small but decisive: notice the moment something worth keeping was settled, and ask for it to be written down.
The knowledge space
rcf/knowledge/ is the project's memory. The convention: notes/ holds internal facts, decisions, gotchas and runtime truths, the "CI runs Node 22, not 24" class of thing; docs/ holds user-facing prose the project surfaces; one topic per file. The agent is instructed to write what it learns there every session, and to grep the space before asking you something it should already know.
When a session settles something the hard way, say so:
Make a note of that before we finish: the seed data has to load before the first search works.A conversational nudge for the agent to write a learned fact into the project's memory. There is no single CLI for this; the agent writes the note itself.
Where the note lands and how it is filed is the agent's business. The test of a good knowledge space is a boring one: the next session does not re-ask.
The operator profile
rcf/.identity/profile.md describes you: name, role, working style, and the preferences that hold for this project. The agent reads it at session start if it exists. It is per-clone and gitignored by default, so it can hold things you would not put in the shared repository, and a colleague's fresh clone carries no profile of yours, which is by design; they write their own.
Worth putting in it: how much detail you want in updates, what you never want done without asking, the vocabulary you use for the product. The scaffold leaves a template there; filling it in is a few minutes that pays back every session.
The next-session pointer
For the gap between sessions mid-build, the agent is instructed to write a handover doc, the queue state, the item in progress, the next actionable id, and to add a one-line pointer to it in CLAUDE.md, outside the managed markers so upgrades never overwrite it. A fresh session follows the pointer and resumes without re-elicitation.
That handover is written automatically when the agent runs out of reliable context, but you do not have to wait for that. Ending a session deliberately, all it takes is:
Let's end the session here and hand over.Ends the session deliberately. The agent writes down where things stand so a fresh session picks up from where this one stopped, without re-asking what this one settled.
Whether the next driver is you tomorrow, a colleague next week, or a fresh session in an hour, they start from what this one knew. The knowledge-space and operator-profile rules are lines in the harness block, which publishes the same text the agent has been given.