OPEN SOURCE. ON YOUR MACHINE.

Your agent has work.
You have your own.

Give your AI agent a private desktop.
Keep your desktop, your focus, and your flow.

Development checkout · Apache-2.0 ·No telemetry

You work at your own desk while an agent uses separate desktop application windows beside it — Your desktop. Your rhythm.The agent’s own workspace.

THE PROBLEM

One desktop.
Two things competing.

When an agent works on your screen, its clicks, windows and typing get in the way of yours. You end up waiting for your own computer.

You should both be able to keep working.

Separate spaces. Same machine.

Native apps in a separate desktop.

Watch. Pause. Step in.

See the work, then take the controls when you need.

Watch

01 / 04

Open the viewer to see the agent’s private workspace while your own desktop stays yours.

Pause

02 / 04

Pause the session to stop new agent actions. Take a look before the work continues.

Take over

03 / 04

While paused, use the viewer to interact with the private workspace yourself.

Resume

04 / 04

Resume the session when you are ready for the agent to continue.

A workspace of its own.

Run native applications in the agent’s private desktop.

Illustration of a text editor and image editor on a private desktop

Application windowsPrivate display

Bring your agent.

Connect a tool-capable agent host through MCP or the CLI.

MCPCLI

Orbit

One agent. A clear chain of control.

Your agent gives instructions. Orbit manages the workspace.

Your agentMCP or CLI

Orbit brokerLocal session manager

ViewerOptional: watch and control

Desktop workspacesNumbered private desktops

Application windowsMove a selected window

Instructions go from your agent through Orbit to its workspace.

Agent actionsOptional viewer connection

From setup to your first task.

Three steps. The essentials are right here.

01
Install on your machine.
Use the commands below. The installer checks what your system needs.
Go to installation
02
Connect your agent.
After installation, run this in your terminal. It prints configuration to paste into your agent host’s MCP settings; it does not connect the host for you.
sbar-orbit connector-config
03
Give it a first task.
Ask your connected agent to inspect available applications, then work in a private desktop. Existing desktop applications remain on hold.
sbar-orbit applications
This command lists installed executable paths and available usage metadata without launching applications. Read the reported limits before choosing an application.

Orbit does not collect usage data. Your agent tools and applications still make their own network requests.

Developer reference (English)

START LOCAL

A place for your
agent to begin.

Install Orbit, connect your agent, and open its first workspace.

Full installation reference (English)

In your terminal

git clone https://github.com/M7MMAD-OMAR/sbar-orbit
cd sbar-orbit
./install.sh

Bun is required. Linux also needs user cgroup delegation. Private desktops currently require the Fedora setup.

Development checkout

Limited: private desktop tests on Fedora. Native desktop control on Windows and macOS is not implemented or measured.

The private desktop runtime uses a shared Linux resource budget. Installation on another system does not establish native desktop support. See support tiers.

Native owner handoff is on hold. Do not enable owner input or load the native plugin. Read the native hold.

BUILT IN THE OPEN

A little coffee.
More room to build.

Orbit is free and open source. If it makes your workday a little better, you can support the person building it.

Always optional. Always appreciated.

Your agent has work.You have your own.

One desktop.Two things competing.