Remote shell for
Claude Code and Codex

Run both on your own machine with the Claude or ChatGPT subscription you already have. Full control from any browser, and no vendor lock-in.

Free to start Use your own AI subscription Code stays on your machine
What it is

Claude Code meets Codex
in a remote shell.

Chatcode connects your browser to a real terminal on your own server or Mac. The agents run there, in sessions that keep going when you close the tab.

Both agents, side by side

Run Claude Code and Codex in separate sessions on the same project, compare their work, or let one review the other.

Full control

Your machine and a real shell: your files, your tools, your agent settings. Choose per session whether Claude Code or Codex runs sandboxed or with full access.

No vendor lock-in

Agents sign in with your own accounts or keys, and we never proxy inference. Switch agents any time; your repos and sessions stay on your machine.

How it works

From signup to a live session in a few minutes.

Four steps and one of them is “wait roughly thirty seconds for your server to come online.”

1

Sign in with your email

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

2

Connect a machine

Easy mode: connect DigitalOcean and we'll spin up a droplet for you. Or install the Chatcode gateway on your own Linux server or Mac.

3

Open a session

Pick a folder under ~/workspace and an agent, and you land in a real shell. Sign in to the agent once, the way you would on your laptop.

4

Keep it running

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

Agents you can run

Claude Code and Codex first. Others when you want them.

Claude Code and Codex come preinstalled and have the deepest support. Add Antigravity CLI, Kimi Code, Pi or OpenCode from the app, or open a plain shell.

google · agy
moonshot · kimi
pi.dev · pi
open source
Ownership & honesty

What runs where, in plain words.

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

Browser app.chatcode.dev
Chatcode connection layer
Your machine + gateway Linux server or Mac
Agent session Claude Code / Codex / …
browser ⇄ chatcode ⇄ your machine

Your code, your machine

Files, environment variables and tool state live on the machine you connect. We don't store your repos and we don't keep your SSH private keys.

TLS on every hop

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

Time-limited support access

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

Telegram

One session, every device you carry.

The browser gives you the full terminal. Link Telegram to follow the same session from your phone, answer the agent, and hear back when long work finishes.

  • Same session in the browser and Telegram.
  • Replies and approvals from Claude Code and Codex.
  • A message when long-running work finishes.
FAQ

Reasonable questions, short answers.

Is it really free?

Yes, there is a free Basic plan. Paid plans add higher limits and features such as voice transcription. The other costs are still yours: your VPS provider, your AI account 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 spin a droplet up for you with one OAuth step. If you'd rather bring your own Linux server or Mac, install Chatcode there and attach it to your account the same way.

Whose AI tokens are being used?

Yours. Each agent (Claude Code, Codex, Antigravity CLI, Kimi Code, Pi, OpenCode) signs in inside the session with your own account or key. We don't proxy through our credentials and we don't bill you for inference.

What if I stop using Chatcode?

Your code, the agents and their logins stay on your machine. The agents are the vendors' own CLIs, so you can keep using them without Chatcode.

What happens if I close the browser?

Nothing dramatic. The session keeps running on your machine even after you close the page. When you come back, the terminal reconnects automatically.

Can the chatcode team see my code?

Your files live on your machine – we don't pull them. The service acts as a trusted relay for terminal traffic today, which means an operator with access could in theory inspect what passes through. We treat that as a real trade-off rather than a marketing footnote. End-to-end terminal encryption is on the roadmap.

How many sessions can I run?

Basic and Starter currently allow 5 active sessions total and 1 server. Plus and Pro raise those account limits. Existing sessions are not killed when a plan changes, but creating new sessions is blocked while your usage is over the active plan limit.

What does “early production” mean here?

A focused product that does one thing reliably: create or connect a server, open a terminal, and keep agent work running without losing it. A few things you might expect later – end-to-end terminal encryption, multi-user workspaces, deeper enterprise controls – are deliberately not in scope yet. We'd rather ship the boring parts well than the impressive parts unevenly.

Want to try it?

Sign in with email, point it at a server, open a session. You can be talking to a real agent on your own VPS in about the time it takes to read this page.