Ecosystem
DevOS is a set of parts that work together or alone. Of the ten below, 2 are shipped, 3 are partly shipped and 5 are planned. A planned part is not available, and nothing here has a date.
DevOS ADE is free and open source (MIT). Companion, Mobile and the relay are free to download during the beta; paid plans are planned and not yet available. See Pricing for the hypothesis.
Steer the agents on your own computers from your phone: DevOS Mobile (the app) and DevOS Companion (the Mac app that runs the bridge). A paired browser shows the same inbox.
iPhone and iPad are in beta. Android is planned, with no date.
Compared with. Compared with the remote-control features inside single vendors’ agent apps: Control works across vendors and on computers you own. The comparison is on the Compare page.
An agentic development environment you run on your own Mac or Linux computer and open in a browser: chat, Claude Code and a sandboxed terminal, with a budget for each key.
Self-hosted and free. Controlling it from the phone app is planned, not available.
Compared with. Compared with hosted agent workspaces: ADE runs on your hardware and your own subscriptions or cloud account, and you can read the code.
Carries traffic between your phone and your computers without needing the same Wi-Fi. App payloads are sealed end to end.
The relay sees routing, pairing and push metadata. It does not see sealed payloads. Phones paired by older versions use HTTPS until they enroll, and the browser client runs code the relay serves.
Compared with. Compared with a plain tunnel or VPN: a tunnel moves packets; the relay also pairs devices, sends push and lets the app channel stay closed off Wi-Fi.
Members and guests, shared sessions, claims on shared repositories and visibility rules every member can see.
Not built. Today a person can invite others to one Mac as members or guests until an end date; that is not the team plane.
Compared with. Compared with per-seat team plans from agent vendors: the plan is bring your own model, with no markup on model costs.
Limits, approvals and an audit trail for what agents may do and spend.
Shipped: per-key budgets and alerts in the ADE, approvals on the bridge (the first answer wins) and guest scopes with end dates. Planned: a policy engine and an exportable, tamper-evident audit log.
Compared with. Compared with admin consoles in agent vendors’ team plans: those cover their own tool only; Governance is meant to cover every vendor you run.
A credential broker, so agents do not hold your raw keys.
Not built. Today agents on a Mac bridge see an API key placed in their environment. Subscription logins stay in each vendor’s own app. The ADE already gives agents budgeted virtual keys instead of cloud keys.
Compared with. Compared with a general secrets manager: Vault is planned for agent sessions in particular, with budgets and approvals attached.
Where an agent runs: your Mac, a disposable sandbox desktop, or another computer over SSH.
Shipped: sandbox desktops (Apple container or Docker) and SSH computers. Planned: local models; none are supported today.
Compared with. Compared with a single hosted cloud runtime: you choose the computer, and nothing needs to leave your machines.
A shared list of tools, MCP servers and skills a team can approve, with a verified publisher.
Not built, and nothing is signed or curated today.
Compared with. Compared with public tool directories: the aim is a list your team approves, with verified publishers.
Context that sessions and people on a team can share.
Not built. The ADE has a single-user shared-files tool; there is no shared memory between people.
Compared with. Compared with each agent’s own notes file: Memory is meant to be shared across vendors and people.
An open control API and a conformance suite, so any runtime can be steered by the same clients.
A draft exists and is under review. It is not published and nothing implements it yet.
Compared with. Compared with each vendor’s private protocol: an open, testable contract that others can implement.
DevOS