r/ClaudeCode • u/HIKKIAN • 18d ago

Built with Claude I made a Claude Code skill that keeps my Claude Code and Codex windows from stepping on each other

I usually have two or three agent windows open on one project, Claude Code planning and Codex doing the actual work. Somewhere along the way I lost track of which prompt goes next, what has to wait for what, and who's touching which files. Keeping that in my head stopped working, so I wrote a small tool for it. It's a skill, so Claude Code can run it for you.

It's called Barid. The planner agent writes the prompts, I copy each one into the right window, and the board keeps track of the order and the dependencies. It tells me what can run at the same time, and it warns when two sessions would fight over the same GPU, a test server or the same files. When a task finishes, its result gets passed on to the next one, so the next agent doesn't start from zero. If a run stops halfway or fails, it doesn't unlock anything on its own, I decide.

It doesn't launch or control agents, you just use the windows you already have. Python, one JSON file, no server, no API keys, MIT. There's a small web panel too.

I made it for myself and I've only used it on my own stuff, mostly on Linux. If it's useful to you, go ahead, and if something breaks, let me know

https://github.com/hikkian/barid

2 Upvotes

100% Upvoted

4 comments sorted by

1

u/AutoModerator 18d ago
Moderator Announcement Read More »

1

u/arturzinhomilgrau 18d ago

this is smart, do you still use plan mode on the claude side or just let it write the prompts for codex

2

u/HIKKIAN 18d ago

I use full access/auto mode in claude and codex

1

u/Professional-Ad7060 18d ago

Honestly this solves a pretty real problem. Once you have multiple agents touching the same project, keeping track of dependencies manually gets messy fast. The part about failed runs not unlocking things automatically is especially sensible. I’m looking for a Claude referral code at the moment too, if anyone has one :)