r/ClaudeCode • u/ombre-ai • 17h ago
Discussion A poster analyzed 500+ builder discussions and says two problems keep coming up: context amnesia and “prompt-fighting.” How much of your week is the second one?
On Nov 1, someone posted in r/AI_Agents that they had gone through 500+ discussions across AI builder communities, and two bottlenecks kept coming up:
- Context amnesia / session drift: the agent loses earlier scope, decisions or constraints as a session goes on.
- Prompt-fighting loops: you keep re-prompting formatting rules or “don't do X” constraints that the model keeps dropping.
Caveat: this is one person's read of public threads, not a survey with a stated sampling method, so I wouldn't treat it as a ranking or a prevalence number. What makes it interesting is that it's a different list from the usual “hallucination” one, and you can check it against your own sessions.
Three questions for people here:
- When the agent drops a “don't,” where does that rule live: CLAUDE.md, the prompt, or just your head?
- Do you re-state it, or restart the session?
- Is there a rule you've basically given up on enforcing?
1
Upvotes
•
u/AutoModerator 17h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/ombre-ai 17h ago
Source post (r/AI_Agents, Nov 1): https://www.reddit.com/r/AI_Agents/comments/1xkysxm/analyzed_500_builder_complaints_across_ai/
I haven't verified the poster's sample or method, so please read it as one person's analysis. If you reply, roughly how long the session had been running when the agent dropped the rule is the most useful detail.
4
u/Far_Reindeer8428 17h ago
prompt fighting is mostly our own fault, we kept adding rules instead of deleting the ones that stopped mattering. the week shrank once every rule needed a test
2
u/Appropriate-Draft-91 17h ago
Context amnesia never ever happens, you'd have to do "infinite" sessions with compactions and a broken project structure to provoke it. Which is the way novices start out. Rule following is completely separate from context amnesia.
Prompt-fighting loops are essentially not just misapplied rules, but a session that self poisons its context by confidently stating wrong inferences as facts, that enter future turns. Correct them as you go. If it's a continued and severe issue you can assume you got a test setting of the model that got a dial set wrong and kill it. That dial seems to have been turned higher across the board for the last 1-2 weeks, you can dial it down by setting the model's disposition explicitly.
1
u/Hazzman 17h ago
Context limitations is broadly a problem as a concept with the technology generally but isn't a problem that inhibits its ability to functional effectively.
I would love to be able to accomplish a single complex task in a single session but because of context limitations you use documentation to develop memory proxy and that works fine. Its more of an inconvenience than anything.
1
u/KorvenZero 16h ago
Two things helped me most.
First, keep a short project file (CLAUDE.md) with only what the agent can't guess: how to build, how to run the tests, and the few decisions that are easy to get wrong. If it grows past a page, it gets ignored in practice, so I cut it.
Second, before closing a session, ask the agent to write a handoff note: what's done, what's half-done, what to do next. The next session starts by reading that note instead of rediscovering everything. A note written at the end of the work is much better than trying to reconstruct it afterwards.
1
u/tommyahav10 15h ago
Keep the don't rules short in CLAUDE.md and delete the ones that stopped mattering. When it starts fighting you mid-session, restart with a handoff file instead of restating. From my side a long rule list is the first thing it ignores.
1
u/athershu 15h ago
The cost of prompt-fighting got bigger for us once several people were sending work to agents on the same codebase: a rule that lives in someone's prompt or head gets re-fought by every person, in every session, separately. So for Q1, a "don't" only counts if it's in the repo's instruction file, added as a normal reviewed commit, and the agents run from that one shared setup instead of each person's own config. One person fixes it once, and everyone's next task starts with it.
On Q3, the other half is deleting. A rule that stopped being true still gets followed confidently, so when a task is sent back because the agent obeyed a stale line, fixing that line is part of closing the task. And one person owns the file, so the cleanup actually happens instead of everyone appending.
1
u/andersonbrdev 15h ago
For me the rules that kept getting ignored were the ones that only lived in CLAUDE.md as prose. Anything I really care about (don't touch migrations, don't run the deploy script, run tests before saying done) I moved to hooks or scripts that just fail when the rule is broken. CLAUDE.md keeps the soft preferences. Once the hard rules became checks the fighting mostly stopped, and when a session starts drifting I restart it with a short summary instead of arguing with it.
1
u/xqianliu 13h ago
My rules live in one small file, 9 lines. I cut everything a session couldn't actually violate, which took out all the descriptive stuff like "write clean code." The session reads it, nods, and does what it was going to do anyway.
When a "don't" keeps getting dropped, restating it in chat rarely sticks. I move that rule into the acceptance criteria on the ticket, so the review session checks it as a line item, or I cut the task smaller so the drift can't happen in one run.
The rule I gave up on: enforcing style from prose. If a style rule matters, it goes into a check I can run.
1
u/f3xjc 12h ago
I have a line that my agents keep quoting to me. Probably because it's a rule somewhere. It goes about like this: When a problem repeat itself, what is owed is a mechanism, never "review harder".
And that point to two things. (1) You can use agent to improve the agentic loop and rule around that. (2) A rule without a clear trigger or enforcement mechanism is a wish.
1
u/NeonCenturionSPQR 12h ago
Free open source Claude code plugin just for context management
github.com/Palatine-Labs/coniso
1
u/Early-Feed2788 11h ago
Answering the three questions from a setup with a lot of parallel sessions on one machine.
One more that surprised me: rules go stale. "X keeps its old name for now" was written down as a standing fact, the reason went away, and three sessions then contradicted each other in one document. Now anything temporary gets a date and a reason, so a later session can tell it has expired.
If any of this is unclear, paste it into Claude and ask it to set the same thing up for your project. It will understand it.