§ 01 / pitch

A local runtime for AI agents.

Bring your orchestrator, your agent, your model. Pick the container engine you already use — Docker, OrbStack, more on the way. WarpDrive boots an isolated, MCP-wired sandbox for each run and gets out of the way.

join the alpha watch a real session ↓

§ 02 / one real session

What it actually looks like.

This is the control surface, not the agent. Boot the sandbox, wire MCP, point at an orchestrator, attach to live sessions from a laptop or your phone. The agent doing the work is whatever you brought.

§ 03 / what you bring · what we provide

An infrastructure play, not a platform.

WarpDrive is opinionated about isolation and indifferent about everything above it. Bring whatever you want to bring; replace any of it tomorrow without touching the runtime.

you bring

The orchestrator
Claude Code, Codex, OpenCode, your own — anything that ships a warpdrive.manifest.yml.
The agent and the model
Cloud APIs, local runtimes — Sonnet, Opus, GPT, Gemini, llama.cpp, Ollama. The runtime doesn't care.
The container engine
Docker and OrbStack are tested today. The architecture isn't tied to either — Podman, Colima, anything that runs OCI containers can plug in.
Your API keys
Stored on your machine, used by your agent inside the sandbox. Nothing routes through us. There is no us.

warpdrive provides

The sandbox lifecycle
Boot, isolate, run, tear down. Cleanly, every time, with a workspace bind-mount you can trust.
The MCP fabric
Pre-wired servers — Serena, Context7, Chrome DevTools, Filesystem — speaking to the agent over a single bridge.
The session bus
Every keystroke and tool call logged, replayable, addressable from anywhere on your network.
The mobile pickup
Live terminal access from your phone. Same session, no copy-paste, no re-prompting.

§ 03b / what it looks like, drawn

The runtime, on one page.

A flat schematic of how the parts sit together.

YOUR DEVICES · INTERCHANGEABLE laptop mobile YOU BRING workspace dir any host path → bind-mount as /ws orchestrator repo warpdrive.manifest.yml → helm runs setup WARPDRIVE · MANAGED BOUNDARY API · :7777 sandbox container /ws · host workspace mount helm · agent CLIs tmux · skills · hooks · plugins /home/.../orchestrators/active tmux-manager · readiness gate mcp fabric isolated docker network · stdio mcp · filesystem mcp · memory mcp · code-index mcp · docs-fetch mcp · browser-dt mcp · seq-think mcp · custom... model cloud · or · local RUNS ON docker · orbstack · ... FIG · 01 · WARPDRIVE RUNTIME · LOCAL
All inputs are interchangeable. The runtime is what stays the same.

§ 04 / it follows you off the desk

The session keeps going. So do you.

Sessions don't end when you close the laptop. Open the companion on your phone and you're in the same sandbox, the same agent, the same terminal — keystrokes, output, escape codes, all of it. Pick it up between meetings. Watch from the couch. Drive a run from a train.

android today.

§ 05 / for orchestrator authors

Ship a manifest, get a runtime.

Building an orchestrator? Drop a warpdrive.manifest.yml at the root of your repo. WarpDrive reads it, boots the sandbox you described, and runs you inside it. The manifest schema, helm lifecycle, runtime guarantees, and the public REST API are all in the docs.

read the integration guide → 
manifest: 2
name: claude-code
description: Drive Claude Code on the active /ws workspace.

infrastructure:
  requires: [bash, tmux, git, node]
  environment:
    - name: ANTHROPIC_API_KEY
      required: true

setup:
  command: ./scripts/setup.sh

sessions:
  - name: chief
    pattern: chief-session
    role: primary

actions:
  - id: open-chief
    name: Open Chief
    command: ./scripts/open-chief.sh
    session: chief
  - id: run-task
    name: Run Task
    command: ./scripts/run-task.sh
    async: true
    params:
      - name: prompt
        type: string
        required: true
warpdrive.manifest.yml — minimum viable orchestrator

§ 06 / what's actually shipping

The honest state, today.

Alpha means alpha. This is what works, what doesn't, and what's next.

works today

  • macOS, Linux, and Windows desktop builds
  • Docker and OrbStack as container engines
  • Claude Code, Codex, OpenCode as orchestrators (any orchestrator with a manifest, in principle)
  • Cloud and local agents, any model
  • MCP servers pre-wired: Serena, Context7, Chrome DevTools, Filesystem
  • Mobile companion for Android

rough edges

  • Manifest schema is on v2 — earlier versions don't load.
  • Only the default sandbox is exposed via the orchestrator API today; multi-sandbox orchestration is internal.
  • setup.command must be non-interactive — anything that prompts for input will hang.

coming next

  • Podman and Colima support (architecture is engine-agnostic; integration is the work)
  • iOS companion
  • Multi-sandbox orchestration exposed through the public API

§ 07 / what early users say

We don't have testimonials. We have peers.

  • you have an additional full time customer now. ███ and i are both on warpdrive latest as daily driver.
    alpha tester · building agent infrastructure
  • [ placeholder — alpha tester quote pending ]
    —
  • [ placeholder — alpha tester quote pending ]
    —
  • [ placeholder — alpha tester quote pending ]
    —

§ 08 / join the alpha

We'll email when there's a build for you.

Drop your address. No newsletter, no decks, no roadmap pitch. We'll email when there's a build worth your time.