compozy/compozy

The autonomous control plane for your agents.
See and steer every Claude Code, Codex, and Cursor session.
Always-on agents check in on their own, and you step in only when one needs you.
Download ·
Docs ·
Marketplace ·
Changelog ·
Blog
The bottleneck stopped being the model. It became managing the sessions. Run Claude Code, Codex,
and Cursor in parallel and you end up with five terminals, a prompt typed into the wrong one, and
no clear view of which agent is waiting on you. Keeping them working means gluing loops, cron,
webhooks, and approvals together by hand.
CompozyOS replaces the pile, not one tool in it. It runs the agent CLIs you already have as
sessions that outlive the terminal, keeps every one of them visible, and calls you only when a
decision is yours. Loops, schedules, permissions, and approvals come built in, so there is no
stack to assemble around the agent.
## Install
bash
curl -fsSL https://compozy.com/install.sh | sh
The verified installer pins the latest release and checks its Sigstore provenance before it
installs the binary on macOS or Linux. Prefer the desktop app?
Download it for macOS or Linux.
Homebrew, npm, Go, or from source
bash
# Homebrew
brew install compozy/compozy/compozy
# npm
npm install -g @compozy/cli
# Go, with the tag shown on https://github.com/compozy/compozy/releases/latest
go install github.com/compozy/compozy@
# From source
git clone https://github.com/compozy/compozy.git
cd compozy
go build -o ./bin/compozy .
The CLI runs on macOS, Linux, and Windows. The
installation guide covers installer
flags, Linux packages, verification, and managed updates.
Then start one session, from the repository you want agents to work on:
bash
compozy install # pick a provider (the verified installer opens this for you)
compozy daemon start # start the local daemon
compozy session new --agent general --name first-run
The Quick Start continues through the
first prompt, live attachment, inspection, and cleanup. Today's experience is technical: a
terminal, a local daemon, and a config.toml.
## Every session, sorted by who owns the next step
Every session lands in Needs you, Working, Waiting, In review, or Done. Needs you is the only
loud colour on the screen, so you know where to look.
Worktrees give parallel agents their own checkout of the same repository.
The branch, the pull request, and its checks sit on the session.
Handoff continues a session with another agent CLI when one runs out.
Approvals hold a tool call until a person allows it, and waiting work rises to Needs you.
## Agents that check in on their own
An always-on agent has a name, a face, and one main session per project. It reviews its work on a
schedule, stays quiet when there is nothing to say, and calls you when something needs a decision.
Check-ins. On a schedule, the agent reviews its project in a hidden, read-only session. A
quiet check costs no model call.
Sources. Point it at what it should watch: new GitHub issues from an extension, or a script
you approve.
Reports. Reports land in its main session. Come back after a day away and one card sums up
what happened.
Proposals. Pick a proposed action, or let the agent do it without asking, up to a daily