You’re halfway through a feature when the agent stops. You open a different one, point it at the same repo, and type “keep going.”
It has never seen the conversation. It only has the files.
This is the most common handoff in agent-assisted development. Same person, same repo, zero shared memory. Whatever you agreed on in chat is gone unless it was written down.
Railspike tries to write it down. Each cycle leaves four files: an assessment, the requirements, a plan, and a summary. The bet is that a fresh agent can read them and continue correctly.
I tested that bet with three real sets of plan files. I only read the files. I didn’t hand them to a live agent.
**Case 1**
The request was to fold two features into the project. The assessment recommended splitting them. The first cycle therefore excluded the second feature on purpose.
A new agent that only sees the original request will try to build the missing half. One that reads the requirements will ask first. Same repo, opposite actions.
**Case 2**
A homepage was finished. Local checks passed. The summary still listed three open gates: review, merge, and live verification. The commit that recorded this changed only the summary file.
Without that list, the next agent is tempted either to redo finished work or to ship on authority nobody granted. One approval had lived only in chat and never made it into the files at all.
**Case 3**
A plan file described a data contract and five completed stages. At the bottom sat a hotfix note that changed the meaning of a field. Nothing was crossed out. The old approval gate was still there.
An agent that treats every sentence as live can reintroduce the old problem. One that reads the file as a chronology gets it right. The file does not force the right reading.
**Before you type “keep going”**
Look for five things:
1. The outcome currently wanted
2. The decisions still in force
3. The next action actually authorized
4. What was actually checked
5. What is still open
A short current-state section at the top of each plan would answer all five. Compress too hard and you lose the exception that matters.
The chat is gone. The files are still there. Whether the next agent notices what they say is the only question that matters.