chatcode.dev
Remote Control for Claude Code and Codex
Last verified:
What is chatcode.dev?
Chatcode.dev is a remote control platform for Claude Code and Codex AI coding agents. It allows developers to run AI coding agents on their local machine with a Claude or ChatGPT subscription, while keeping them fully reachable from anywhere through the chatcode.dev service. This enables remote access to your local coding environment and AI agents.
Key features include running agents locally on your machine, remote accessibility through the platform, support for both Claude Code (Anthropic) and Codex (OpenAI) agents, and maintaining your local files, tools, credentials, and approvals on the host machine while enabling remote control. The service acts as a relay between remote devices and your local Claude/Codex session.
This tool is designed for developers who use Claude Code or Codex CLI and need remote access to their coding agents. It is particularly useful for developers who want to work on their local codebase from different devices, maintain local-first workflows while enabling remote collaboration, and leverage their existing Claude.ai or ChatGPT subscriptions for remote agent access.
chatcode.dev pricing
Pricing model: Freemium
Chatcode.dev uses your existing Claude.ai or ChatGPT subscription - there is no additional pricing for the service itself. You need a Claude.ai subscription for Claude Code remote control, or a ChatGPT subscription (including Free tier) for Codex. The service does not charge extra fees beyond what you already pay for your AI subscription.
chatcode.dev pros
- Runs agents locally on your own machine
- Requires only existing Claude or ChatGPT subscription
- No extra cost beyond your subscription
- Files and workspace stay on your host machine
- Credentials and approvals remain local
- Full remote accessibility from anywhere
- Supports both Claude Code and Codex
- Uses signed-in remote device with relay
- Maintains local-first workflow shape
- No need to set up custom infrastructure
- Reusable server with URL and QR code
- Supports standalone Codex app-server
- Optional CLIProxy routing available
- Keeps real session running on connected host
- Only sends control events and receives session updates
chatcode.dev cons
- Requires Claude.ai subscription login (API-key auth cannot create remote session)
- Local machine must be running for agents to work
- Requires ChatGPT/OpenAI OAuth authorization
- Network dependency for remote relay connection
- May have connection errors if WebSocket ends in error state
- Device must be toggled off in settings if token revoked
- Requires Node.js 18.18 or later for setup
- Only forwards prompts, approvals, and status remotely
Frequently asked questions about chatcode.dev
What is chatcode.dev?
Chatcode.dev is a remote control platform for Claude Code and Codex AI coding agents. It keeps your locally running agents fully reachable from anywhere by acting as a relay between remote devices and your local Claude/Codex session.
How does remote control work?
You run agents on your machine with a Claude or ChatGPT subscription, and chatcode.dev keeps them fully reachable from anywhere. A signed-in remote device talks through a relay while the real session keeps running on your connected host machine.
What subscriptions do I need?
For Claude Code remote control, you need a claude.ai subscription login. For Codex, you need a ChatGPT subscription (including Free tier) or an OpenAI API key plus Node.js 18.18 or later.
Where do my files stay?
Files, workspace, tools, plugins, and credentials all stay on your host machine. The remote control only sends control events and receives session updates - your local files never leave your machine.
Can I use API keys instead of Claude.ai login?
No. Remote Control needs a claude.ai subscription login. API-key or Console auth cannot create the remote session for Claude Code.
What is the server mode?
Server mode is best when you want a reusable server with URL and QR code. You run 'claude remote-control' to start it, enabling a persistent remote access point.
What happens if connection errors occur?
If you get 'Remote control is enabled but connection is errored', the cloud still tracks your device as enrolled but the WebSocket ended in error state. Stop the local daemon to clear state, then start again, or toggle the device off in ChatGPT Remote Control settings before retrying.
Can I use CLIProxy routing?
Yes, CLIProxyAPI/CCS is optional and provides account rotation, quota visibility, or failover behind the remote session. It handles model routing separately from the remote control functionality.
How do I start remote control?
You can start it three ways: using the built-in Claude Code command 'claude remote-control', opening a new session with 'claude --remote-control "My Project"', or typing '/rc/remote-control' inside a running Claude Code screen.
What is the difference between host and remote device?
The host machine runs the real Claude/Codex session with files, tools, credentials, and approvals. The remote device only sends control events and receives session updates through the relay, with no local files.