Skip to content
Always-on Claude Code · Any AI client

Manage Claude Code from your phone, browser, or AI assistant.

Your sessions stay live. Reach them from anywhere — ChatGPT, Claude.ai, or any MCP client. No open terminal required.

Always-on systemd

Sessions that don’t disappear

Run as a daemon and resume on demand — built for reboots, drops, and real life.

AI-agnostic MCP

Your preferred AI client

Use ChatGPT (including voice), Claude.ai, or any MCP/HTTP client to control sessions.

Team-ready RBAC

Central control across machines

Manage multiple devices and users with roles, audit trails, and shared device pools.

ChatGPT · Voice Mode via DetachDev MCP
You 📱 from your phone
Using DetachDev, list sessions on my dev box
ChatGPT
Here are the Claude Code sessions on dev-01 (project dir: /home/you/projects):

1. api-refactor
session_id: 4d5e7372-07f1-4c45-80de-f725b230f3a4
last_modified: 2026-03-03T14:15:39+00:00
size: 180,729 bytes

2. react-dashboard
session_id: 09b32e19-47d3-4379-bfb5-b69967ec3f99
last_modified: 2026-03-03T16:34:44+00:00
size: 4,847 bytes
You
Resume the api-refactor session — the auth middleware test was failing, pick up from there
ChatGPT
Session resumed on dev-01. I've passed your prompt to Claude Code — it's working on the auth middleware test now. I'll relay the output as it comes back.

Core capability

Any AI client.
Any device.
Your sessions.

DetachDev exposes your Claude Code environments over a secure MCP/HTTP bridge. Connect from your phone at a coffee shop, your iPad on the sofa, or a colleague's machine across the world.

  • Claude.ai, ChatGPT, or any MCP client — connect via custom connector or HTTP action
  • Voice-first workflows — approve, instruct, and review via voice mode from your phone
  • Session continuity — list, resume, and manage sessions that are waiting for you
  • Multi-device, multi-VM — connect dev environments across machines and regions
● Connected via MCP
You (from phone)
"Using DetachDev, start a new session on dev-01 in /home/me/projects/invoicing and scaffold the REST API"
AI client
New session started on dev-01. Claude Code is now working in /home/me/projects/invoicing with your prompt. I'll pass back the output as it comes through.
Actual responses depend on your AI client and Claude Code environment.

Key features

Every feature designed around one principle: your code doesn't stop when you walk away.

Remote session management

List, start, resume and stop Claude Code sessions on any connected device without keeping a terminal open.

🧲

Local session capture

Sessions started locally in a terminal are automatically captured and made remotely controllable — zero workflow changes.

📜

Session history & search

Every interaction is captured and indexed. Full‑text search across prompts, tool calls and messages. Export transcripts as JSON or CSV.

👥

Teams

Invite teammates, assign roles, and share device pools. Full access controls so the right people can see and do exactly what they should.

🖥️

Multi‑device, multi‑VM

Connect environments across multiple VMs, regions and machines. One platform manages all your dev sessions.

🖥

Dashboard & admin

A full web interface to browse sessions, manage devices, edit prompts, build playbooks and oversee billing.

🔁

Playbooks & automation

Chain multiple sessions into automated workflows with approvals, webhooks and conditional steps.

🔐

Secure by design

Bearer tokens, device token rotation and outbound‑only connectivity keep machines safe. No inbound ports are opened.

📱

Mobile‑first workflow

Interact via voice or text from your phone — approve prompts, instruct and review output without a laptop.

How it works

Get started in four simple steps.

Step 1

Install the client daemon

Install the DetachDev client on each dev machine. It runs in the background and connects outbound automatically.

Step 2

Connect your AI client

Add the DetachDev MCP endpoint as a custom connector in Claude.ai, a ChatGPT action, or any HTTP-capable assistant.

Step 3

List and manage sessions

See all your running and paused Claude Code sessions across devices. Resume, start new, or stop sessions remotely.

Step 4

Keep shipping

Give instructions, approve actions, review output — all from your phone, tablet, or any device with an AI client. Your code never stops.

Security & architecture

Designed so your dev environments stay yours.

Authentication

  • Three-layer auth: Sanctum, shared secret, OAuth 2.1
  • Device tokens verified with bcrypt hashes
  • PKCE-protected OAuth flows

Network model

  • Outbound-only WebSocket from devices
  • No inbound ports opened on dev machines
  • TLS encryption in transit (configurable certs)

Audit & logging

  • Every MCP call logged with user, device and timestamp
  • Session metadata and command history retained
  • RBAC with roles and permissions

Infrastructure

  • Pure PHP — no framework attack surface
  • RPM-packaged for controlled deployments
  • Systemd process supervision and restart
Read more about security

Plans & pricing

Five tiers. Start free, scale as your team grows. Prices exclude VAT.

Billing:

Starter

Get started free.

£0/mo
  • 1 device connection
  • Basic session management
  • MCP endpoint access
  • Community support
Get Starter

Solo

For individual developers.

£10/mo
  • Up to 3 device connections
  • Full session management
  • Session history & search
  • Email support
Get Solo

Business

Security & admin controls.

£25/mo per seat
  • Unlimited devices
  • OAuth 2.1 / SSO integration
  • Advanced audit & compliance
  • Custom retention policies
  • Priority support + SLA
Try Business

Enterprise

At scale, your way.

Custom
  • Dedicated infrastructure
  • Custom integrations
  • On-prem / private cloud
  • Dedicated support & SLA
  • Bespoke terms
Contact Sales
Feature Starter Solo Team Business Enterprise
MCP endpoint access
Session list / resume / new / stop
Device connections 1310UnlimitedCustom
Concurrent sessions per device 13510Custom
Session history & search
Multi-user / RBAC
Shared device pools
Audit logging
OAuth 2.1 / SSO
Custom retention policies
Custom integrations
On-prem / private cloud
Support CommunityEmailPriorityPriority + SLADedicated

Prices exclude VAT/Sales Tax. Limits and terms subject to change.

Choosing between DetachDev and Claude Remote Control?

See the side-by-side breakdown: always-on sessions, client flexibility, team controls, and operational durability.

FAQ

Do I need to open ports on my dev machine?

No. The client daemon connects outbound to the platform over WebSocket. No inbound ports are required on your dev machines.

Which AI clients work with DetachDev?

Any AI assistant that can make HTTP requests or speak MCP — including Claude.ai (via custom connectors), ChatGPT (via actions), and any MCP-capable client.

What does DetachDev actually run on my server?

A lightweight background daemon — two small PHP processes that start on boot, use minimal memory, and have no external dependencies. There's no framework, no Node.js, and no database on your dev machine. It connects outbound and stays out of the way.

Can I connect multiple VMs?

Yes. Each VM runs the client daemon with its own device token. The platform aggregates all connected devices so you can manage sessions across machines from a single AI client.

Is my code exposed to DetachDev?

DetachDev relays commands and output between your AI client and Claude Code on your machine. Your source code stays on your dev machine — it's never stored on the platform.

Stop losing your flow.

Set up DetachDev in minutes. Start managing your Claude Code sessions from anywhere.