Two months later, nothing figured out twice

Solo buildersSolo founder returning to a paused project

We paused a product for a client project. Coming back, nobody remembered why the queue worker was split from the API, or what was half-done.

How do I stop my AI agent redoing work and re-deciding things on a project I paused two months ago?

If ArcRoom was in the project before the break, the decisions (like why the queue worker was split from the API), the answers and the steps your agent saved are still in the playbook, and a new session reads them before it works. The last-run note then says what was in progress when the work stopped. Expiry limits set with arcroom rule --idle-days decide which old answers stop being handed over.

Also asked as: I forgot why I built my project this way. How do I find out? · How do I see what was half-done before a long break from a project? · Can an AI agent remember a project's decisions after months away?

The work

The last-run note says what was in progress when the work stopped.

ArcRoom keeps
  • Last-run note
  • Decision
  • Recall
  • Expiry rule
The next agent gets

Last session (63 days ago): "move email sending to the worker", stopped mid-way.

Step by step

  1. The last-run note says what was in progress when the work stopped.
  2. Decisions and answers still in the playbook come back with recall.
  3. Expiry settings (arcroom rule --idle-days) decide which memories expire, so old noise doesn't come back.

What the agent sees

Last session (63 days ago): "move email sending to the worker", stopped mid-way.
Decision (Aug 2): worker separate from API. Why: long jobs were timing out requests.

Compared with today's tools

Git history + README

Read commit messages and the README, or ask an agent to summarise git log for the last few months.

Setup
0 min
Ongoing
a few hours reading, or about 50k tokens of agent summarising

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

Commits say what changed but rarely why; ArcRoom keeps the decisions and the half-done last session.

Where it stops

Memories past their expiry limit are gone, and code that changed a lot makes old answers stale.

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