Agents and private state

Documentation / Workspaces

Agents and private state

Connect once, launch official clients and keep each workspace’s conversations and memory.

Accounts belong to the controller

Connect Codex, Claude Code and Cursor Agent through the dashboard's Agents panel. Native sign-in runs on the controller. Refresh credentials stay in its private provider homes; assigned workspaces receive compatible access material for the same owner.

Prepared bases and unused warm reserves remain credential-free. A sleeping workspace catches up when it resumes. Connecting an account does not multiply its allowance or guarantee every model is included in its plan.

Keep the whole native home

Engine Box preserves each workspace's private home between runs, including native settings, skills, memory, transcripts and browser profiles. Project files also retain repository instructions, scratch notes and build output.

ClientExamples of private state
Codex~/.codex, ~/.agents, project instructions
Claude Code~/.claude, ~/.claude.json, project memory
Cursor Agent~/.cursor, ~/.config/cursor, project configuration

Stable project paths matter to native memory lookup. Engine Box does not merge or synchronize whole homes between workspaces. Portable tenant state and cross-workspace memory are separate future capabilities.

Launch and resume an exact conversation

Call the operator MCP tool agent_launch for an assigned, running workspace:

{
  "host_id": "primary",
  "name": "ebox-example",
  "provider": "claude",
  "prompt": "Read this project's instructions and summarize its structure.",
  "workdir": ".",
  "timeout_seconds": 120
}

Poll agent_run with the returned run ID and the same host/workspace. To continue that conversation, call agent_launch again with resume_id set to its returned native_session_id. Engine Box requires the exact native UUID; it does not guess the latest chat.

The clients run under their native tool and approval policies. The bounded API currently allows runs up to 300 seconds with at most 256 KiB of combined output. Direct terminals remain available for interactive workflows. See native run semantics.

Usage is an observation, not a shared balance

The Agents panel reports native allowance data when a qualified provider interface exposes it. Otherwise it shows that usage is unavailable and links to the provider. An allowance reset is not automatically a billing renewal date.

Parallel work still consumes the connected account's limits. Engine Box does not pool unrelated accounts or share provider-side inference caches. Native conversation resume restores saved context; VM memory preservation and provider prompt caching are different mechanisms.

One trusted owner today

The current controller serves one owner. Its operator token grants fleet authority and must stay outside guest environments. Private homes, credentials and checkpoints must never become reusable templates.

Parallel agents can use separate private workspaces. Public multi-tenant hosting, movable tenant volumes and shared writable native homes are not part of the current authorization model. See availability and limits.

Built from the source. Browse technical reference ↗

Search concepts, guides and command examples.