Move the load off your laptop.
Keep repositories, dependency installs and long-running tasks on your servers. Run your control plane there too, so sessions and browser access stay available when your laptop is offline.
YOUR SERVERS. PERSISTENT ENVIRONMENTS. ONE CONTROL PLANE.
Move Claude, Codex, Antigravity, Pi and 23 more agent CLIs to your remote servers, inside persistent, isolated Docker workspaces. Claude Code and Codex can also use models through OpenRouter, Vercel AI Gateway or LiteLLM. Leave them running. Manage sessions, accounts, files and resource access from one console — with separate environments for every developer.
Connect your console over HTTPS/WSS and explicitly pair local Docker. Continuous folder sync over WSS is available; on macOS it is verified with OrbStack, while Docker Desktop file sharing is not yet measured.
For a custom SSH port or an IPv6 address, add a Host entry to ~/.ssh/config and choose the alias.
The installer will ask for your token (input hidden). This page never reads or sends it, and the token never appears in the command, shell history or files. A GitHub token also fetches the private devctrl source; the token is imported into the server's Git accounts. Minimum token permissions
Minimum GitHub permissions: a fine-grained token for resource owner devctrldev with only devctrldev/devctrl, Metadata and Contents read-only, plus what your own repository needs; or a classic token with repo.
curl -fsSL https://devctrl.dev/install.sh | shUse Docker on this computer. Requires Docker Compose, Node.js, Python and Git; no remote server or SSH. Add accounts and projects in the local console.
Pick a repository URL or local Git folder and an SSH host. Choose GitHub or GitLab tooling. Select supported local Git profiles, Claude and Codex authorizations to import, or sign in to Antigravity in its remote CLI. Setup prepares your server, adds devctrl tui remote and devctrl web remote shortcuts and returns a private browser link. A URL needs no local Docker. A folder also installs the Docker client for automatic Exchange sync.
Keep repositories, dependency installs and long-running tasks on your servers. Run your control plane there too, so sessions and browser access stay available when your laptop is offline.
Put the team’s compute to work without mixing private environments. Each developer gets their own containers, credentials and storage; you choose shared resources and per-user budgets.
See sessions across projects and hosts, send files, connect services and switch eligible accounts. Enable context tools, update project tools and remove declared task artifacts from one console.
Loading the recorded terminal…
FROM ONE SESSION TO MANY
A growing stack of terminals, SSH connections, dependency trees and credentials makes every new session harder to manage.
devctrl prepares the remote workspaces, keeps sessions organized and brings files, access, updates and cleanup into the same workflow.
AGENTS AND MODELS
devctrl runs every agent below in the same persistent workspaces on your servers. Files, resources, approvals and session history work the same for all of them. What differs is how much devctrl manages inside the agent: accounts, quota and models for the first three, launch and resume for the rest.
Sign in with your own accounts, see quota and reset times, pick the model from the installed CLI and continue on another account when one runs out. Sessions get the devctrl MCP tools and Project messaging.
Claude Code and Codex accounts can run through one of these gateways (Cloudflare AI Gateway: Claude Code only). The key stays encrypted in the controller; sessions get a model allowlist, recorded cost and an optional monthly budget.
devctrl installs, starts and resumes each of them in a managed workspace; all 24 passed that check on Linux x64. These are partial adapters without quota tracking. Pi, Gemini CLI and Qwen Code sessions also get the devctrl MCP tools and Project messages. Run more agent CLIs
Messages, delegated tasks and handoffs that one agent sends to another are screened before delivery. By default, binaries, encoded data and code-like content wait for your approval.
01 / INFRASTRUCTURE CONTROL
Run the controller and browser gateway on a server you control. Keep repositories, workspace data and credentials on the infrastructure you choose.
Connect an existing server over SSH or use a console link over HTTPS/WSS. Pair local Docker for local execution. Cloud adapters provision compatible hosts; sandbox adapters expose separate API environments. Docker-managed sessions require a Docker-capable adapter. Choose your compute
A modest laptop can control many remote sessions. Dependency installs, containers and background jobs use the servers’ CPU, memory and disk; your computer only needs to run the client.
SESSION → WORKSPACE → COMPUTE
Your infrastructure runs the work.
WAYS TO RUN IT
Put Core, Hosts and consoles where they suit your work: everything on a laptop, agents on a server while Xcode builds on your Mac, or one server shared by a team. Each configuration shows what runs where.
For trying devctrl or working solo, with no server to set up.
LAPTOP → LOCAL DOCKER → AGENTSSOLO · ONE SERVERFor one developer who wants agents to keep working while the laptop is closed.
LAPTOP / PHONE → SERVER → WORKSPACESCLOUD · HOME NETWORKFor a machine behind a home router, reached from a phone or laptop on any network.
PHONE → EDGE → ENCRYPTED TUNNEL → HOME SERVERCLOUD · SEVERAL SERVERSFor one person with a home server, an office server and a GPU box.
SIGN IN ONCE → EVERY SERVER → ITS OWN ADDRESSCLOUD · TEAM ORGANIZATIONFor a team that signs in to its servers with one account per person.
INVITE → MEMBERS → SIGN IN WITH DEVCTRL CLOUDCLOUD · CONTRACTORSFor giving a contractor or client access to some of your servers, not all of them.
INVITE → ADD TO ONE SERVER → OTHERS STAY HIDDENAPPLE PLATFORMS · MAC + SERVERFor iOS and macOS developers whose builds and simulators need a Mac.
AGENT EDITS → LOCAL COPY → XCODE BUILDMIXED · TWO HOSTSFor keeping quick sessions on the Mac and sending heavy work to the server.
ONE CORE → TWO HOSTS → A HOST PER PROJECTTEAM · SHARED SERVERFor several developers sharing compute without sharing environments.
USER → OWN PROJECTS → OWN CONTAINERSELASTIC · CLOUD + SANDBOXESFor running many temporary tasks in parallel without buying hardware.
CORE → PROVIDER API → TEMPORARY HOSTSTWO CORES · FEDERATIONFor keeping your own installation separate while its agents work with a team’s.
PAIR → LINK A PROJECT → MESSAGE ACROSS CORES02 / ISOLATED ENVIRONMENTS
Keep the checkout, dependencies and session data together in a persistent Docker workspace. Configure its folders, credentials and service access, then leave the coding session running.
Use the managed runtime or a supported devcontainer.json; the Host creates the container itself through the Docker API. Every new coding session gets its own working directory and Git branch. Reuse a compatible container, or start another for separate processes and resources.
Attach selected local or remote folders with read-only or read/write access. Grant fixed-target service routes and deliver selected runtime secrets. MCP tools and skills show agents the resources already configured.
Control access through container boundaries, folder permissions, runtime credentials and enforced Internet allowlists. New or rebuilt restricted workspaces keep required agent endpoints reachable on rootful Docker 28+ or Rootless Docker 29.9.1+.
Give developers access to shared compute, with private projects, accounts, storage and containers for each person. Manage the team’s infrastructure from one server console.
Each user’s work runs in separate containers, account homes and storage. Teammates can work on the same repository in their own environments.
Connect your own Claude, Codex, Antigravity and Git accounts. Runtime credentials go to your workspaces, and private session history stays with you.
Publish selected APIs, databases, folders and model endpoints to the team. Grant access per project while keeping each developer’s containers and credentials separate.
Plan CPU, RAM, storage and workspace capacity across all of a developer’s containers. Track measured use alongside reservations and enable hard caps on supported hosts.
See every Claude, Codex and Antigravity session by project, account and host. Find work waiting for input, check quota and continue from another eligible account when needed.
Send context, connect resources and manage updates and cleanup alongside the sessions. Detach and return from the terminal or browser while the server keeps working.
Open the Task Graph to follow each session: the plan its agent reports, one line per conversation turn and what is waiting for you. Follow what each agent is doing
Leave the agents working. Let Overnight turn the server off. Enable it before you leave; when every session finishes or needs your input, devctrl shuts down eligible cloud compute through its hosting adapter. Set up Overnight
From your Mac, choose between two remote servers for different projects. Leave sessions running when you disconnect, return to the same workspace, and grant access to the specific services each project needs. Docker containers share the host kernel; a separate worktree separates working files, not infrastructure.
Run doctor for configuration and telemetry checks without an AI account. Inspect repository technologies, partial parser coverage and suggested skills before activating a pinned bundle. Additional analysis uses an explicitly assigned, admitted Control Room account; unavailable checks stay visible. Diagnostics and technology coverage
Drop screenshots, documents or datasets into a remote workspace. Download reports, builds and archives from your browser. Enable a two-way folder mirror when you want files synchronized with your computer.
Connect APIs, databases, model endpoints, GPU hosts and folders once. Give selected projects the resources they need, with read-only or read/write folder access and connection health in view.
Need a custom connection? Write a gateway in TypeScript or another runtime. Register it on your host and grant selected projects access. Your integration code stays outside devctrl. Build your own gateway
Built-in MCP tools and skills tell agents how to use configured connections. Review additional access requests in the console and deliver approved changes to the running session.
Search running, frozen and stopped Claude and Codex sessions by words or by meaning, then open the match, restore the session or hand the work off. Choose a local embedding model or your own provider key. Search your sessions
Archive ended sessions to your own S3 storage under a dedicated encryption key. Free local history once the copy is verified, and restore it when you need it. Core also writes a complete copy of its database every day. Archive and restore sessions
Import local Claude Code and Codex sessions directly into devctrl Cloud or your own S3 bucket. Connect multiple buckets and choose the default for new imports. See the project and repository for each import and download the original history. Continue an imported session on a managed Boat sandbox using your subscription.
Every devctl command that reaches the controller is also a typed MCP tool with the same authorization, so Control Room and your own agents can manage schedules, reviews, hosts and Projects directly. Drive devctrl through MCP
Run a schedule now without moving its next slot. Attach your own terminal to a session’s tmux with devctl remote-terminal, and complete commands in bash, zsh or fish. Attach to a session
THE SAME DEVCTRL. ANOTHER WINDOW.
Start sessions, choose repositories, connect resources and move files with browser controls. Review changes as a folder tree, edit session names and manage CLI updates. Desktop and mobile use the same React screens and authenticated server API.
Host the controller and gateway remotely to keep the console available when your laptop is offline.
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Coming soon
Coming soon
Installation currently requires authorized source access. An anonymous GitHub source download was unavailable at the latest check. Read setup and source-access requirements.
05 / HOW IT WORKS
Setup adds missing server dependencies, prepares the controller and workspace, and imports only the accounts you select. A repository URL leaves just a small Python/SSH launcher on your computer. Pass a local Git folder instead to read its remote and automatically install the Exchange sync client too.
curl -fsSL https://devctrl.dev/install.sh | sh -s -- 'https://github.com/devctrldev/devctrl.git' 'remote-server'The TUI runs on the server over SSH; the browser connects to the server’s gateway. Neither needs local Docker. Disconnect your laptop and the controller, web console and coding sessions stay online.
devctrl tui remotedevctrl web remoteStarted with a local Git folder? Its agent-interchange sync is already configured. Started with a URL? Add the same client whenever you want. It pulls a prebuilt Docker image and needs local Docker plus an unlocked SSH agent. No local controller; browser uploads and downloads need no helper.
devctrl client installTo run workloads on your computer too, explicitly connect local Docker as an execution host. Only this additional module gets access to its Docker socket.
devctrl host install localStart with an Ubuntu server and working SSH access. Optional folder sync requires local Docker, an unlocked SSH agent and trusted host keys. Local client setup and boundaries
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.