Orbit / Download for Windows

Orbit for Windows

Most tools for running several AI coding agents at once are macOS only. Orbit ships a Windows x64 build of the whole local product, free, with no account.

SmartScreen will warn you, and here is why

Orbit's Windows builds are not code-signed yet. When you run the installer, Windows shows a blue Windows protected your PC dialog. Click More info, then Run anyway.

That warning is not about what the app does. It appears for any executable without an Authenticode signature from a certificate authority. An OV certificate for an individual seller costs a few hundred dollars a year and needs company registration documents, which is a real obstacle for a one-person project outside the US. Signing is on the list. Until then the honest position is that you are trusting a stranger's binary, and you should weigh that.

If you would rather wait, leave your email at the bottom of this page and you will get one message when signed builds ship.

Install

1. Run the installerClick More info, then Run anyway when SmartScreen appears. The NSIS installer puts Orbit in your user profile, so it needs no administrator rights.
2. Point Orbit at a git repositoryAdd a project by choosing a folder that is already a git repo. Orbit never modifies your working checkout; it creates worktrees under your home directory instead.
3. Let it find your agentsOrbit detects the agent CLIs already installed on your machine and sets up presets for them. Claude Code, OpenAI Codex, Cursor Agent, Gemini CLI, OpenCode, GitHub Copilot, Amp, Droid, Aider and Pi all have first-class presets. Anything else you can launch from a terminal also works.
4. Set your verify commandsGive Orbit the lint, typecheck and test commands for the repo. Nothing gets marked ready for review until those pass, so an agent claiming it is done does not become your problem later.

Requirements

What runs on your machine

Orbit is local-first. Your projects, workspaces, tasks and settings live in a SQLite file at %USERPROFILE%\.orbit\orbit.sqlite, and every worktree lives under %USERPROFILE%\.orbit\worktrees\. Your source code stays where it is. If you never turn on the optional cloud, nothing about your work leaves the machine.

Uninstalling is the installer's uninstall entry plus deleting that .orbit folder. There is no hidden state anywhere else.

Windows-specific notes

• Paths in worktrees can get long. If a repo has deep nesting, turn on long path support in Windows (git config --system core.longpaths true) before adding it.
• The portable build keeps its data in the same %USERPROFILE%\.orbit location, so switching between portable and installed keeps your projects.
• Terminals inside Orbit use your default shell. PowerShell, cmd and Git Bash all work; set the one you want in Settings.
• There is no auto-update on the unsigned builds yet. Check the releases page, or leave your email below.

Why parallel agents need worktrees

Two agents editing one checkout will corrupt each other's work within minutes. One stages a file the other is halfway through rewriting, and git status stops meaning anything. A worktree gives each task its own directory, its own branch and its own index, sharing one object store. Ten agents can then run at once without a single collision.

Orbit creates those worktrees, runs one agent in each, watches the terminals for questions that need you, and merges finished work through a single lane so two merges never race. There is no git checkout anywhere in the merge path, so your own working copy is never touched. That design is described in more depth in the docs.

Keep reading

Orbit for macOS · Is Orbit open source?