The missing control plane around coding agents
CompozyOS starts from an increasingly familiar mess. A developer can launch Claude Code or another agent in seconds, but continuous work needs much more than a prompt. Someone must preserve sessions, isolate workspaces, schedule jobs, route approvals, hold credentials, record artifacts, expose status, and recover from failures. Teams often build this layer from shell scripts, terminal multiplexers, cron entries, and conventions that only one person understands.
CompozyOS puts those responsibilities into a home-scoped daemon. Sessions, tasks, Loops, memory, permissions, and agent activity live beyond any single terminal or browser connection. A CLI, web interface, HTTP and server-sent events, Unix sockets, MCP, and native tools all read the same daemon-owned state. That shared source of truth is the project's best idea. It avoids the common failure where a web dashboard says one thing while a background process has moved on.
The project calls itself an operating system for agents. That is inflated terminology, but the scope is closer to an application runtime than a simple wrapper. It manages lifecycle, persistence, automation, extension trust, and communication between agents. It does not provide the underlying intelligence. You still install and authenticate a supported ACP-compatible CLI such as Claude Code, OpenClaw, or Hermes.
A small local core with substantial responsibilities
The first-run path is reasonable. Install the beta binary through the verified shell installer, npm's beta tag, an explicit Go release tag, or source. Run compozy install, start the daemon, enter a repository, and create a session using an agent definition. State is local by default and backed by SQLite unless a configured provider or extension owns an external boundary.
That is enough for an evaluation, not a complete operational setup. Provider credentials and each CLI's own home-directory policy still matter. Agents live in global or workspace directories, and each can carry MCP configuration. Global settings, workspace overrides, explicit flags, permissions, and runtime rules form a hierarchy that operators need to understand before permitting unattended changes. The doctor and structured JSON output are helpful because automation can verify state rather than scrape friendly text.
Remote access is deliberately separate through Compozy Gateway. That keeps a local daemon from becoming network-visible by accident, but it also means remote supervision is another service and security boundary to configure. Peer discovery and delegation through Compozy Network add more possibilities, along with more identities and receipts to inspect. Start local and single-user before opening those surfaces.
Loops, sessions, and extensions fit real work
A session is durable agent conversation and activity. A Loop is reusable automation that can run on a schedule, webhook, or trigger with no terminal attached. Authored task files remain Markdown with typed frontmatter, then the runtime imports them into durable tasks for Loop execution. This gives a team reviewable files in git and inspectable runtime state instead of hiding the whole workflow in a database.
The extension model is similarly deliberate. Extensions declare versioned resources and behaviors, while the daemon retains discovery, trust, lifecycle, and hook control. Go and npm SDKs match daemon versions, and generated manifests reduce drift between code and packaging. The same runtime can expose tools through MCP, which lets another agent manage sessions and resources without a custom one-off adapter.
Compozy Network lets agents discover peers, exchange typed messages, delegate work, and close tasks with receipts. That is more accountable than vague agent-to-agent chat. Still, teams should treat every automated handoff as policy design: which agent may call which tool, where it may write, when a person must approve, and what evidence counts as completion. CompozyOS supplies objects for those answers, not the answers themselves.
The v0.3 migration is a reset
The largest buying warning is not hidden. The README says v0.3 is beta, v0.2.15 is deprecated, and the older line receives only critical fixes. The migration guide goes further, calling v0.3 a hard cut rather than an in-place compatibility release. Runtime databases, command names, extension contracts, and review behavior do not carry forward automatically.
Many old commands have new shapes or no equivalent. TUI run attachment, bulk run purging, task validation, provider-backed review fetching, PR polling, auto-push behavior, and several parallel or recovery flags were removed or deferred. No live configuration migrator ships in the beta. Old extension SDK users must port their work, while programs importing the v0.2 Go library need to pin it or redesign against current interfaces. This is honest documentation, but it makes CompozyOS a risky foundation for a workflow that cannot absorb change.
The active issues are concrete reminders of beta status. Issue #365 describes a Codex ACP process failure that leaves a valid transcript readable through CLI recap but makes normal UI reopening return an internal error. Issue #370 reports inconsistent skill resolution for extension-published agents. Image attachments are proposed in issue #366, so a user cannot yet expect ordinary paste, drag, or picker handling for screenshots and mockups.
Health is excellent, maturity is not
The repository was pushed on August 13, 2026. Beta.13 was published on August 11 after a rapid sequence of v0.3 prereleases, while the latest non-prerelease remains v0.2.15 from July 17. The six-item open count combines issues and pull requests. Several issues were created or updated on August 13, which shows immediate project activity rather than a quiet queue.
Documentation is unusually thorough for such a young system. The README explains ownership boundaries, installation channels, config precedence, extensions, skills, and the daemon model. Separate installation, provider, gateway, protocol, CLI, and migration material answers the next layer of questions. The migration guide's explicit list of removed behavior is particularly valuable.
CompozyOS is worth a serious trial when agent operations already feel like infrastructure. Its architecture recognizes the unglamorous parts that make autonomous work safe and observable. The current beta is best used on disposable or well-backed-up workspaces with explicit approvals. Wait for v0.3 stable if your priority is compatibility and predictable upgrades rather than early access to a stronger runtime model.