The web is where work happens. Agents needed a way in.
Panes exists because the teams building autonomous systems at L1fe kept needing the same thing: a real browser, isolated, in a known region, with access that could be granted to an agent and revoked without a postmortem. We built it on Omega — the compute platform that already ran our browser workloads — and scoped it with Keystone, the identity layer the rest of the platform trusts.
Principles
What we believe about browser infrastructure
Agents are principals
Most browser platforms bolt agent access onto an API key. We started from the opposite end: every actor — human or agent — is an identity with explicit permissions, and the browser is something you're granted, not something you hold.
Facade, not fork
Panes is a deliberate product facade over Omega's production browser workload. We don't run a second browser stack for marketing screenshots — the console, SDK, and MCP tools drive the same deployments the platform runs.
Credentials should die young
Long-lived secrets leak — into logs, into agent context windows, into screenshots. Term credentials expire in minutes by design, so the blast radius of any leak is measured in seconds of usefulness.
The console is the spec
If a capability isn't good enough for a human operator at 2 a.m., it isn't good enough for an agent either. Everything ships in the console first, with the same API surface exposed to code.
The platform
Part of something larger
Panes is one product in the L1fe ecosystem — browsers on Omega compute, identity from Keystone, metering through Garden.
OmegaCompute — runs every isolated Chromium sessionKeystoneIdentity — OAuth, tenancy, and permissionsGardenMetering — usage events into the platform ledger