Project
The durable setup. Repository, default branch, environment recipe, and references to secrets.
PERSISTS ACROSS SESSIONS ↗
ZERON CLOUD / DESIGN EXPLORATION
Agents, without
the laptop.
Same project. Your choice of harness.
A workspace that keeps going when you close the lid.
Explore the architecture ↗A proposed paid feature.
Built on the engine we already have.
Built on the engine we already have.
EXECUTION, UNTETHERED
▱ Your laptopLOCAL ENGINE
One project.Many places to work.☁ Cloud workspace ENGINE RUNNING
01 / THE PRINCIPLEKeep the context.
Choose the compute.
Choose the compute.
35° 41′ N
139° 41′ E
139° 41′ E
LOCAL BY DEFAULT✳CLOUD WHEN YOU NEED IT✳HARNESS INDEPENDENT✳CONTEXT THAT STAYS
01 / PRODUCT MODEL
A project is the home.
A session is the work.
Cloud is a place to run a session. Enable it once on a project, then choose local or cloud whenever you start something new.
Session
The conversation and task. Its own branch, selected harness, model, and execution location.
LOCAL OR CLOUD ↗
Cloud workspace
The session’s isolated checkout and saved harness state. Compute can sleep; the work remains.
DURABLE STATE, REPLACEABLE RUNNER ↗
TRY THE INTERACTION
One small choice.
A different place to run.
The project stays the same. Execution moves to the location you select.
A dedicated cloud workspace. Your laptop can go offline.
NEW SESSION · INTERACTIVE PREVIEW↗
▧ comet↳ main
Build the next great thing.
Your project context is ready.
☁ Cloud
Cloud workspace · isolated checkout · saved state
Illustration only. No repository is connected and no compute is started.
02 / REPOSITORY ACCESS
Your repo.
Your permission.
For private GitHub repositories, install the Zeron GitHub App and choose which repos it can access. Signing in to Zeron and granting repository access are separate steps.
Choose the repositories
Install on your account or organization. An organization may require an owner’s approval. Access can be revoked from GitHub.
Save the environment
Pick the base image, setup commands, and required secrets once. Store secret references on the project; inject credentials only into authorized workspaces.
Start an isolated session
Clone the chosen revision into a separate workspace. Uncommitted changes on your laptop are not included automatically.
03 / EXECUTION ARCHITECTURE
The same engine.
A new address.
Run the existing headless Zeron engine inside an isolated cloud workspace. Keep the harness adapters, transcript sync, terminal, and file protocols.
Zeron appDesktop or mobile
← RPC / SYNC →Control planeAccess · scheduling · usage
← SCOPED LEASE →Cloud runnerHeadless engine + harness
└──── Durable workspace: checkout + harness state + run journal ────┘
Any supported harness
Scheduling stays independent of the agent. Each adapter declares its runtime, authentication, capabilities, and resume requirements. Cloud support is validated per harness.
Scoped by workspace
Give each runner a limited credential and an exclusive execution lease. A cloud runner must not inherit the broad trust of a personal synced device.
State survives compute
Save uncommitted files and native harness state at stable paths. Restore before accepting new work. A transcript alone cannot resume an agent.
Implementation notes for the existing codebase +
Space currently binds a device to a folder. Introduce a logical project above spaces so a local folder and a cloud workspace can belong to the same project.
Reuse Harness, the headless engine, relay RPC, and document sync. Add server-owned workspace lifecycle, quota checks, metering, and lease fencing. Billing and execution ownership must not rely on editable client documents.
Provisioning must be idempotent. On runner failure, fence the previous owner and recover the journal; do not blindly replay commands with external side effects. Changing harnesses creates an explicit context handoff, not a native-session migration.
04 / LIFECYCLE & ECONOMICS
Work persists.
Compute takes a break.
A subscription would include compute credits and a concurrency limit. Model usage is separate. Exact pricing and provider authentication support remain to be decided.
The agent is executing in its workspace. Meter allocated compute and keep progress available on every connected device.
COMPUTE ACTIVEBudget before boot
Enforce entitlement, concurrency, and spending caps before allocation. Overages are opt-in.
Sleep on actual idle
Check process and tool activity before stopping. A quiet transcript does not mean an idle agent.
Retain with clarity
Show storage retention and charges separately. Keep transcripts readable without waking compute.
THE FIRST RELEASE
Small surface.
Room to grow.
One repository per project. Isolated cloud sessions.
A validated harness set. Saved workspaces. Automatic sleep and wake.