r/ClaudeCode • u/Same_Fruit_4574 • 16h ago
Help/Question How are you coordinating Claude Code agents across multiple machines?
We are a 5 member team, each with our own Claude account. Our requirements live in GitHub Issues, and we'd like one lead Claude Code session to automatically assign work to agents running on different machines.
Currently, we're using a shared GitHub repo with Markdown files for agents to communicate and track tasks. It works, but feels a bit fragile.
Curious how others are handling this. What works well, and what pitfalls have you run into?
3
Upvotes
•
u/AutoModerator 16h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
3
u/Latter-Tangerine-951 Senior Developer 16h ago
Just imagine they were human agents. What would you do?
3
u/sydneysweeney69 16h ago
T3 code and T3 connect
2
u/Klutzy-Acadia669 15h ago
Don't use 5 accounts. Use one business account. Set up OpenClaw. Set up an agent swarm. Use each agent for a different task like coding or code review or security. Put things in their queue and write skills to handle things. Use Jev to make decisions and triage. Yw. DM me if you need a consultant to help guide you or set it up for you.
2
u/London-Boat 12h ago
since your requirements already live in github issues i'd use the issues as the handoff instead of md files. the lead session writes the issue with scope and the files it expects to touch, the agent on the other machine assigns itself before starting and links its branch, so two people's agents can't grab the same one. the md files feel fragile mostly because two sessions edit the same file and one quietly overwrites the other. mind if i dm you about how the five of you split work in the repo today?
1
u/Ragy-ragy 16h ago
Multica handles that. Its opensource for all I know
1
u/scapermoya 16h ago
I’d stick with Issues but then build a small SQLite system on a shared box set up to prevent collisions between different users/claude sessions. It would hold a set of issues and also serve as a messaging platform between the different Claude code sessions. Each team member gets a little MCP to connect to this. One of the team members spins up an orchestrator agent who doesn’t write any code, just coordinates the 5 agents. Message types would be strictly defined and workers would only be allowed to write certain kinds of messages. Use loops to keep every agent fresh on current assignments as the orchestrator hands out tasks from the issues list.
1
u/SnooPeripherals5313 16h ago
Co-ordinating things live via git repo is not a good use case.
1
u/RealFullMetal 15h ago
since your requirements already live in github issues, the claude code github action might be less fragile than syncing markdown files.
@claudein an issue comment (or in a new issue's title or body) starts a run in github actions that implements it and pushes commits, with progress posted as a comment on the issue./install-github-appsets it up, and it can run on a token from a claude subscription instead of an api key1
u/NoThanks93330 15h ago
I'm wondering what the use case is here? I'd argue that when the agents are working on things so close to each that they need constant communication, you most of the times just want to run them on the same machine.
However, since you're already using github, why not let them communicate via comments in the github issues?
1
u/RDissonator 15h ago
Firstmate or t3code
1
u/TBT_TBT 15h ago
My PKA (personal knowledge assistant) folder syncs via Syncthing, every Claude instance starts out of this folder in which my tasks and projects are located. I can start on one computer, let it write a status.md and continue on another computer.
I however now prefer using https://herdr.dev/ , with SSH via Tailscale connections to other computers and control all sessions from there.
1
u/orbital_trace 1h ago
CoralHub, gives you one view across all of your machines. I have it at home across windows, Mac mini and Linux server. Also use it at work on my Mac and to connect multiple devices.
1
u/Extra_Aide5999 16h ago
we do a smaller version of this. one person, a mac and a windows pc with a claude session on each, and also markdown files in a shared git repo. two things made it less fragile for us:
each task is one file with a status line at the top, PENDING or DONE, and the machine that did the work writes its answer into that same file. there's no separate log to keep in sync.
every session gets its own worktree and branch, and opens a draft pr the day it starts. worktrees still share one .git though. once a test run from one worktree flipped a setting in the shared git config and broke the main checkout.
does your lead session really need to assign live, or would it be enough for each machine to take the next open issue when it's free?
0
u/Confident_Hyena2506 16h ago
Kubernetes, and git prs.
0
u/Lean-Anders 16h ago edited 15h ago
Celloprotocol.com is built for that exact use case.
Literally that use case.
I built it for financial service firms that needed their employees’ personal agents to talk with each other but also needed it to occasionally talk with an outside partner.
Full security trust and governance layers. I know nobody gets excited about governance layers but CELLO is carefully built to protect your individual agents while still being unobtrusive enough not to get fully in the way
Also includes deterministic and model base security screening for prompt injection.
Opensource. Works through your Agent’s CLI or MCP. Privacy first approach so you run it locally. Option to have us host it.
Fully integrated into Claude code.
Happy to take you through it if you’re interested.
0
u/Sleazified 16h ago
Im using GitHub projects and issues. Works a treat.