DarnlyNew agents and new models come out every few weeks, and plans run out at different times. Lots of vibecoders use two or three agents. The trick is to keep what matters out of any one tool, so switching is just opening a different app.
1. Put your instructions in AGENTS.md
AGENTS.md is a plain file in the root of your project with notes for any coding agent: how to run the app, what not to touch, how you like things done. Codex and Cursor read it. For Claude Code, add one line to CLAUDE.md: @AGENTS.md. Now one file teaches every agent.
2. Keep your bugs in the project, not in a chat
A bug you described in last week's Cursor chat is gone when you open Claude Code. Keep bugs in files instead: a BUGS.md the agent ticks off, or a folder of reports. How to keep a list of bugs.
3. Use tools that don't belong to one agent
Each agent now has its own browser: Claude in Chrome, Cursor's Design Mode, Codex for Chrome. They're useful, but the way you report bugs with each one stays behind when you switch. A bug capture that saves to your project works with all of them.
Darnly is built for that. You press Option+Shift+B, click the broken part and say what you expected. The report lands in .darnly/inbox/ in your project. Setup writes the AGENTS.md note, a /darnly command for Claude Code and Cursor, and in Codex you just say "fix my Darnly bugs". Change agents whenever you like. Your bug list comes with you.
4. If your code isn't on your computer
For apps built in the cloud, Darnly's optional cloud inbox holds your bugs, and any agent that can add an MCP server reads them at https://api.darnly.dev/mcp. Setup for Claude Code, Cursor and Codex.
5. Switch in one step
Open the new agent in the same project folder and say: "Read AGENTS.md, then fix the bugs in .darnly/inbox/." That's it. It picks up the same instructions and the same list.
Want your bug list to travel with you? Add Darnly to Chrome, it's free. Or read why Darnly when your agent already has a browser.