Skip to content
Run AI coding jobs. Walk away. Stay in control.

Your AI builds.
You orchestrate — from anywhere.

Check progress, answer questions, and direct your AI from any AI assistant or your phone — no SSH, no terminal.

Always-on

Your AI doesn't stop when you leave.

Runs in the background on your dev machine — survives reboots, drops, and overnight runs.

Works with ChatGPT, Claude, and more

Works with ChatGPT, Claude, and more.

Connect once via a secure link — no ports, no setup headaches. Control your sessions from whichever AI tool you already use.

Team-ready

Manage multiple machines in one place.

Multiple machines, multiple sessions, multiple teammates — all visible and controllable from one dashboard.

ChatGPT via DetachDev MCP
You
Using DetachDev, list sessions on my dev box
ChatGPT
Here are the Claude Code® sessions on dev-01:

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.

Being at your desk shouldn't be a dependency.

Your AI is doing the work. You're the bottleneck.

Situation 01

You can't leave your desk

Your AI might need input. So you sit there, watching a terminal, going nowhere.

Situation 02

You missed the question

Claude asked for approval 20 minutes ago. You were in a meeting. The session's been idle ever since.

Situation 03

You open SSH just to check in. It didn't finish.

You're on your phone. You just want to know if it's done. Instead you're fumbling with keys in Termius.

Situation 04

Your work is on a machine you can't reach

Your dev box is at the office. You're not. The session — and all its context — is sitting there, unreachable.

Situation 05

The terminal that must never close

tmux. screen. nohup. You know every workaround. You shouldn't need any of them.

Situation 06

Five sessions, zero visibility

Running parallel AI jobs across machines. No way to know which ones need you right now.

Your AI keeps coding even when you're offline. DetachDev keeps your sessions running and reachable — from your phone, ChatGPT, or Claude. No SSH. No terminal. No desk.

Get started free

Core capability

Reach your sessions
from anywhere.
On anything.

DetachDev bridges your Claude Code® environments to the AI client already in your pocket. No SSH. No open terminal. No being chained to one machine.

  • Works with ChatGPT, Claude, and other AI tools — connect via a secure link (no ports or setup headaches)
  • Mobile-friendly — approve, instruct, and review from your phone or tablet
  • Your AI keeps working when you're offline — sessions persist through reboots, drops, and overnight runs
  • Every machine, one view — switch between VMs and regions without losing track
● Connected via MCP
You (from phone)
"Using DetachDev, start a new session on dev-01 for the invoicing project and scaffold the REST API"
AI client
New session started on dev-01 for the invoicing project. Claude Code® is working on your prompt. I'll pass back the output as it comes through.
Actual responses depend on your AI client and Claude Code® environment.

Built for developers who can't afford to stop.

Every feature answers the same question: how do we keep you in control without keeping you at your desk?

Always-on Claude Code sessions

Start a session and walk away. The daemon keeps it alive through reboots, network drops, and terminal closes. Resume it from anywhere, any time.

We catch what you already started

Launched a session from your terminal before you knew about DetachDev? It's captured automatically and available remotely — zero workflow changes.

Nothing gets lost

Every prompt, tool call and response is captured and indexed. Search across your entire history. Export transcripts as JSON or CSV whenever you need them.

Your team, not just you

Invite teammates, assign roles, share device pools. Full access controls so the right people see and do exactly what they should — and nothing they shouldn't.

Every machine. One dashboard.

Register your laptop, your dev server, your cloud VMs. Manage sessions across all of them without juggling terminals or SSH configs.

Full control from the dashboard

Browse sessions, manage devices, edit prompts, configure playbooks and handle billing — all without touching a command line.

Let it run while you sleep

Chain sessions into automated workflows with approval gates, webhooks and conditional steps. Work happens. You get notified when you're needed.

Your code never leaves your machine

DetachDev relays commands and output — nothing else. No inbound ports, outbound-only connections, bcrypt device tokens, full audit trail.

Full Claude Code control from your phone

Approve prompts, give instructions and review output from wherever you are. No laptop. No VPN. Just your AI client and a connection.

Up and running in minutes.

No complex config. No open ports. No devops degree required.

Step 1

Install the daemon on your dev machine

Install the DetachDev client and it starts immediately as a background service — connecting outbound, opening no ports, staying out of your way.

$ curl -fsSL get.detachdev.io/install.sh | sh
Step 2

Connect it to ChatGPT or Claude

Paste your personal link into Claude.ai® or ChatGPT® — takes 30 seconds. Works with any AI tool that supports custom connections.

your link https://mcp.detachdev.io/u/your-token
Step 3

List and resume your sessions

Ask your AI client to list your sessions. Pick one up, start a new one, or check what's waiting for input — all without touching a terminal.

Step 4

Go do something else

Your sessions keep running. You get notified when you're needed. Your code ships while you live your life.

Your code never leaves your machine.

DetachDev relays commands and output — that's it. Your source code stays on your hardware. Every action is logged.

No open ports. Ever.

  • Outbound-only WebSocket from your device
  • Nothing listening on your machine
  • TLS encrypted in transit, end to end

Every action is attributed

  • Every MCP call logged: user, device, timestamp
  • Immutable audit trail — tamper-evident
  • RBAC so every person has only what they need

Access that can be revoked

  • Per-device tokens, bcrypt hashed
  • Revoke any device instantly from the dashboard
  • OAuth 2.1 with PKCE for external integrations

Enterprise-ready from day one

  • SSO, SCIM provisioning, data residency
  • Encryption at rest, KMS, legal hold
  • On-prem deployment available
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?

Unlike SSH, tmux, or remote desktops — DetachDev is built for AI workflows, not humans typing commands. Unlike Claude Remote Control — you're not locked into one AI tool.

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

Frequently Asked Questions

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.

Your next session is already waiting.

Set up DetachDev in minutes. Start managing your Claude Code® sessions from anywhere — free to start, no card required.