The workspace agent that finishes before a frontier harness has finished thinking.

Spatio is an agent harness with a control plane for your workspace. Ask for anything and it lands as a real artifact in seconds, not a chat reply. When a task needs more than speed, the harness hands it off to the Claude Code or Codex you already pay for, and folds the result back into the same thread.

Download for Mac

The Spatio Agent Control Plane

Agents

The Spatio workspace agent harness.

The Spatio Agent is a harness, not a chat box bolted onto a model. It holds every tool in your workspace, sees the artifact you have open, and acts on real data, running on wafer-scale inference at over 1,800 tokens per second.

When the work turns into real engineering, it hands off to the coding agent you already pay for. No config, no second API bill: if Claude Code or Codex is signed in, Spatio finds it, briefs it, and folds its work back into the same conversation.

Output throughput as measured by Artificial Analysis, July 2026: 1,851 t/s for Gemma 4 31B on Cerebras, the model the Spatio Agent runs; 53–69 t/s for Claude Code’s Opus 5 and Sonnet 5; 61–121 t/s across Codex’s GPT‑5.6 and GPT‑5.3‑Codex. The deep gear is slower on purpose, and it runs on the subscription you already pay for.

Fast gear · runs your workspace
>1,800tok / s

Spatio Agent

The harness we built in house. It drives the loop itself: every workspace tool on every turn, grounded in the artifact you have open, acting on real data rather than describing it.

Hands off to
Deep gear · what you already pay for
50–70tok / s

Claude Code

Already signed in on your machine? Spatio finds it, and hands big engineering to Anthropic’s agent, which reports back in the same thread.

60–120tok / s

Codex

The same handoff to OpenAI’s Codex on the plan you already pay for, working in your repo with the context Spatio hands it.

Features

What you can do with Spatio

  • The Spatio home view: every agent run across the workspace in one sortable table, grouped into Active and Idle, with the repo, driving agent, turn count and date on each row.

    Every artifact in one table

    The home view puts your whole workspace in a single dense, sortable table, the view you already think in. Filter, group and scan across every platform at once instead of hopping between apps to find the thing you half-remember.

  • The Spatio left sidebar with a group called Spatio Fundraising expanded to show the two artifacts nested inside it, a note and a sheet, beside the group detail listing its property schema of status, owner, priority, dates and budget.

    Structure that bends to your team

    Groups are a nestable container for any artifact, shipped with opinionated templates that are offered rather than imposed. Strong defaults when you want them, and a structure you can actually reshape when your team does not work the way the tool assumed.

  • A direct-message thread with the Spatio Workspace Agent, in which it explains that it can see the layout of the workspace (the open tabs, panes and active apps) and will check any specific page or file on request, with the message composer below.

    A harness, not a chat box

    Spatio drives the agent loop itself: every workspace tool on the table each turn, grounded in the artifact you have open, executing against real data. When work turns into real engineering it hands off to the coding CLI you already pay for.

  • The Spatio Store with a developer list down the left (Spatio Labs, Google, Microsoft, Atlassian, Airtable, Bitbucket, GitHub, GitLab, Granola, HubSpot, Linear, monday.com, Notion, Salesforce, Slack, Stripe and more) and Google selected, showing its eight connectors: Calendar, Docs, Drive, Sheets, Gmail, Slides, Contacts and Tasks, each marked Synced with how long ago it last ran.

    Your data, however it has to be reached

    Native providers for the systems we build deep, third-party providers for the long tail, and Spatio Browser for everything with no dependable API. Your agent works in the real account with your real session rather than a stale export.

Spatio CLI

The same agent, in your terminal.

The workspace does not stop at the app. Install the CLI and the agent that runs your docs, tasks, mail and channels is one command away: pipe it your git log, script it in CI, or hand it your inbox from the shell you already live in.

  • spatio -p "…"

    One-shot headless runs. Prompt in, streamed reply on stdout, so it composes with pipes and drops straight into scripts and CI.

  • spatio chat

    Session-addressable runs. Open a session, send turns, tail the event stream as NDJSON, and pass the session id between processes.

  • spatio do <action>

    Every platform action, from the shell. Complete tasks, send mail, create notes. New platforms show up automatically, no CLI update needed.

Read the CLI docs

Install in one command

npm install -g @spatio-labs/cli

Live in your terminal

matt@Matthews-MacBook-Pro — spatio
Last login: Thu Jul 2 09:12:04 on ttys002
matt@Matthews-MacBook-Pro ~ %
Clients

Any MCP client can drive the harness. We ship the ones you will want.

The Spatio Workspace Agent Harness is exposed over MCP, so it is not tied to our app. Point Claude Code, Codex, Cursor or anything else that speaks the protocol at it and the agent gets every tool in your workspace, grounded in your real data.

We also build first-party clients, because most days you do not want to assemble one. Same harness, same workspace, same artifacts, whichever you open.

Desktop

The central hub

Where you do all your work. Augment your agents, open every platform, and watch artifacts come to life at native speed.

CLI

In your terminal

Drive your workspace without leaving the shell. Kick off agents, check on runs, and act on results inline.

iMessage

From your phone

Text your agent like a teammate. Ask a question, hand off a task, or approve a result straight from Messages.

Any MCP client

Bring your own

Claude Code, Codex, Cursor, or anything else that speaks the protocol. Point it at the harness and it gets the same tools and the same workspace.

Local to cloud, handled

Start on your desktop. Continue in the cloud.

Our purpose-built handoff keeps every run alive across surfaces. Work you begin on the desktop continues uninterrupted in the cloud while you’re away, then resumes with full context the moment you return. No re-briefing, no lost progress.

Local
Build the Acme customer deck
On it. Generating the deck locally on your Mac.
Reply to the agent…