Run two coding agents in the same folder and eventually they edit the same file and undo each other's work.
In orc each one gets its own branch and its own copy of the code. Right now three are building three features, and none can touch another's files.
#ClaudeCode#AIcoding
Shipped in orc: ask "by the way".
A quick question while the agent is mid-task, answered on the side, without adding a word to the main conversation.
Keep the answer there, or drop it into your next prompt.
#ClaudeCode#buildinpublic
@ATown_Jonesy The btw sees the whole conversation so far, so it knows what the agent is doing. Basically it uses /side in codex and /btw in claude behind the scenes. But it provides extra stuff like
1. quoting back
2. multiple btws
3. follow up in btw
and a good UI.
@AvatarsMuse The btw sees the whole conversation so far, so it knows what the agent is doing. Basically it uses /side in codex and /btw in claude behind the scenes. But it provides extra stuff like
1. quoting back
2. multiple btws
3. follow up in btw
and a good UI.
AI made writing the code the fast part.
Everything around it is still on me: running it, testing it, reviewing it, answering the agents when they get stuck.
I write less code now. Mostly I unblock the agents that do.
#AIcoding#buildinpublic
It runs on the Claude or ChatGPT subscription you already pay for, and your code never leaves your computer.
Free while it's in early access, on Mac and Windows. I'd love to hear what breaks.
https://t.co/6gBnd0E95Q
I've been building orc. It runs several coding agents at once, Claude Code and Codex, each on its own worktree.
Running six agents is easy. Knowing which one has been stuck for ten minutes is the hard part.
So orc puts every agent waiting on you in one list.
#ClaudeCode#Codex