1AgentBox

App coming soon

The workspace
is the computer

A sealed Linux workspace for a whole team of coding agents. Drop in Claude Code, Codex, Gemini CLI or Grok — they share files, a bus and one browser, and nothing else on your account.

WaitlistRead the spec
Host app
macOS · Windows
Guest
One VM per workspace
Boundary
Workspace, not account
Reset
Snapshot & restore
Host · macOS / Windowschat · live view · approvals
start · stop · snapshot · approve
Sealed · one workspace
8 GB · 4 vCPU

Stoic OS — Ubuntu Server 24.04 LTS minimal, arm64.

  • 01

    Claude Code

    lead

    own profile

  • 02

    Codex

    tests

    own profile

  • 03

    Gemini CLI

    docs

    own profile

  • 04

    Grok

    research

    own profile

Shared inside the seal:/workspaceMCP busOS-owned browser
Isolation is the workspace, not the account.

§01 — Load-bearing decisions

Four decisions everything else hangs off

  1. 01

    The workspace is the computer

    One workspace equals one Stoic OS instance. Agents are residents of that machine. Snapshot, pause, destroy and network policy apply to the workspace. The account is not a shared PC.

  2. 02

    Agents are services

    A declared roster: role, runtime, cwd, MCP, network, secrets. Restartable. Not a chat tab that happens to have a terminal.

  3. 03

    One OS-owned browser

    Fast engine first, Chrome on promotion. Agents attach over loopback CDP. They do not each spawn Playwright-Chrome.

  4. 04

    Reset is cheaper than cleaning

    Immutable /usr. Updates are a new Stoic OS version. Workspace data survives. Snapshot before a risky run.

§02 — The boundary

Screens are not a security boundary

One computer per account

Everything in one pod

shared pod

  • cookies
  • files
  • CLI creds
  • browser profile
  • bot 1
  • bot 2
  • bot 3
  • bot 4

As observed in August 2026, Grok Bot runs a shared per-account pod (Cursor pod-daemon), not one VM per bot. Cookies, files and CLI credentials are pooled.

One computer per workspace

A box each

  • checkout

    own OS
    own creds
    own browser

  • billing

    own OS
    own creds
    own browser

  • docs

    own OS
    own creds
    own browser

Every workspace gets its own Stoic OS instance. Agents are residents of that machine, and you pick the model runtime per agent. Computer use is a tool here, not an identity.

§03 — Sizing

Honest RAM. Disk is a different number.

"A few GB" is a disk-image target, not a RAM promise. Chrome dominates RAM. These are creation-sheet SKUs — there is no popular middle tier here, only the one that fits what you are running.

  • Lite

    2 GB
    vCPU
    2 vCPU
    Browser
    Fast engine only

    Docs, crawl, structured sites, CLI agents

  • Standard

    8 GB
    vCPU
    4 vCPU
    Browser
    Fast + Chrome on demand

    Real SaaS, login, watch and takeover

  • Dense

    16 GB
    vCPU
    4-8 vCPU
    Browser
    Chrome headed

    Several agents plus a human looking

The UI shows live guest memory, not only the SKU you bought.

§04 — Out of scope

What this is not

  • Not a chatbot with a shared cloud PC.

    The work runs in the guest. The Mac or Windows app is a spectator: chat, live view, approvals, lifecycle.

  • Not a new kernel, and not Ubuntu plus a wiki.

    Stoic OS is an immutable Linux userspace. Read-only /usr, agent supervisor as the session, browser and MCP as OS services.

  • Not a daily-driver desktop.

    No Hyprland rice, no GNOME, no Steam. Humans watch through the host app. Computer use is a kiosk, not a coworker desktop.

  • Not one Chrome profile for the whole account.

    Default: one browser profile per agent. A shared profile is an opt-in inside a workspace, never the default across the account.

§05 — Credentials

Separate logins, separate box

Agents in one workspace can read /workspace. That is the contract, stated up front. If two agents should not share a login, they do not share a workspace — or at minimum they do not share a browser profile.

  • Browser profileone per agent, by default
  • Shared profileopt-in, inside a workspace only
  • Across the accountnever
Three identical sealed machines on a shelf, each its own computer.

§06 — Questions

Straight answers

01How is this different from Grok Bot?

As observed in August 2026, Grok Bot puts every bot on one shared per-account pod (Cursor pod-daemon), not one VM per bot. 1AgentBox gives every workspace its own computer, and lets you pick the model runtime per agent. Isolation and multi-model assignment are the product.

02Do agents share logins?

Not unless you opt in. Default is one browser profile per agent. They share /workspace files and the MCP bus. Separate credentials means a separate workspace or a separate profile. The UI has to say this where the checkbox is, not only in a doc.

03Is Stoic OS a new operating system?

It is a sealed, versioned, agent-shaped Linux image, not a new kernel. Base is Ubuntu Server 24.04 LTS minimal, arm64. Calling it an OS is honest about the contract. It is a lie if it is Ubuntu plus a wiki.

04Will you claim a 64 MB browser that does the whole web?

No. The fast engine will lose some pages. Compat Chrome exists for those. Lite is fast-engine-only. Standard promotes to Chrome on demand.

05What does a few GB mean?

Disk image, not RAM. Chrome dominates RAM. The creation sheet sells Lite 2 GB, Standard 8 GB, Dense 16 GB. The UI must show live guest memory, not only the SKU.

06Do I need 1VM or vpsbox?

They are backends, not the product. Same Stoic OS image on a local VM or on a Linux box you already have, over SSH.

A sealed black machine in a metal cage, one violet status light on.

App coming soon

Seal the box. Hand it a team.

1AgentBox is pre-launch. The waitlist is where the first Stoic OS images go out, and where the SKU pricing lands once it is set.

WaitlistFull spec