Last night's work, not redone tonight

Solo buildersSolo founder, one product, evenings and weekends

We were building the billing page for a side product. At 1 a.m. the session ended halfway: Stripe webhook done, the plan-upgrade screen not started. The next evening a fresh Claude Code session knew nothing, and the first 20 minutes went to re-reading files and asking what we were doing.

How do I stop my AI agent redoing last night's work in a new session?

With ArcRoom, the steps your agent finished last night are in the playbook. Tonight's agent reads the playbook before it works, so it skips what is done and starts at the unfinished step. You also get a last-run note: what was asked, what was edited and whether it closed cleanly.

Also asked as: Why does Claude Code forget everything I did in yesterday's session? · How do I resume yesterday's AI agent session without re-explaining the task? · Can a new Claude Code session see what the last one edited?

The work

Every turn's metadata (prompt, files touched, commands) is recorded as it happens.

ArcRoom keeps
  • Last-run note
The next agent gets

your last session in this project (19 h ago) stopped mid-way.

Step by step

  1. Every turn's metadata (prompt, files touched, commands) is recorded as it happens.
  2. When the next session opens in that folder, ArcRoom puts a last-run note in front of the first prompt: what was asked, what was edited, whether it closed cleanly.
  3. The agent starts from the unfinished step instead of exploring the repo again.

What the agent sees

ArcRoom: your last session in this project (19 h ago) stopped mid-way.
Asked: "add plan upgrade after the Stripe webhook"
Edited: api/webhooks/stripe.ts, db/plans.sql
Treat its work as unfinished.

Compared with today's tools

Recap file (NOTES.md) the next session reads

Before closing, ask the agent to write what is done and what is next into NOTES.md, and tell the next session to read it first.

Setup
0 min
Ongoing
~5 min per session, if you remember at 1 a.m.

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min (npx arcroom init)
Ongoing
None

Close when you remember to write it; ArcRoom writes the note even when the session dies or you forget.

Where it stops

The note is a summary of steps, not the exact state of a half-run command. Exact resume is on the roadmap.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in solo builders