Matrix OSMatrix OS

Matrix OS

Set up and use Matrix OS, a persistent cloud computer for coding agents, with guides for the web app, CLI, desktop, integrations, and billing.

Maintained by the Matrix OS team. Product instructions are updated with the supported workflow.

Cloud coding computer

Matrix OS is a persistent cloud computer with an AI kernel — for developers who run AI coding agents.

Sessions keep running after your laptop closes. Reach your computer from the web shell, CLI, mobile, or desktop.

Matrix OS is a real computer hosted in the cloud. It has a terminal, a file system, persistent shell sessions, and an AI kernel. You clone repos, run tests, launch coding agents, and leave long-running work running — then pick it up from any device.

"The biggest bottleneck in AI-assisted development isn't the model — it's losing context every time your environment restarts." — Matrix OS founding team

A computer, not a dashboard

Matrix is not a chat window bolted onto a cloud service. The AI is the kernel: it has access to the shell, files, integrations, and skills, and running sessions can continue after you close the browser, while your Matrix computer is running.

Why Matrix

Your cloud computer should stay awake, remember context, and move with you.

Local development keeps asking the wrong machine to do the work. Matrix gives developers a persistent computer in the cloud so agents, terminals, previews, and context keep running without laptop sleep hacks or keep-awake apps.

Always-on compute

Keep terminals, dev servers, previews, review loops, and agents alive after the laptop closes.

Agents keep running

Claude, Codex, Pi, OpenCode, and Hermes work inside the same cloud machine instead of fighting local sleep.

Work from anywhere

Move between the web shell, CLI, and upcoming Mac/iOS apps without moving the project.

Shared with teammates

Hand off a running workspace, terminal session, repo, or preview without recreating local setup.

Context in one place

Files, repos, settings, skills, logs, integrations, and agent history live in the Matrix workspace.

How it works

Provision your Matrix computer

Sign up at app.matrix-os.com, choose your power level and region, complete billing, and wait for your computer to provision. Takes a few minutes.

Always-on computers start with Starter. Builder and Max add capacity for parallel work. See billing and plans for current limits.

Open the web shell

The web shell at app.matrix-os.com is your primary interface. Open Terminal, authenticate GitHub with gh auth login, clone your repo, and start working.

Connect from your laptop

Install the matrix CLI and run matrix login. Attach to persistent sessions, sync files, and run coding agents — all against the same cloud computer.

Launch a coding agent

Start Claude, Codex, Pi, or OpenCode in a named session. The agent runs on your Matrix computer. Detaching leaves a running session on that computer; reconnect to an available session from another surface. Plan limits, sleep, restarts, and process exits affect whether work is still running.

Apps For Your Work And Life

Open Apps to use the personal web apps installed on your Matrix computer, or ask Matrix in Chat to build a tracker, planner, or dashboard. Review apps in Web Canvas, Web Desktop, or Electron Desktop and check that sample data saves and reopens. See the Apps guide for device support.

Matrix App Gallery is planned curated discovery for Matrix apps. Read the gallery scope for what is available today and which sharing features are still planned.

Where to go next

What Matrix is

Persistent sessions:

  • Closing a browser or detaching from Terminal does not itself end a running session.
  • Long builds, agent runs, and test suites can continue while your Matrix computer is running. Reconnect to see their current state.
  • Computer sleep, restarts, plan limits, and ended processes can interrupt work. Check the session status after reconnecting.

One computer, four surfaces:

  • The web shell (app.matrix-os.com), the matrix CLI, the mobile app, and the desktop app all connect to the same machine and the same sessions.
  • Workspace files live on that computer. Sign in on each surface and reconnect to available sessions instead of creating a separate copy of the workspace.

AI at the kernel level:

  • Hermes runs on your Matrix computer. Background availability depends on your plan and setup. Coding agents — Claude, Codex, Pi, OpenCode — install as tools on that computer and run in named sessions.
  • The AI kernel has access to the shell, files, apps, and integrations with your permission.
  • Saved conversations and workspace files provide context for later work. Check the outcome of an interrupted task before starting it again.

Your files are yours:

  • Your home directory, repos, and workspace data live on your Matrix computer.
  • The platform handles routing, auth, and recovery — your data stays under your control.

How is this guide?

On this page