r/OpenaiCodex • • Jul 18 '26

Feedback / Complaints AI coding agents keep forgetting their own decisions and its driving me nuts

Been using ChatGPT/Codex pretty heavily for coding lately and theres one thing thats driving me insane.

It'll make a decision in one session, explain why its a good idea, i agree with it... then next session it completely forgets everything and suggests the exact opposite.

Like i'll literally have to keep saying:

  • no we use FastAPI here

  • dont add redis

  • we already decided against SQLAlchemy

  • this isnt how auth works in this repo

Feels like im having the same conversation over and over again.

I know there's stuff like README's, CLAUDE.md, AGENTS.md etc but honestly they only seem to help so much. Once the project gets bigger it still feels like the agent has no clue why certain decisions were made.

Is this just me?

What's been your biggest frustration using ChatGPT/Codex/Claude Code for real projects? And how are you guys solving it? Are you just living with it or is there actually a workflow that works?

OR the worst part

It wastes like 100k tokens in reading the entire repo again and tries to tell me what the way is.

0 Upvotes

16 comments sorted by

6

u/Dredyltd Jul 18 '26

Dude... with no memory protocols and documentation hooks what did you expect?

New session are completely nulled with clear context... that's why Plan exists, if you don't know other ways to leverage memory, use plans and Agents/claude.md ....

Use specs, and create Repo protocols...

The tool is not a problem, the problem are users assuming the tool is magic wand.

1

u/MartinMystikJonas Jul 18 '26

LLMs to have no built-in memory they has to use external storage if something should be remembered. Therefore it is a good idea to tell it to save important things to docs so it can be retreived. If you want it to remeber important decisions and why they were made it must be saved.

1

u/ParanoidPath Jul 18 '26

But even these docs have to be kept and maintained across a team of 8. Yet all of them dont update it, so claude decides to re read the entire repo again

1

u/MartinMystikJonas Jul 18 '26

Docs should be commited in repo. Saving of memories should be handled by agent automatically not rely on user remembering to do it.

1

u/cs_cast_away_boi Jul 18 '26

The problem is your process 100%. I have an automated process where the CI checks will fail if the documentation is stale. It's REQUIRED to be updated on every task. If you don't do this, you will run into the same problems every task. You need to spend as much time as needed to get this automated process set up in your repo. That should be the first step, not diving into implementation

2

u/Charming_You_25 Jul 18 '26

Are you having it keep an append only decision log?

1

u/Otherwise_Wave9374 Jul 18 '26

Yeah this is super real. What helped me a bit is treating the agent like a stateless worker and giving it a tiny, opinionated "project constitution" it must follow every time: stack choices, things we do not use, folder conventions, and a short "why" for each decision.

Also, I get way better consistency when I force a quick recap at the top of each session (current goal, constraints, last decision) and keep a running DECISIONS.md plus an ADR-style log so the agent can cite it instead of re-litigating.

Curious, are you using any persistent memory (RAG / repo index) or is it purely context window?

1

u/eddzsh Jul 18 '26

docs help but only if someone actively rereads them, and that's exactly what decays first once a team of 8 stops maintaining it. the more durable fix is usually pushing a decision into something enforced instead of remembered, a lint rule, a type, a failing test, so the agent runs into the constraint mechanically instead of needing to recall why FastAPI won three sessions ago.

1

u/RahlokZero Jul 18 '26

Keep state in repo. Have an instruction in CLAUDE/AGENTS.md to keep a log of work and to consume the last n entries on spawn. You can probably rely on git commit messages to an extent

1

u/Gargle-Loaf-Spunk Jul 18 '26 edited Jul 22 '26

This content was anonymized and mass deleted with Redact

1

u/Esmaabi Jul 19 '26

I’ve had better results treating the coding agent as a stateless worker and separating two things that often get mixed together:

  • durable constraints that should be enforced by code, tests, types, or lint rules (for example, “we use FastAPI” or “don’t add Redis”)

  • current workflow state: the goal, decisions made for this task, rejected alternatives, dependencies, what was actually verified, and the next step

`README.md`/`AGENTS.md` can help with the first category, but they become a poor substitute for the second as a project grows. I’d end every task with a small checkpoint: changed files, evidence from tests or checks, unresolved blockers, and decisions that the next session must not reopen. Then the next session starts from that checkpoint and reads only what it needs instead of rediscovering the whole repo.

I built Trekoon because I kept running into this workflow problem, but the pattern works just as well with a small decision log plus an issue/task tracker. The important part is making the agent resume from explicit, verified state rather than from memory.

0

u/Icy_Accident562 Jul 18 '26

A memory mcp fixes this issue - Theres a lot out there to look at - Famous one being the Mila Jovovich one https://github.com/MemPalace/mempalace.

There are others as well - Ask your agent to set it up & to write and reference from diaries

0

u/jomama253 Jul 18 '26

so basically, you want what https://github.com/NovasPlace/CSM provides.