All posts
RELEASEv3.3.6October 17, 2026· 4 min read · by VirtConsole

VirtConsole 3.3.6

VirtConsole 3.3.6 renames MicroVMs to Sandboxes and Kits, adds seven agent kits from a signed catalog, a tools gateway that delivers provider credentials to the node instead of the sandbox, a one-sentence launcher, live progress for local backups and an inline switch on backup storages.

ShareLink copied

VirtConsole 3.3.6 gives your customers a place to run AI coding agents in isolated machines, and gives you control over what they can run and which tools they can reach. MicroVMs are now Sandboxes and Kits, agent kits install from a signed catalog, and a tools gateway lets an agent use services such as Linear or Miro without handing the sandbox the credentials.

The existing /api/microvm paths and the microvm:read and microvm:write token scopes keep their names. Coverage of newer endpoints varies by integration.

Sandboxes and Kits

The MicroVM surface is renamed throughout the panels: Sandboxes are the running machines and Kits are the templates they launch from. Panel pages move to new addresses, and bookmarked panel page addresses redirect to the new ones.

Read the sandbox overview and the admin guide to enabling sandboxes.

Seven agent kits from a signed catalog

An agent kit is a sandbox with a coding agent already installed at a pinned version. The seven kits are Claude Code, Codex CLI, Gemini CLI, OpenCode, OpenCode 2, GitHub Copilot CLI and a plain Shell kit.

  • Kits come from a signed Kits Hub catalog. Your panel verifies the catalog and every kit before anything is installed.
  • Admins pick the kits to install in Sandboxes > Kits. When a newer version is published, the row offers Install update.
  • Customers can select an available older kit version in the launcher.
  • Pulls that hit a registry limit are retried automatically with bounded backoff.
  • Private kit images can use a saved registry credential instead of typing it into each kit.
  • Admins can try a candidate version of a kit before making it current.

Read the agent kits guide and the admin kits guide.

MCP tools gateway

Agents in a sandbox can call external tool servers (MCP servers) through a gateway on the node. The sandbox receives local gateway endpoints and server metadata, without upstream provider credentials. The gateway adds the provider credential to forwarded requests. A confirmed sandbox stop clears that run’s node-side gateway state, and your saved account connection remains available for later launches.

  • A provider catalog with hosted servers such as Cloudflare, Grafana, Granola, incident.io, Jira, Linear, Miro and Notion.
  • Custom servers, with OAuth sign-in, a static token or no sign-in.
  • Customers pick the servers per sandbox at launch, and the sandbox page shows the state of each connection.
  • Admins get gateway settings, manual provider registrations, and a drain command to take tool-using sandboxes down before a node downgrade.
  • Claude Code, Codex CLI, Gemini CLI, OpenCode, OpenCode 2 and GitHub Copilot CLI are configured automatically. The Shell kit writes a server list for your own scripts.

Nodes must be current to run the gateway. Read the tools guide and the admin tools gateway guide.

A one-sentence launcher

Starting a sandbox is now one sentence: pick the kit, size, location and lifetime by clicking the parts you want to change.

  • Saved secrets. Keep API keys encrypted in your account and tick them at launch. Values are never shown back.
  • Provider key rows. Each kit suggests the keys it needs, with the vendor’s mark. OpenCode accepts Fireworks, OpenRouter, Anthropic, OpenAI, Gemini, DeepSeek and Kimi keys.
  • One GitHub token. A token line of its own, shared by every kit, so git clone and git push over HTTPS work without a prompt.
  • Key/value rows. Environment variables and secrets share one row editor under Advanced options.
  • Copy as. Copy a launch as a cURL command, or generate OpenTofu and E2B starting points. Saved secret values are replaced with placeholders. The cURL command includes the selected tools; check the comments in the OpenTofu and E2B copies for settings they cannot represent.

Read launch a sandbox.

Backups and the admin panel

  • The backup storages list has an inline enable switch, and a row opens an edit modal instead of a new page.
  • Local backups show progress: the phase, bytes copied, transfer rate and time remaining. Nodes on older agents keep the plain progress bar. The backup queue API adds a nullable progress_detail field.

Thanks for building on VirtConsole. Questions along the way, reach us any time.

ReleaseReleaseSandboxesKitsMCPAI Agents
Back to all posts