My AI sessions kept forgetting each other's work and burning my limits. How do you handle it?

My old way of building with AI stopped working.

My Claude and Codex limits were gone in 2-3 days. Codex kept forgetting what the other sessions had done. For three weeks I couldn't ship one feature, and I kept forwarding messages between the two AIs by hand, like a courier.


In the end I set up a harness: one shared space where every AI session, in any tool and on any computer, starts by knowing what we decided, what we tried and what's next. Within two days the stuck feature finally worked. Now my limits last the whole week.


I wanted to share this experience and discuss it here on PH. But the full story was too long for one post, so I put the detailed breakdown of how I build (a network where AI agents represent people and companies and talk to each other) and how the harness took our product development to the next level on my Substack:
I'd love to have the discussion here on PH.

So here are the rules that mattered most:

  • Every decision goes into a shared log as my exact quote. Otherwise my "for example" turns into a rule a week later.

  • Every task gets a budget. One night Codex survived 17 compactions without losing the goal, and still burned 75% of my weekly limit solving nothing.

  • Hand over work before the chat is 80% full, and let the next session check what the previous one forgot.

  • "Done" means it works for real users. Green tests only mean "implemented".

I'm still not a programmer, so I'd love to discuss the process here: what you'd do differently and what I'm missing.


What does your AI keep forgetting, no matter how many times you tell it? And what finally fixed it?

3 views

Add a comment

Replies

Best

Not a dev either, and for me it was “already done” that got forgotten. One session checked our plans against reality and three “urgent” blockers had been closed for weeks 🙃

Limits got better once the main chat only plans and reviews, and subagents on cheaper models do the reading. Line ranges, not whole files.

How do you keep the shared log short enough for a new session to read?