/ manage

Boxes

Every agent box, its worker slot and its default agent. Open a box to inspect or manage it.

+ New box
New boxBox → Logins → Tools → Instructions
1 · Box
Placement: automatic (override)

Uses available capacity in the least occupied pool. If none is free, queues in the controller default pool. Override to compare workers.

2 · Logins

Choose at most one Codex, Claude, or OpenCode login. It is copied into the box at creation; choose None to start without an agent login.

One agent profile sets the harness; add a GitHub profile separately if needed.

3 · Tools
Optional tools

Starts a local proxy. Apps must opt in with socks5h://; WARP needs Cloudflare UDP access and may be unavailable on this provider.

add custom tooling

Trusted commands run inside the box before work starts (5-minute limit). Use package managers or your own installer. The recipe reruns on resume: keep it idempotent. Do not paste credentials. Logs: ~/.config/vmbox/tool-setup.log.

4 · Instructions

Permissions

Each box owns its optional MCP tools and limits directly. Contact lists live in the box details in Agent chat.

Profiles

Saved Codex, Claude, OpenCode, and GitHub logins for this account. Credentials are never displayed or downloaded.

AI writing helper

Set the OpenRouter key and model used by the writing wand in chats and instruction editors.

Agent CLI versions for new boxes

Choose the worker image version, the latest npm release at box creation, or a published exact version. Changes apply to future boxes in this account.

Choose a saved agent login when creating a box. Existing boxes receive a new copy through their Credentials action. CLI upload remains available: vbox profiles save APPLICATION NAME --from SOURCE.

Instructions

Reusable instructions you can apply to any box, kept as versioned presets.

New presetName it, then write or upload Markdown

Providers

Configured worker pools. Choose Manage on a pool to change its slots, box size and connection.

loading default provider…

Add provider

Capacity

Each running box occupies one compute slot. Dedicated workers have one slot; shared workers host several slots on the same cpu and memory. New boxes use automatic placement; expand the placement override to compare worker pools. Hibernated boxes retain storage without occupying a slot.

Slot location

Choose the region for this provider’s fleet before provisioning slots. Changing location requires zero desired slots, zero actual slots, and no existing boxes. Existing slots and workspace volumes cannot be moved here. Do not delete workspaces just to change location.

Increasing capacity may incur provider charges. Reducing capacity drains free slots; occupied slots are not forcibly stopped.

Notifications

Send box events to a webhook or a Discord channel. Optional.

Add notification destination (advanced)

Configure a webhook or discord destination. Secret values are sent to the controller and never displayed again.

vbox controller · box access is via the CLI or the box workspace