The command menu lags on big projects. Make results show up as you type.
ClaudeOpus 5.5 · working 1m 12s
Thought 6s3 steps
Reading the command menu6 files
Ranking matches as you type2 files
Running the command menu tests
Running
pnpm test command-menu
Commit+14−3
Message Claude…Say it during this turn…
Opus 5.5HighAccept edits41%
Rewrite the homepage hero so it says what studio does in one line.
ClaudeOpus 5.5 · 52s
Thought 4s+2 −2 in 1 file
The hero now says what studio does in one sentence: Studio turns a folder into a working app. The line under it gives the next step, and the download link stays where it was.
Changed 1 file+2−2UndoReview
Commit+2−2
Message Claude…Say it during this turn…
Opus 5.5HighAccept edits12%
Let’s make onboarding feel more thoughtful. Help people connect their first project, then give them a clear next step.
CodexGPT-6-Astra · 1m 36s
Thought 7s+8 −2 in 1 filetests passed
Reading the onboarding flow4 files
Writing the welcome screen
Edited
Welcome.tsxsrc+8−2
Running the onboarding tests12 passed
The welcome flow is ready to review. It uses the existing components and keeps the first run focused on one decision at a time.
A calmer first five minutes
A real welcome. A short introduction gives people a place to start.
One clear next step. Connect a project, then open a conversation.
Keyboard support throughout. Move between choices without leaving the keyboard.
The changes are in src/Welcome.tsx. You can review them alongside this conversation.
Commit+8−2
Message Codex…Say it during this turn…
GPT-6-AstraHighAsk for approval18%
More than just threads.
Billing page
Working
Message from the thread "Plans migration" (id 4b7e2c90-6f1d-4a38-b5c2-9e0d71a3f845):Show details
ClaudeOpus 5.5 · 5s
+52 in 1 file
Built against user.subscription: plan, card, and invoices. Trial users see when their trial ends instead of an empty invoice list.
Changed 1 file+52UndoReview
Commit+52
Message Claude…Say it during this turn…
Opus 5.5HighAccept edits18%
Communication across threads.
One agent asks another before it builds, and the answer lands in both threads.
TasksNew task
In progress1
Cache dashboard queriesPerformancestudiojust now
Ready for review2
Create the welcome flowOnboardingstudiojust now
Polish the project pickerOnboardingstudiojust now
Backlog3
Render transcript rows by blockPerformancestudiojust now
Defer font and icon loadingPerformancestudiojust now
Write useful empty statesstudiojust now
Plan, review, ship.
Turn a conversation into tasks, weigh the approach with more than one model, and read the diff where the work happened.
Simplify the design tokens
Working
openorc/design-tokens-2c91f0WorktreeThis MacRenamePinSnoozeNew subthreadForkOpen in new windowResolveDelete
Move every color, radius, and spacing value into one tokens file.
CodexGPT-6-Astra · 2m 4s
Thought 8s+12 −4 in 3 filestests passed
Every color, radius, and spacing step now comes from one tokens.css. The old per-component values are gone, and nothing outside this worktree has changed.
Changed 3 files+12−4UndoReview
Commit+12−4
Message Codex…Say it during this turn…
GPT-6-AstraHighAsk for approval18%
Parallel work, without collisions.
Give a thread its own worktree and branch. Agents work side by side without touching each other’s files.
Changes
Welcome.tsx
studiosrcWelcome.tsxSave
1import { ProjectPicker } from './ProjectPicker';
2import { Button } from './ui';
3
4export function Welcome() {
5 return (
6 <main className="welcome">
7 <h1>Make yourself at home.</h1>
8 <p>Connect a project to start building.</p>
9 <ProjectPicker />
10 <Button onClick={startConversation}>
11 Start your first conversation
12 </Button>
13 <KeyboardHint />
14 </main>
15 );
16}
Write code yourself.
Open a file beside the conversation, make the change, and save. The agent sees what you changed on its next turn.
Pick it up from Slack.
Mention your personal bot in a channel. Your agent works on your computer and replies in the thread.
Fix the flaky upload test42 msgsAdd the pricing table18 msgsTidy the auth middlewareimported
Bring conversations forward.
Import Claude Code and Codex sessions and continue them with their history intact.
Watch it work.
Built for the agents you already have. Bring your subscriptions, API keys, and favorite coding agents.
Your setup stays yours.
Your accounts and agent configuration stay as they are.
CodexClaude CodeOpenCode
Keep your provider setup
Choose from eight coding agents for each conversation, using the sign-ins, API keys, and configuration you already have.
DecisionKeep the design tokens in one fileLessonRun the size check before pushingCommandpnpm test --filter core
Carry the useful context
Keep decisions and lessons in optional shared project memory, so the next task starts with what you already learned.
A desktop workspace for coding agents. Conversations, tasks, project context, and code review stay together across your projects.
Can I use my existing agents?
Yes. OpenOrc works with the Codex, Claude Code, OpenCode, Oh My Pi, Cursor, Pi, Antigravity, and fx tools you already have installed, through their own sign-in and configuration. Provider subscriptions and API usage stay separate.
Where does my work live?
Projects, conversation history, tasks, and project memory are stored on your computer. Each agent’s requests go to that agent’s provider, under its data policies. So do conversation titles, the code explanations you ask for, and run summaries once you turn memory on, unless you choose another provider in settings.
Does saving a task start work?
No. A task waits in the backlog until you start it. Discuss it first, then begin when the approach is settled.
Can I review changes before they ship?
Yes. The Changes panel sits beside the conversation. Read the diff, ask for another pass in the thread, then commit, push, or open a pull request when your Git setup supports it.
Can I use OpenOrc from my phone?
Yes. OpenOrc for iPhone pairs with OpenOrc on your computer and connects to it directly, over your network or Tailscale, encrypted end to end. Follow and answer threads, start new ones, and ship their changes. The agents still run on your computer, unless you run a thread in the cloud.
Does scheduled or Slack work run while OpenOrc is closed?
No. Schedules and Slack run on your computer, so keep OpenOrc open and your computer awake for them. The phone app needs your computer too, unless it reaches a cloud brain.
Can agents keep working while my computer sleeps?
Yes, with Codex, Claude Code, OpenCode, or Oh My Pi in a cloud thread. Cursor, Pi, Antigravity, and fx run on your connected computer. A cloud thread runs in a sandbox on your own Vercel or Agent37 account, which bills you for it, and its changes sync back to a worktree on your computer. Set up the cloud brain too, and your phone can follow and start cloud threads while the computer sleeps.
Every agent.One workspace.
Start a conversation with the agents you already have, and keep every decision and review in one place.
