01Links
Claude Code
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
Keep separate jobs open across Claude accounts, with Notch showing which account has room to work.
Why I keep it
I use Claude Desktop with Claude Notch because I keep three accounts open and don’t want a usage limit to stop a job halfway. The Code tab runs sessions side by side, while Notch shows each account’s limits, so I can choose where the next job goes.
Each copy has its own data folder, so switching doesn’t mean signing out of another job. I’ve made Claude Notch free and put the setup on the guides shelf; it gives those accounts a visible set of limits and a hotkey to move between them.
How I use it: Three Claude accounts, one notch →01Links
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
02Links
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
03Links
Speak the job, the look and the stack in one brief, so your agent gets the context together.
04Links
Carry a visitor’s voice-agent answers into a call booking, so they don’t have to start again.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.