You run several agents at once.
Each one works in its own copy of the code, and none of them can see the others.
Run coding agents in parallel without them breaking each other's work.
Point anywhere. Click, and everything makes room.Tap anywhere, and everything makes room.
Try the commands.
Click one, or type your own (press /).
~/shop
Sample output, shortened
One changes what another relies on.
Each copy passes its own tests. The break shows up only when you merge.
28%of parallel agent pull-request pairs touched the same code.Orchestraty's public scan of 34 repositories.
Orchestraty tells the other agent first.
Before its next edit, the agent that's affected gets a short note, and adapts.
Watch it happen13/15breaks avoided when the agent was told.Phase 0 trial.
0false notes in the same trial.Phase 0 trial.
What it notices
The bigger the overlap, the louder the note.
Who hearsThe session using it, before its next edit. If callers stay behind, you get one line at push.
And what do you see?
$ git push
orchestraty: 1 caller(s) of charge still use its old form (checkout). Run: orch status
Your agents hear all of this. You don't.
One line, only when something is left. It never blocks the push.
In the agent's sessionA note, before its next edit.
orch status or orch uiEvery session, and where they overlap.At
git pushOne line if callers are still on the old form. It never blocks.Built for developers first.
Your terminal, your agents, your git. Nothing new to run: it starts with your first session and stops when idle.
Agents
Claude Code supported
Codex built
Antigravity built
Any agent through git
Under the hood
Python, in full
TypeScript, opt-in
Hooks · MCP · git
Windows · macOS · Linux
Apache-2.0
Claude Codeworktree checkout
> Read shop/cart.py
> Edit shop/cart.py
Orchestraty: 1 strong overlap
charge (shop/payments.py) was changed by claude in refunds; shop/checkout.py uses it
>
1 other session
A status line, and a band only when it's strong. Claude Code 2.1.287 or later.
Made for everyone who builds with AI.
You and your agents, on your own machine.
Nothing leaves your machine.
No AI model in the loop.
It asks before it changes anything.
Fair questions.
Does my code leave my machine?
No. There is no account and no telemetry. The only network use is opt-in: orch remote on fetches cloud agents' branches from your repository's own remote.
Does it use an AI model?
No. Every note is filled in from a template with facts from git and the code, and it never runs your agents for you.
Which agents does it work with?
Claude Code is supported, and tested with the real agent. Codex and Antigravity are built but less tested. Any other agent or editor is seen through git: its changes count, but it gets no notes.
Can it block my push?
No. At most it adds one line when callers of a changed function are still on the old form. The push goes ahead.
What does it mean if I get no note?
That Orchestraty found nothing, not that nothing is wrong. It reads static calls, so dynamic calls aren't seen.
How do I take it out?
orch restore takes the hooks out, and orch uninstall takes everything out. It backs up every settings file before it changes one.
Phase 1 · early access
Try it in five minutes.
pip install orchestratyorch initorch ui --demoNeeds Python 3.10+, git 2.38+ and a recent Claude Code. Works best today on Python code.