Launch settings already carry an allow-list of tools, so a connector you tick can be added to it by name, and the others simply stay off it.
Return to the point your agents stopped at.
Claude Code and Codex, side by side on your Mac. See what ran to the end, what is waiting on your answer, and where the next step begins.
Join the beta listPrivate beta · macOS
Read what came back. Take the next step.
What finished while you were away, and what still needs a decision, waits in Catch up. Open a result to read the reply, check the work, and pick what comes next.
HomeIdeas storage
Since you left
Ideas storage
Your ideas are saved with the project. 4 files changed. Checks passed.
Open thread
Your ideas stay with the project, even once Dervo is closed.
- Wrote the ideas table and its migration.
- Wired the saved ideas into the sidebar.
- Confirmed ideas come back after a restart.
4 files changed · Checks passed
Ready for reviewWhatever you decide lives in this thread.
Say what you want next. Home knows where it goes.
A single request can join a chat you already have, or open a fresh one. Home decides where the work belongs, and the agent works there. Recent requests stay one click away, so Home keeps room for the next catch-up.
Add search to Ideas storage, chase the Connector picker, and write up the release notes.
Opened Ideas search and continued Connector picker. Release notes will start when a slot opens.
Ideas searchNew chat · ProductRunning · 1 min
Connector pickerExisting chat · ProductStarting
Release notesNew chat · ReleasesWaits for a slot
What would you like to do?
Finds the right chat or starts a new one
Threads pick their own names. Workstreams sort themselves out.
The moment you send your first message, the thread gets a name and a place. Local rules do it, not a model, so titling a chat never costs a call and nothing goes off your machine. Rename a thread by hand and it stays yours — dervo leaves it alone after that.
-
“What I really want is to watch this run and see the orchestrator working in real time so I can tell where it gets stuck.”
becomes
Orchestrator real time -
“how about a new connector picker please”
becomes
Connector picker
Claude hits a usage cap. See what it left behind.
Once Claude Code runs into its usage limit, the thread lays out the stopping point, the files it touched and the step after that. If the run ended on a clean tree, a single press hands your original request to Codex. Replies from both agents sit in one thread, so you can see what each of them did.
- Asked
- Let me choose, per project, which connectors Claude Code may use.
Inside Full access, give me a way to say which connectors Claude Code may use per project. Everything on unless I change it.
Claude ran into its usage limit
The work can continue in Codex.
- Asked
- The request exactly as you typed it.
- Files
- No changes in the tree.
- Stopped
- Right after
FullAccess.tsx. - Next
- First the allow-list, and the picker after that.
Hand off to CodexHold for Claude · 4:00 AM
Hand off automatically in this project from now on
2:14 AM
Codex took over at 2:20 AM, after Claude’s usage limit.
Picking up your request: first the allow-list in launch settings, then the picker in FullAccess.tsx.
Agents propose new rules. You decide which ones stay.
Whenever a run picks up something about your project, it sits in Knowledge as a lesson. An agent sees none of it until you press Approve. After that it becomes a rule for every task here, and both Claude Code and Codex begin with it.
What agents begin with
Each Claude Code and Codex task in this project begins from the files, rules and notes listed below.
Waiting for you3An agent sees nothing here until you approve it
Make sure the plan files are committed before a plan step begins.Lesson
- Why
- The plan files for Ideas storage were checked in git and had not been committed.
- From
- Claude Code, in Ideas storage, when its run finished · 17 Sep
- Becomes
- Rule 5, applied to all tasks here
ApproveEdit firstDismiss
Let builds use SIGINT at whatever it ships with.Lesson
Proposed by Claude Code, in Beta plan screen · 18 Sep
Every run leaves a record. Both agents, one Mac.
-
Status from the run record.
Catch up reads the records your runs saved and writes you a summary. Open any thread to see the replies, files and checks it stands on.
-
Claude Code and Codex, both in view.
Each thread says which agent did the work, and Home keeps track of both.
-
On your Mac.
The agents do their work inside your project folders, and Dervo stores the record of each run on your Mac.
Read this first.
The snags that tend to show up in your first hour, so nothing catches you out.
Import only the chats you want.
Pick which Claude Code and Codex conversations on this machine to bring in. Anything you start fresh in Dervo builds its own record from zero.
Your Mac can’t go to sleep.
The agents run on your Mac, so sleep stops a run in its tracks. Dervo won’t hold the machine awake on your behalf.
The Home chat works with a Claude account.
As things stand, Home can only split work in projects that were set up with Claude. The threads it files are free to run on either Claude Code or Codex.
Handoff expects a clean stop.
Hand off to Codex won’t start if Claude’s run left changed files.
Runs on the accounts you already have.
You sign in with your own Claude Code or Codex account, and your provider’s usage limits still apply.
Join the beta list.
Dervo is in private beta on macOS, and the first builds go to people on the list.
We built Dervo because we were running Claude Code and Codex across a handful of projects and kept losing track of which one was waiting on us. If that sounds familiar, join the list and tell us what you’d want it to do.