Fire it at Claude, Codex and Gemini at once, read the diffs side by side, keep the winner. Switch it on in Labs.
[ overcli ] · a desktop app over your agent CLIs
Overcli is a desktop app that sits over Claude Code, Codex, Gemini, Copilot and Ollama, on the logins you already have — with your files, an editor and a terminal right beside the chat. When you're ready, agents review each other, work flows, keep shifts and argue as teams, so you come back to finished work.
[ the basics ] · everything you'd expect
Before any loop, it has to be the place you'd chat with an agent anyway — so the everyday turn is clearer here than in a terminal.
agent CLIs, one window
open-source flows to install
new subscriptions or API keys
telemetry — its one call out is an update check
[ loops ] · four loops, one engine
It gets checked, retried, and picked up again — from a single review up to a team on its own branch.
[ review ]
Turn on a reviewer and Codex checks what Opus just wrote — or the other way round. They go back and forth in the conversation until the reviewer is quiet or the round budget runs out, and you read the verdict, not the whole argument.
[ flow ]
Each step runs on the model it needs. A failed review goes to a fix step, not back to square one — and it stops exactly where you told it to. 38 flows in the registry, or write your own in a few lines of YAML.
thinking
plan · reviewstandard
build · fix · testsfast
fetch · shipPaused before ship · talk to any step, then Continue →
[ worker ]
Every morning it reads its journal, decides what's worth doing, and proposes it. It remembers what you reject and steers away from it. It starts on probation, and spends only from a pot you approve once. Publish it to overgo and your whole org can ask it.
↺ tomorrow 09:00 — skips anything you rejected
[ team ]
A coordinator plans who contributes and who challenges. You approve the plan; they do the work on its own branch, push back on each other, and hand you one finished pack.
Then the conversation stays open: ask a follow-up, or hand work back to a member.
[ process ] · a Lab
A process is a series of stages, each a team, a worker, or people who decide. A customer escalation goes from a channel to a reproduced bug, a fix, a yes from whoever’s on call and a reply to the customer — each stage briefed with what every earlier one produced. Draw one, or draft it from an image of a flowchart you already have.
Want it for the whole org? Publish it to overgo → and people ask in Slack instead.
[ stack ]
Services — your API, your front end, your workers, your database — start, watch and log beside the code. When a flow finishes, run its branch for real with one click, try it in the browser, then switch everything back. Pinned services stay where they are. Switch Services on in Labs — overcli offers it on any project that has something to run. Share a stack as a file, with typed credentials turned into named blanks, and import it on another machine; a Tiltfile imports too.
[ editor & terminal ] · why we closed our IDEs
When agents write most of the code, the job is reading it, checking it, running it and shipping it — and all of that is here. The editor, go to definition, the file tree, a terminal, every diff, worktrees, the whole stack running beside it. We build overcli in overcli.
Edit any file in tabs, with highlighting for most languages. ⌘S saves; an open file refreshes when an agent writes to it, and a ruler marks every line it changed.
Go to definition: your project is searched first, instantly — a cheap, fast model is asked only when the search finds nothing. Several matches? Pick one, or Refine.
Find any file or walk the tree, and flip any change the agent made between Diff and File.
A terminal drawer under the chat: a real shell per tab, so the test you want to run is one keystroke away.
[ and more ] · there's a lot in the box
Comparing models, watching your spend, running local models, flows in CI, writing without a repo — the things you reach for between loops.
See all 42 features →Fire it at Claude, Codex and Gemini at once, read the diffs side by side, keep the winner. Switch it on in Labs.
Usage by backend, model and project over 5h, 24h and 7d — so you see what each turn cost.
Group related repos and talk to them as one — the agent edits across them, runs every suite, shows one review.
Tabs and highlighting, HTML and Markdown previews, and .tsx components rendered live with your own Tailwind.
Slash commands, sub-agents, skills, plugins and MCP servers across every backend — copy an MCP server from one CLI to the others in a click.
Browse the catalog, pull and delete in a click, watch the server log and the GPU — cloud or local, same window. Switch it on in Labs.
Run a flow or a worker from the command line on a box you own — or deploy it to GitHub Actions or Jenkins as a generated pipeline.
Open a folder of documents, or describe what you want and start from a prepared folder — with an undo history and flows made for writing.
Create, rebase, merge, push or remove a git worktree from inside the conversation — nothing touches your checkout until you say so.
✓ your existing CLI logins — no API keys✓ Apache 2.0 · no telemetry✓ signed and notarized✓ macOS · Windows · Linux
[ download ] · grab a build
Overcli is in beta, but the macOS builds are now Developer-ID signed and notarized by Apple — they open on a double-click, no right-click ceremony. Windows isn't code-signed yet, so SmartScreen may still flag it. Either way the source is right there; build it yourself.
Stable macOS builds open clean — signed with a Developer ID and notarized by Apple, so there's no Gatekeeper prompt. Windows isn't code-signed yet: SmartScreen may say “unrecognized app” → More info → Run anyway. Rather build it yourself?git clone https://github.com/overcodelions/overcli && cd overcli && npm install && npm run dist:mac
[ faq ]
The app is free. Overcli is open source under Apache 2.0 — no licence to buy, no per-seat pricing, no paid tier holding features back, and no invoice from us. What you do pay for is model usage on the agent subscriptions you already have, which is why every flow step names its own model and why the crew draws from a pot you set.
claude, codex, gemini, copilot, and ollama. Overcli drives the CLIs you already have installed and signed in — it is a window over them, not a reimplementation of them. If you have none of them yet, the start screen walks you through it and keeps watching — install a CLI in a terminal and the app unblocks itself without a restart.
No. Overcli uses the auth those CLIs already hold — a Claude Pro plan, a ChatGPT plan, gcloud credentials, a GitHub Copilot seat, or a local ollama. No API keys to issue, no new billing relationship, no per-seat pricing.
Wherever the CLI you picked was already sending it. Overcli adds no server, no proxy, and no account of its own — it runs the same binaries on the same machine with the same credentials. Pick ollama and nothing leaves the box at all.
None in the app. No analytics and no crash reporting; the only server it contacts itself is GitHub, to check for updates. Conversation history is files on disk you can open in any editor, and you can verify all of that in the source.
Yes — but it is alpha as of 0.17, so treat it as something to trial rather than to depend on this quarter. The same flow YAML runs headlessly from an overcli command line — one shot in CI or on a machine you own — and a flow or a worker cadence can be deployed to GitHub Actions or Jenkins as a generated pipeline. There is no second runtime to certify: the app and the CLI drive the same runner and the same engine, so what you reviewed at a desk is what executes on the runner. It still authenticates the same way, through the CLIs and credentials you already provision.
Three things. A risk scan reads each step's prompt override and tool list before you install, save or run it, looking for credential-file references and for network egress declared as local — a high-severity finding pauses the run. A step's declared tool list is enforced as a real allowlist rather than trusted as a label, so a step that declares nothing no longer keeps everything. And bash, websearch and webfetch require the same approval as pushing or sending, so an unattended worker without a grant for outside actions stops rather than proceeding. On macOS a fourth: flow steps run in a write sandbox, so a step can change its own run folder and the repo's git data but not your dotfiles or other projects.
No — not since 0.16. Documents projects are folders of documents rather than code: Overcli scaffolds one, keeps an undo history for it, and never mentions git in the process. The history underneath is an ordinary repo, so nothing is locked in and any other tool can read it, but nobody is asked to learn it. A folder you already have can be brought in with one button, and any project can be switched between documents and code without moving a single file.
Each agent works in an isolated git worktree instead of your checkout, so you can rebase, merge, or throw the whole attempt away from inside the conversation. Your working tree is never the experiment.
Not without you saying so. Every worker is hired on probation — it may propose, it may not launch, and promoting it is an explicit act you take. The whole crew draws from a single monthly pot you set once; a worker below the waterline skips its shift and journals why rather than quietly overspending. A worker imported from a .worker.yaml always lands back on probation regardless of what the file says, and a shared worker can never ask to run in your working copy.
No. A rendered document preview may run the CDN script it was built from and nothing else — no fetch, no XHR, no sendBeacon — and inlined images, fonts, and stylesheets stop at an allowlist of previewable types, including through a stylesheet's own imports. A dashboard that calls a live API shows no data instead of fetching it, which is the trade for a preview that can't exfiltrate what it can see.
Yes — Apache 2.0, and the repo builds with npm install && npm run dist. macOS releases are Developer-ID signed and notarized; Windows isn't code-signed yet, so SmartScreen may still warn.
[ family ] · over your tools, not instead of them
One window over your agent CLIs — then put them in a loop.
A better git client — and one ticket across many repos.
overdb →Every environment at once — and branches of your data.
overgo →overcli for your whole team — on your own server.