Developers using AI daily: what’s the one thing you still do manually every single session?
For me it’s explaining what I was doing before I opened the chat.
Asked how people carry context between AI coding tools. Almost everyone said a notes file in the repo.
The part most people skip: what already failed.
Without it, the next model happily retries the same three fixes you ruled out an hour ago.
Question for people using more than one AI coding tool:
When Claude Code / Cursor / Codex hits a limit mid-task, how do you carry the context over to the next one?
Copy-paste the chat? A notes file? Just start over?
@actvox Agreed, the dead ends are noise, except for a one-line “tried X, didn’t work” so nobody retries it. I’d keep it in the repo root. Most tools look there first.
@radialbuild “Starts at attempt six” is the key part. Logging what failed matters more than logging what worked, because otherwise the next model tries the same fixes again.
Claude Code hit its usage limit mid-task again.
Switched to Gemini and spent 15 minutes re-explaining the bug, the files, what I’d already tried.
The model isn’t the bottleneck anymore. Context is.
@automater_ai Agreed. The trick is getting it written before the limit hits, not after. Do you have the agent update it every step, or only at the end?