
Multi-agent runtime on Mac for turning...
Do not treat it as a chat that answers one question. Write one business objective, attach constraints and the material you already have, let the CEO office set the cadence, and let objectives and key results split the work across departments. Research, engineering, creative, growth, security, and operations can move at the same time, and each agent uses its own browser and files. At the end, look for proof: whether a page shipped, whether tests remain, and whether email or payment is connected. The web app is not here yet, and outside payments and email still need you to check budgets and approvals. It fits someone on a Mac who wants a long-running business handed to a group of agents, such as linking a site, distribution, and delivery.
Matrix is a multi-agent runtime on Mac for turning one objective into an agent company that keeps operating. A web app is not available yet. You submit intent, constraints, and files. A CEO office sets the objective, policy, and cadence, then an objectives-and-key-results system splits the work into tasks. Research, engineering, creative, growth, security, and operations can run in parallel. Each agent has its own browser, tools, files, and memory. Built-in runners include Neo Intelligence, Claude Code, and Codex. A task ends with proof such as files, tests, screenshots, a shipped page, revenue, or traffic, and skills plus memory stay for the next round. It also includes site publishing, payments, a budget wallet, and email. A site can use your domain or a matrix.site subdomain.
Difficulty: Advanced
One objective, many departments
The CEO office sets the objective and cadence, and the objectives-and-key-results system splits tasks across departments that run in parallel.
A browser and memory each
Each agent uses its own browser, tools, files, and memory, and departments collaborate through one file system.
Close work with proof
A task has to leave files, tests, screenshots, a shipped page, revenue, or traffic, rather than stopping at a plan.
Site, email, and payments
A product site can go on your own domain or a matrix.site subdomain, with email, a budget wallet, and payments connected.
Ship one site
A founder gives a product objective and source material, has engineering and creative produce the pages, and uses the live site as proof.
Run distribution and follow up leads
A growth department browses and runs distribution, email follows up replies, and a person still sets the budget approvals.
Reuse last round's memory
When the same agent company starts another round, it keeps the skills, decisions, and blockers already recorded instead of restating the whole background.
The official note says it runs on Mac today, and the web app comes later. On the computer you give one objective, constraints, and files, and the system then assigns departments. It is not a chat you finish from a phone message. The Mac client is the current entry, and the web app is not available yet. Each agent can use a browser and files, so the machine has to support that desktop work. You judge the proof at the end, not only a reply.
The page says work closes with proof. Proof can be files, tests, screenshots, a page that is already live, or revenue and traffic. The CEO office owns the objective and cadence, and objectives and key results split that objective into tasks. Proof closes the job, and key results are checked against the original objective. Skills and memory stay, so the next round does not restate the background. Outside payments and email still need you to check budgets and approvals.
Real reviews and feedback from users