Dev
Triage new issues as they land
An always-on agent watches new GitHub issues. It proposes what to do; you pick.
An operating system for AI 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.
curl -fsSL https://compozy.com/install.sh | shVerified installer · macOS and Linux · Desktop for macOS and Linux · CLI for macOS, Linux, and Windows

CompozyOS starts the agent CLIs you already have as durable sessions you can see, steer, and hand off.
15
built-in integrations
Your subscriptions and API keys stay yours. CompozyOS resells no model access.
See supported agentsThe problem
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.
Always-on
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 limit you set.

Agents keep notes on purpose. Nothing is extracted behind your back.
Always-on next to On-demand: keep a few agents watching, start the rest when you need them.
Check-ins need Claude, Codex, or OpenCode.
Use cases
Dev
An always-on agent watches new GitHub issues. It proposes what to do; you pick.
Dev
A conductor splits the work into slices. Each slice runs in its own worktree.
Dev
A reviewer finds, an implementer fixes. Findings land in a file you can open.
Ops
A schedule starts an agent with nobody watching. Every run is recorded, with retry on failure.
Ops
Each concern is a task an agent claims. Runs close with evidence.
Ops
A tool call can require approval before it runs. Waiting work rises to Needs you.
Community
From the beta program · Dec 2025 – Feb 2026
“This tool is spectacular.”
“At work, employee of the week is going to be Compozy.”
“I left it running and went to a family barbecue.”
—on GitHub
MITlicense
78releases
Local-first
Supervise
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.
Orchestrate
A session delegates to subagents and watches their progress live. An agent can end its turn and wake when a pull request's checks finish, another session settles, or a command exits.

Worktrees give parallel agents their own checkout of the same repo.
The branch, the pull request, and its checks sit on the session.
Continue a session with another agent CLI when one runs out.
Built in
Fork a session, continue it with another agent, rewind to a checkpoint, or steer it mid-turn.

And the details
Loops
A Loop is a named contract: a goal, a way to verify it, and a stop. The daemon runs it unattended and always ends it honestly.

No Loops ship by default. Write one, fork one, or install an extension that ships one.
Read the Loops guideAutomations
Schedules, runtime triggers, and signed webhooks live in one place. Every run is recorded, and finished runs leave your session list on their own.
A briefing waiting for you every weekday at 08:30.
Manage the same job from the web, the CLI, or HTTP.

Built to be built on
Extensions, plugins, and MCP servers share one Marketplace, by category, with one-step Add. An extension brings skills, agents, tools, hooks, and check-in sources into the same registries your agents already use.
Write one in Go or TypeScript, with React for views: init, build, validate, dev, publish.

From the catalog
Side by side
Synara, T3 Code, Hermes, and OpenClaw each prove demand for part of the system. CompozyOS ships those parts in one product.
| CompozyOS | Synara | T3 Code | Hermes | OpenClaw | DIY stack | |
|---|---|---|---|---|---|---|
| Runs the agents you already use | Partial | |||||
| Always-on agents that check in on their own | Partial | Partial | — | |||
| One board by who owns the next step | Partial | Partial | — | — | ||
| Loops, schedules, and triggers | Partial | Partial | Partial | |||
| Approvals and audit | Partial | Partial | Partial | Partial | Partial | |
| Local-first and MIT | Partial |
Why it holds: one runtime, one state model. Sessions, agents, approvals, and runs are core objects, so nothing has to be glued together.
Checked against the public documentation of Synara, T3 Code, Hermes and OpenClaw on November 10, 2026. Partial means the docs cover part of the row.
Getting started
Download the desktop app, or install the runtime with the verified installer, Homebrew, npm, or Go. Today's experience is technical: a terminal, a local daemon, and one config file.
Pick a provider
compozy install
The verified installer opens this for you.
Start the daemon
compozy daemon start
Open a session
compozy session new --agent general --name first-run
from the repository you want to work on
See every session, let always-on agents watch your projects, and step in only when one needs you.
curl -fsSL https://compozy.com/install.sh | sh