Answers

How to run multiple Claude Code agents without conflicts

Give all your Claude Code sessions one shared plan and have them claim work from it. On a Develosaur board, starting a task claims it for that session: another session that tries to start it is refused and takes a different task, and a claim expires if its session goes quiet. Develosaur coordinates tasks, not files, so give parallel sessions their own git worktrees or branches.

Steps

  1. Add the server for all your projects:
    claude mcp add --transport http --scope user develosaur https://mcp.develosaur.com/v1/user/mcp
  2. Open one terminal per agent, each in its own git worktree, and start Claude Code in each. Run /mcp once to sign in.
    /mcp
  3. Give every session the same instruction:
    Work the develosaur board: claim the next task, finish it, then take the next one.
  4. Watch the board: each task an agent has started shows who holds it.
  5. When a session ends, have it hand off so the next session starts where it stopped:
    Hand off on the develosaur board.

Try it without an account

Paste this into your agent. It builds a temporary board you can keep later:

Read https://mcp.develosaur.com/llms.txt and use it to build me a develosaur board for my project

Questions

What stops two sessions taking the same task?

Starting a task claims it. A second session that tries to start the same task is refused, the refusal names the holder, and the session moves on to other work.

Does Develosaur stop two agents editing the same file?

No. It coordinates tasks, not files. Run parallel sessions in separate git worktrees or branches.

Can I try it without an account?

Yes. Paste this into an agent that can fetch URLs: "Read https://mcp.develosaur.com/llms.txt and use it to build me a develosaur board for my project". It builds a trial board you can keep later.

Related

Other answers