Open source. Local first. Model agnostic.

Your AI agent just got a computer.

Qubicl gives AI agents a private, persistent, containerized workspace on your machine. Choose a preset with the right mix of durable files, terminal access, local web research, Chromium, desktop control, and human takeover. Works with Codex, Claude, OpenCode, OpenClaw, Hermes, Open WebUI, Cursor, VS Code, and other compatible agents and clients.

Install Qubicl See how it works

$ npm install -g qubicl-cli

Apache 2.0 · No Qubicl account required

localhost:4173

⋮

LOCAL COMPUTER Research, build,
and hand it back. Open preview

Terminal— □ ×

agent@research:~/project$ npm run build

✓ 42 modules transformed.

✓ built in 1.24s

agent@research:~/project$

First public release

Qubicl 0.1

Turn local Docker into durable, observable computers for external AI agents connecting through MCP, OpenAPI, or Open WebUI’s Open Terminal integration.

A computer that keeps its files

Durable, host-visible files persist across restarts, upgrades, backups, checkpoints, and clones.

More than a terminal

Give agents web research, a persistent browser, desktop apps, screenshots, local previews, Git, and managed processes.

See it. Take it over.

Watch the live computer, fence agent tools, finish the task yourself, then return the same session to the agent.

Operator controlled

Choose resources, network policy, exposed tools, active skills, credentials, and lifecycle for every computer.

Read the 0.1.0 release notes Pre-1.0 interfaces may evolve

Open connections

Your agent stays.
Qubicl adds the computer.

Keep the model, client, and workflow you already trust. Connect over supported local interfaces, then expose only the capabilities each task needs.

Explore client connections

Local connection No Qubicl account required

Your existing client Agent, IDE, or automation

MCP OpenAPI Open Terminal

Local gateway Qubicl localhost only

Terminal

Files

Browser

Desktop

No Qubicl account.

No cloud control plane.

No model lock-in.

Just computers on your machine.

Progressive presets

Choose only the computer the task needs.

Every preset starts with durable files, terminal access, Git, managed processes, and local web research. Add a browser or desktop only when the work calls for it.

file-system

Headless shell, processes, Git, durable files, and web research.

Fast coding and automation
No graphical viewer

1 CPU · 512 MB

browser

Persistent Chromium, OCR, screenshots, and PDF inspection.

Semantic and visual browsing
Live viewer included

2 CPU · 2 GB

Most versatile

computer

Browser plus a lightweight XFCE desktop, editors, document tools, and SSH.

General purpose agent work
Human takeover included

2 CPU · 3 GB

workstation

Full development and office environment with LibreOffice.

Heavier desktop workflows
Broadest app catalog

2 CPU · 4 GB

Before handoff

Agent working

Keyboard + mouseAgent

Agent toolsAvailable

Browser + desktopLive

After handoff

Operator in control

Keyboard + mouseOperator

Agent toolsFenced

Browser + desktopSame session

Control transferred safelyresearch · localhost

Human takeover

Watch without interrupting. Take over without starting over.

The live viewer is passive until you act. Take control and Qubicl fences agent tools, stops ordinary managed commands, and hands you the keyboard and mouse. The persistent browser and explicitly managed desktop applications remain visible, so you can continue the task and return control when you are done.

Passive observation
Fail-closed handoff
Persistent session

How takeover works

Four steps

From install to a connected computer.

Install the CLI

Install the Qubicl command-line tool from npm.

npm install -g qubicl-cli

Run setup

The wizard validates local Docker, compares presets, previews resource and image effects, obtains the selected computer image and gateway, and can create the first computer.

qubicl setup

Create a computer

Name the workspace and select the preset that better supports the job.

qubicl create computer-name --preset computer

Connect your agent

Generate validated setup instructions without editing client files or exposing a token.

qubicl connect computer-name --client open-webui

Stay local

The operator stays in control. Work stays inside its computer.

Computers run without privileged mode, a Docker socket, host namespaces, arbitrary mounts, or passwordless elevation. The gateway binds only to localhost, and model-facing files stay inside the durable home.

Know the boundary: Qubicl is for trusted or operator-supervised workloads. Controller and workload processes share each computer container, so takeover is a cooperative fence for Qubicl-managed work. It is not a VM-grade boundary against hostile custom images, kernel exploits, Docker compromise, or another user who controls the host account.

Read the security model

Host trust boundaryLocal machine

01 Agent clientYour existing tools

localhost only

Local Qubicl gatewayAuthentication · policy · routing

authenticated tools

03 Computer containerTerminal · browser · desktop · files

No Docker socketNo privileged modeNo host namespacesNo arbitrary mounts

Runtime modelOne resource-bounded container per computer

Qubicl 0.1.0

Give your agent somewhere real to work.

Install the CLI, run the setup wizard, and create your first local computer.

Requires Node.js 22.14+ or 24.x, Docker Engine 24+ or Docker Desktop 4.29+, and Docker Compose 2.24+. Linux x64 is directly validated; Linux ARM64 and macOS are best-effort.