Driving
Handing over
The knowledge space, operator profile and handover document preserve project decisions and progress between sessions. They let the next session resume without repeating settled questions.
A coding-agent session does not retain the previous session's memory. Three conventions configured by rcf init preserve it in files. Ask the agent to record decisions or findings that the next session will need.
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 a decision or finds a useful fact, ask the agent to record it:
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.
The agent chooses the note's location and topic. A useful note lets the next session proceed without repeating the question.
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 provides a template. Fill it in so each session uses your preferences.
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 the active agent-instructions file (CLAUDE.md or AGENTS.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.