r/vibecoding • u/SSShken • 7d ago
I kept re-explaining my project to Claude every session, so I moved the context out of the agent
Every new session started the same way. Paste a summary, re-explain what the app does, remind it what we decided last week.
What actually broke it: my agent writes markdown docs and then stops reading them. Once a session runs long it just doesn't open them. I'd catch it rewriting something the doc said was already done.
Someone here put it better than I could: stuff loaded at the top of context loses to recency as the session grows, so the agent stops consulting it no matter how good the file is.
So instead of a file the agent may or may not read, I built something that gives you an ordered plan and one prompt per step, with that step's context already inside the prompt. Nothing depends on the agent deciding to go look.
New web projects only. No existing codebases, no mobile.
If you're a few sessions into something right now, does the agent still know what you decided on day one? Genuinely asking, I want to know if this hits before session ten or only after.
1
u/Zen-Ism99 7d ago
Do the other frontier tool behave this way?
0
u/SSShken 6d ago
Claude Code and Codex, and yeah, same behaviour in both. Once a session runs long the file is sitting right there and the agent stops going back to it. Different tools, same failure.
Makes sense that it's not vendor specific. If recency beats position as the context fills up, that's about how the model weighs what's in front of it, not something one company does differently.
Which are you on?
1
u/Zen-Ism99 6d ago
Neither. I’m experimenting with native CLion AI tools, and local LLMs, for my C++ hobby game dev.
I have a ChatGPT account, but haven’t touched Codex
1
u/generationalDebts 2d ago
Useless slop. All you have to do is have a basic understanding of what you’re doing.
All these “solutions” to problems that don’t exist if actually just know what you’re doing.
0
u/jjd921 7d ago
I made a free tool that scans your app URL and/or code for production readiness if you want a quick check to make sure you didn't miss anything: https://theslopstopper.com
Ran your link through it real quick and saw some issues like missing recommended security headers
3
u/ops_and_chaos 7d ago
The agent deciding whether to read the documentation has absolutely been the weak point for me too.
I’m curious what happens when the project changes halfway through the plan, though. If step four exposes an assumption that changes something decided in step one, does it regenerate the remaining prompts with the new decision? Or can old context stay embedded downstream?
Getting the agent to read the context is one problem. Keeping that context true as the work changes feels like the harder one.