Windows & macOS · Native · Open source

A native terminal workspace that any agent can drive.

Your agents, files, diffs and local app. In the workspace with your running terminals.

Windows x64 + WSL2 · Apple Silicon, macOS 14+

Windows is unsigned. macOS is ad-hoc signed, not notarized. Your OS may warn on first launch. Installation help

Compi, working on itself.Agent / diff / terminal
An agent reviewing notification changes beside a code diff and terminal inside Compi
An agent reviews Compi’s notification changes.Release 0.5.0 ↗
Explore the workspace Agents · Editing & review · Persistent work

01Shared controls

Your agent can drive
the workspace.

It can make room for another task, read a terminal’s output or open your app beside the work. You see the same workspace.

See the CLI reference ↗
Workspace commands · from a Compi shell
01 / Inspectcompi --json pane list
02 / Make roomcompi split --right
03 / Open the appcompi browse http://localhost:3000
Real CLI commands, not a playback of the workspace above.
The browser command needs a local app running on port 3000.

See what’s running.

Read pane IDs and program-reported state. Capture another terminal’s output without taking over its view.

Make room for the next task.

Create a terminal, split the view or rearrange existing panes. Running processes stay where they belong.

Bring the result to you.

Open a file, a diff or a browser pane for review. No mouse-driving needed.

Use whichever agent can run shell commands. Compi supplies the controls, not an agent harness.

02Edit · review · run

The work around
your terminal.

Write the notes. Review the changes. Keep the build running. You don’t have to leave the workspace for each one.

GPUI Markdown notes beside browser documentation inside Compi
Markdown notes beside a live documentation page.01 / 03

01 / Write & look things up

Notes beside
the source.

Edit ordinary Markdown, switch to Read mode and keep a documentation page or local app beside it.

Browser inspection and automation come from your agent’s own browser tools. Compi provides the pane.

GPUI Markdown research notes beside browser documentation inside Compi
Markdown notes beside a live documentation page.

02 / Review the result

The agent’s work.
Your review.

Bring up a diff beside the conversation. Inspect working changes or a past commit, stage changes and commit.

An agent reviewing notification changes beside a code diff and terminal inside Compi
Agent review, code changes and a running terminal.

03 / Keep an eye on it

The build is
still right there.

Keep terminal output visible while you inspect the machine it’s running on. Arrange the panes around the task.

Compi host resource Monitor beside terminal compilation output
Live host resources beside a terminal build.

03Leave · keep running · return

Close the window.
Keep the work.

The window is a view into running work. Close it, reopen it and reconnect to the same shells.

01

Leave it running.

Your terminals live in Compi’s background server. Closing the window doesn’t end their processes.

02

Know when you’re needed.

Supporting programs report when they need attention or finish. Compi can notify you instead of making you check every tab.

03

Return to the terminal.

Click a notification to focus its terminal, or reopen Compi and pick up the same running work.

Restarting the server or rebooting ends running processes. Window persistence is not reboot survival.

Notifications, in the app.Recorded in Compi
Notification settings and browser panes.Open video ↗

In-app and Windows system notifications, with optional Windows sounds. macOS notifications remain unverified and have no sound in 0.5.0. Release details.