Open source. Local first. Model agnostic.

Your AI agent just got a computer.

Qubicl runs locally with Docker and gives AI agents durable Linux computers with files, terminal access, browser automation, desktop applications, human observation, and 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$

Persistent by design

One computer Persists.

The computer owns its durable home, Chromium profile, network policy, tools, credentials, and runtime configuration. Agents are temporary. The computer is not.

Durable identity

Files, workspaces, cookies, site data, local storage, preferences, sessions, and browser history survive restarts and supported upgrades.

Shared by choice

Compatible clients can reconnect to the same computer and continue with its existing home, browser profile, policy, tools, and credentials.

Separate by trust

Create separate computers when agents, clients, projects, or users should not share persistent identity and state.

Operator owned

Manage resources, network access, tools, skills, credentials, and lifecycle from the CLI or local dashboard. Review changes before approving them.

See what shipped in 0.5 Local first · Model independent · Apache 2.0

Shared computer state

Change the client.
Keep the computer.

Codex, Claude, OpenCode, OpenClaw, Hermes Agent, Open WebUI, Cursor, VS Code, and other compatible clients can continue work in the same Qubicl computer. A new client does not mean a new home or isolated session.

Explore client connections

Local connection No Qubicl account required

Compatible client Agent, IDE, or automation

MCP OpenAPI Open Terminal

Shared local gateway Qubicl localhost only

Terminal

Files

Browser

Desktop

Your files.

Your browser.

Your policy.

The agent gets a computer, not your machine.

Progressive presets

Choose only the computer the task needs.

Every preset starts with a durable home, terminal access, Git, managed processes, and local web research. Browser-capable presets add a durable Chromium profile. Images are acquired lazily and share layers across presets.

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 profile, OCR, screenshots, and PDF inspection.

Cookies and sessions persist
Reset tabs without wiping the profile

2 CPU · 2 GB

Most versatile

computer

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

General purpose agent work
Authenticated viewer and takeover

2 CPU · 3 GB

workstation

Development and office workflows with supported Writer, Calc, and Impress applications.

DOCX and PPTX previews as PDF
Broadest supported work surface

2 CPU · 4 GB

Local management

Your computers.
One place to manage them.

Create computers, adjust resources, manage tools and network access, and review backups and updates from a local dashboard. See what will change before you approve it, then follow the operation through completion or recovery.

Explore the dashboard

01 / COMPUTERS

See every computer.

Check lifecycle state, resources, exposed tools, network policy, skills, and scoped credentials.

02 / REVIEW

Approve the plan.

See effects and interruptions before a change runs. Sensitive actions ask for your password again.

03 / BACKUPS

Protect durable homes.

Create backups, checkpoints, and clones without turning the computer into a disposable session.

04 / RECOVERY

Return to unfinished work.

Operation history survives restarts and keeps ambiguous results available for local review.

Optional setup

Enable it from the host.

The dashboard is available on native Linux x64 and Apple Silicon macOS. Set the administrator password in your terminal, then finish setup in the browser.

$ qubicl dashboard enable

$ qubicl dashboard open

Setup guide ↗Upgrading? →

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. Viewer-capable computers authenticate internal noVNC traffic, and raw VNC is never exposed. Take control and Qubicl fences agent tools while the durable browser profile and managed desktop applications remain visible.

Authenticated viewer
Fail-closed handoff
Persistent computer

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 setup instructions for a compatible client. Other clients can later reconnect to this same computer and continue its existing state.

qubicl connect computer-name --client open-webui

Explicit trust boundaries

One computer is one shared trust boundary.

Agents connected to the same Qubicl computer share its persistent home, browser profile, network policy, tools, credentials, and runtime configuration. Disconnecting an agent does not reset that state or create a security boundary.

Separate what should not trust: Create different computers for agents, clients, projects, or users that should not share state. Qubicl is designed for trusted or operator-supervised work. Its Docker containers are not a VM boundary for deliberately hostile code.

Administration stays with the host owner. The dashboard previews changes before approval and requires password confirmation for sensitive actions. Optional private HTTPS administration is configured separately from remote agent and viewer access. Both are off by default.

Read the security model

Host trust boundaryLocal machine

01 Compatible clientsShared only by operator choice

authenticated

Operator gatewayAuthentication · policy · routing

fenced access

03 Persistent computerHome · profile · tools · policy

Loopback by defaultAuthenticated viewerPath-safe storageExplicit remote TLS

Trust modelSeparate computers for separate trust

Releases

The latest from Qubicl.

Qubicl 0.5 adds local management, private administration, and more resilient recovery. Explore the release and the upgrade guide for existing computers.

Current release0.5

Local management.
Reviewed changes.

A dashboard for your computers, optional private HTTPS administration, and recoverable operations that preserve durable state.

Read the 0.5 release notes

Release archiveAll

Every public release.

Browse current and historical release notes, upgrade guidance, support status, and known limitations.

View all releases

Platform support · Qubicl 0.5

Run Qubicl on Linux, macOS, or Windows through WSL 2.

Core Qubicl supports Linux x64, Apple Silicon macOS with Docker Desktop, and Windows 11 x64 through Ubuntu 24.04 on WSL 2 with Docker Desktop. Every Qubicl computer runs Linux.

Management dashboard: Available on native Linux x64 and Apple Silicon macOS. Windows through WSL 2 uses the CLI.

Requires Node.js 22.14+ or 24.x, Docker Engine 24+ or Docker Desktop 4.29+, and Docker Compose 2.24+. Run as your normal user. Start Docker before setup.

Other platforms and Windows setup

Linux ARM64, Intel macOS, Windows on ARM, and other WSL 2 distributions are best effort for core Qubicl. Native Windows and WSL 1 are unsupported.

On Windows 11, install Ubuntu 24.04 under WSL 2 and enable Docker Desktop’s WSL integration. Install and run Qubicl inside Ubuntu. Keep Qubicl state and computer homes in the Linux filesystem under /home, not on a mounted Windows drive.

Support policy and release testing are distinct. See the release-specific testing scope and the platform guide.