Skip to content

An operating system for AI agents

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 for macOS
curl -fsSL https://compozy.com/install.sh | sh
Open the runtime docs

Verified installer · macOS and Linux  ·  Desktop for macOS and Linux · CLI for macOS, Linux, and Windows

An always-on agent's main session with its While you were away card

Runs the agents you already use.

CompozyOS starts the agent CLIs you already have as durable sessions you can see, steer, and hand off.

15

built-in integrations

Claude CodeOpenAICodexCursorGeminiOpenCodeOpenCodeGitHub Copilot
Qwen CodeKimiOpenRouterMoonshotxAIVercel AI Gateway

Your subscriptions and API keys stay yours. CompozyOS resells no model access.

See supported agents

The problem

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.

claude
$ claude
Waiting for your input…
was this the payments repo?
codex
$ codex
Allow command? [y/N]
▌
cursor
$ cursor
Editing checkout/retry.ts
Applying 14 changes…
claude
$ claude
Session expired.
$ tmux attach -t 4
codex
$ codex
Rate limited. Retrying in 42s
$ crontab -e
One sessions board

CompozyOS replaces the pile, not one tool in it.

Always-on

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.

The Agents view: always-on and on-demand agents, each with a face and what it is doing now

Check-ins

On a schedule, the agent reviews its project in a hidden, read-only session. A quiet check costs no model call.

An agent's heartbeat page: next check, today's quiet checks, and why each one stayed silent

Sources

Point it at what it should watch: new GitHub issues from an extension, or a script you approve.

An agent's Sources list watching new GitHub issues in a repository

Reports

Reports land in its main session. Come back after a day away and one card sums up what happened.

A While you were away card: ten quiet hours, two decisions, with a check-in timeline

Proposals

Pick a proposed action, or let the agent do it without asking, up to a daily limit you set.

Two proposals from the agent, each waiting for someone to pick it

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.

Create an always-on agent

Check-ins need Claude, Codex, or OpenCode.

Use cases

CompozyOS takes the jobs you keep doing by hand.

Dev

Triage new issues as they land

An always-on agent watches new GitHub issues. It proposes what to do; you pick.

Dev

Deliver a spec while you are away

A conductor splits the work into slices. Each slice runs in its own worktree.

Dev

Review a change until the round is clean

A reviewer finds, an implementer fixes. Findings land in a file you can open.

Ops

Leave a briefing waiting every weekday

A schedule starts an agent with nobody watching. Every run is recorded, with retry on failure.

Ops

Keep release checks as claimed work

Each concern is a task an agent claims. Runs close with evidence.

Ops

Wait for a person before a sensitive action

A tool call can require approval before it runs. Waiting work rises to Needs you.

Community

Developers have been running it for months.

From the beta program · Dec 2025 – Feb 2026

“This tool is spectacular.”
Fabio Vedovelli
“At work, employee of the week is going to be Compozy.”
João
“I left it running and went to a family barbecue.”
Jefferson Veloso
  • —on GitHub

  • MITlicense

  • 78releases

  • Local-first

Supervise

Details that matter.

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

Agents hand work to each other, not to you.

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.

A session with its three subagents open and running, and nested child sessions in the sidebar

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

Comes with what you would otherwise build.

Agent work that outlives the terminal

Fork a session, continue it with another agent, rewind to a checkpoint, or steer it mid-turn.

A running session with Fork from here on each message and Queue, Steer and Interrupt in the composer

And the details

Later

Park a session with a reason and a date.

Folders and bulk actions

Group sessions, then move or archive them together.

Provider usage (experimental)

See subscription limits and when they reset.

One-click update

Update the app and the runtime from the menu bar.

Vault

Keep secrets out of your config files.

Hooks

Run your own code on daemon events.

Skills

Give agents reusable instructions from any source.

MCP sign-in

Sign in to MCP servers and attach them to agents.

Model catalog

Curate the models each provider offers.

Health

Spot stuck or unhealthy sessions.

Loops

Loops stop when the goal is verified.

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.

The Loop editor: a graph of source, action and control nodes that branches on a route
  • Bounded by design: every Loop carries an iteration cap.
  • A human gate parks the run until someone approves, requests changes, or rejects.
  • Seven named endings: done, no-op, blocked, failed, exhausted, stalled, canceled.
  • The same run from the web, the CLI, and HTTP.

No Loops ship by default. Write one, fork one, or install an extension that ships one.

Read the Loops guide

Automations

Put agent work on a schedule or an event.

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.

A scheduled automation: when it starts, what it asks the agent, and its recorded runs

Built to be built on

One install. The daemon already has a place for it.

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.

The Marketplace by category, with one-step Add

From the catalog

GitHub InvertocatGitHubLinear LogoLinearContext7NotionSentry
PlaywrightStripePostHogPostgresSupabase

Side by side

Every piece, side by side.

Synara, T3 Code, Hermes, and OpenClaw each prove demand for part of the system. CompozyOS ships those parts in one product.

CompozyOSSynaraT3 CodeHermesOpenClawDIY stack
Runs the agents you already usePartial
Always-on agents that check in on their ownPartialPartial—
One board by who owns the next stepPartialPartial——
Loops, schedules, and triggersPartialPartialPartial
Approvals and auditPartialPartialPartialPartialPartial
Local-first and MITPartial

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

Install CompozyOS. Start one session.

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.

  1. 1

    Pick a provider

    compozy install

    The verified installer opens this for you.

  2. 2

    Start the daemon

    compozy daemon start

  3. 3

    Open a session

    compozy session new --agent general --name first-run

    from the repository you want to work on

Keep every agent running.

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