chatcode.dev – Remote control for Claude Code and Codex

Remote control for

Claude Code and Codex

You run agents on your machine with a<br>Claude or ChatGPT subscription ;<br>chatcode.dev keeps them fully reachable from the<br>browser and Telegram.

Start free

See how it works

Free to start

Use your own AI account

Code stays on your VPS

~/workspace · claude-code<br>live

What it is<br>A small piece of glue between<br>your browser and your server.

You bring a server. We give you a clean way to run AI agents<br>inside it – visible from anywhere, with persistent session continuity<br>and a simpler browser workflow than raw SSH alone.

Browser terminal

A full xterm-compatible terminal in a tab. Drag-and-drop file<br>upload, scrollback, copy/paste – all the things you'd expect.

Persistent sessions

Each session stays alive on your server. Close your laptop, walk to a<br>café, reopen – your agent is still there, still mid-thought.

Your VPS, your data

Code, secrets and tool state all live on the server you<br>control. We don't store your repos and we don't keep your SSH<br>private keys.

Bring your own AI

Works with the Claude Code, Codex, Gemini and OpenCode CLIs –<br>signed in with your own account or key. We don't proxy<br>inference through our own credentials.

Continuity across devices

Same session, same agent, same context – whether you opened<br>it on desktop, mobile web, or through linked Telegram views.

Sandbox toggles

Per-session sandbox switch for Claude, Codex and Gemini. You<br>decide whether the agent gets full access or stays in a box.

How it works<br>From signup to a live session in a few minutes.

Four steps and one of them is &ldquo;wait roughly thirty seconds for<br>your server to come online.&rdquo;

Sign in with your email

Magic-link auth. No password to remember, no extra account<br>to manage.

Hook up a server

Easy mode: connect DigitalOcean and we'll spin up a droplet<br>for you. If you'd rather bring your own server, install the<br>Chatcode connection there and attach it to your account.

Open a session

Pick a workspace folder under ~/workspace,<br>pick an agent (Claude, Codex, Gemini, OpenCode) and you<br>land in a real shell. Sign into the agent once, the way<br>you would on your laptop.

Keep it running

Sessions stay alive between visits. Drop files in by<br>drag-and-drop, get Telegram updates when long jobs<br>finish, and reattach later from anywhere.

Agents you can run<br>The CLIs you already use, ready on your server.

Claude Code and Codex are the fastest path on a fresh setup.<br>Gemini and OpenCode can be added from the app when you need them.

Claude Code

anthropic · sandbox

Codex CLI

openai · sandbox

Gemini CLI

google · sandbox

OpenCode

community · BYO key

Continuity<br>One session, every device you carry.

The browser is the main view, but you don't always have the<br>browser. Link Telegram and follow the same session from the<br>Mini App and linked chats. The browser stays the main<br>terminal view; Telegram handles continuity and notifications.

Same session across web and Telegram.

Telegram updates for session activity and long-running work.

Mini-app pages for picking a server and resuming a session.

Browser stays the full terminal; Telegram is the continuity layer.

Browser<br>app.chatcode.dev

Chatcode<br>connection layer

Your server + gateway<br>Chatcode daemon on your VPS

Agent session<br>Claude / Codex / Gemini

browser ⇄ chatcode ⇄ your server

Ownership & honesty<br>What runs where, in plain words.

We'd rather be specific about the trade-offs than wave hands.<br>The short version is below.

Your code, your VPS

Files, environment variables and tool state live on the box<br>you provisioned. We don't store your repos and we don't keep<br>your SSH private keys.

TLS on every hop

Connections are encrypted in transit. Because Chatcode relays<br>terminal traffic today, the service can still see it. We're<br>upfront about that and a<br>payload-encrypted mode is on the roadmap.

Simple setup, clear ownership

You bring the server and the AI account. We handle the browser<br>access, session continuity, and connection layer without<br>turning your workflow into terminal plumbing.

Honest launch scope

Some edges are still intentionally simple while we launch:<br>no end-to-end terminal encryption yet, account-level plan<br>limits, and a gateway safety cap for runaway sessions.

Workspace-scoped sessions

Each session is rooted under ~/workspace in a<br>folder you choose. Sidebar groups by workspace, tabs show<br>the relative subpath, and nothing leaks across.

Time-limited support access

If you grant us SSH for a debug session, it's an opt-in<br>key with auto-expiry. You can revoke it in the dashboard at<br>any time.

FAQ<br>Reasonable questions, short answers.

Is it really free?

Yes, there is a free Basic plan. Paid plans add higher<br>limits and features such as voice transcription. The other<br>costs are still yours: your VPS provider, your AI account<br>or API plan, and any paid third-party services you connect.

Do I have to use DigitalOcean?

No. DigitalOcean is the easy path because we can...