What Is Optimus Orca? The Build Surface of Optimus, Explained
Optimus Orca is the build surface of Optimus, the AI operating system for founders. It’s a macOS command-line orchestrator that drives 8 or more Claude Code sessions in parallel from a single terminal — each agent working in its own isolated git worktree — so one architect can take down big builds without a dev team, and without breaking flow.
What exactly is Orca?
Optimus is one platform with three surfaces, and Orca is the one you build on. When you sit down at the terminal to make something — a feature, a site, an internal tool, a whole product — Orca is the surface that turns you from one person typing into one architect directing a pod of AI workers.
Concretely, Orca lets you drive 8+ Claude Code sessions from one screen. Each agent gets dispatched into its own isolated git worktree, so eight parallel workstreams never trip over each other. You watch the commits land as they ship. When an agent gets stuck, you harpoon it and Orca recycles the slot instantly with a fresh one. And everything the pod ships reports back to Optimus, so the record of the work is waiting in your portal the moment you step away from the keyboard.
The tagline on the tin is the whole point: Orca helps you flow. Not “Orca answers your questions.” Not “Orca chats with you about code.” It keeps you in the build while a crew does the work in parallel.
Why is it called a “build surface”?
An operating system needs different surfaces for different modes of work. Optimus has three, one crew behind all of them:
- Orca — the build surface. Terminal. For when you’re making things and in flow.
- Ollie — the know surface. Portal. Same orchestrator as Orca, in business-owner form — hand him a mess, he hands it back clean, and everything your agents have done is visible in one place.
- Mako — the go surface. Telegram. For brainstorming and directing work from your phone.
Behind them, Harry — the honey badger — does the heavy lifting in the background when Ollie dispatches it. If you want the deeper concept, read what a build surface actually is in an AI operating system.
What does Orca actually do?
Four things, and they compound:
- Orchestrate. Drive 8+ Claude Code sessions from one UI. Observe and steer every one of them without losing the thread.
- Autopilot. The pod self-advances — it picks up the next task as each one lands, surfaces commits as they ship, and only pulls you in for a real decision.
- Voice command. Brief the pod out loud and let it talk back. Direct a team of agents hands-free, eyes off the screen.
- Harpoon & recycle. A self-healing pod. Kill a stuck agent and Orca reuses the slot instantly, so one bad run never freezes the crew.
How is Orca different from a chatbot?
Not a chatbot. A worker. A chat window gives you text; Orca gives you commits. A chat thread holds one conversation; Orca holds a pod of isolated workstreams, each with its own git worktree and its own receipts. When a chat assistant goes sideways, you start the conversation over; when an Orca agent goes sideways, you harpoon that one agent and the other seven keep shipping.
There’s also the reach question. An agent is only as useful as what it can touch. Every Optimus agent — Orca included — connects to the tools and platforms you already run through one secure gateway, with each connection scoped to your own keys. That’s a patented approach: your agents get the reach of your entire stack, and you never hand your keys to a platform. The full comparison is in terminal agents vs chat UIs.
Who is Orca for?
Founders who are done outsourcing their own product. The architect who has the vision, knows the business cold, and is tired of translating it through ticket queues, agencies, and someone else’s sprint calendar. You don’t need to be an engineer — you need to be decisive. The agents write the code; you own the architecture. If that’s you, start with how to build software without a dev team.
Where does the work go when you’re done?
This is the part single-tool setups miss. Orca isn’t a standalone gadget — it’s one surface of an operating system. Every commit, every shipped task reports back to Optimus. Close the laptop, open the portal, and Ollie shows you everything the pod did while you were in flow. Build in the terminal, stay in the know everywhere else.
FAQ
Is Optimus Orca the same thing as Claude Code?
No. Claude Code is the individual coding agent. Orca is the orchestrator that runs a pod of 8 or more Claude Code sessions at once from one terminal — each in its own isolated git worktree — so you direct a crew instead of babysitting one window.
Do I need to know how to code to use Orca?
You need to make decisions, not write syntax. The agents write the code; your job is the architect’s job — describe the outcome, judge the result, and steer. Terminal basics are learnable fast, and everything Orca ships is reviewable in the Optimus portal.
What platforms does Orca run on?
Orca is a macOS command-line orchestrator. You run it in the terminal on a Mac, and everything it ships reports back to Optimus so it is visible in your portal from any device.
How do I get Orca?
Orca comes as one of the three surfaces of Optimus. You activate the whole crew — Orca, Ollie, and Mako, with Harry working in the background — at activateoptimus.com.