Public source for the client-side bridges of CodeAgent Mobile — the workflow-continuity layer for AI coding agents.
— , the terminal bridge that wraps Claude Code in a PTY and streams it to any device
Workflow-continuity bridge for AI coding agents. Wrap Claude Code or Codex in a PTY and supervise, approve, and redirect the session from any device — async. The terminal companion for CodeAgent Mobile.
2026-11-15
ดาว
—
เครื่องมือ
—
อัปไทม์
—
apps/cli
codeam-cli
apps/vsc-plugin — extension for VS Code, Cursor, and Windsurf
apps/jetbrains-plugin — plugin for the IntelliJ family (IntelliJ IDEA, WebStorm, PyCharm, Rider, GoLand, …)
What is CodeAgent Mobile?
The supervision layer for agents already running in your IDE. Now that AI agents run for hours, not seconds, you no longer need to stare at a terminal — CodeAgent streams the session to your phone or web dashboard so you can approve diffs, redirect prompts, and stay in the loop async. Works with Claude Code, Copilot, Cursor, Windsurf, JetBrains AI, OpenAI Codex, Vertex AI, and any agent in your editor.
Install once in your IDE, pair with a QR, your workflow follows you across devices. See codeagent-mobile.com.
Install (users)
CLI — codeam-cli
npm install -g codeam-cli
codeam pair # generates a 6-character code
codeam # starts Claude Code with mobile control
VS Code / Cursor / Windsurf
VS Code Marketplace → search for CodeAgent Mobile · listing
Every client (CLI + both plugins) reads the same two env vars to pick which API host it talks to. Priority order — first match wins:
Variable
Effect
CODEAM_API_URL
Full URL override. Use when pointing at a custom staging endpoint or a self-hosted instance. Example: CODEAM_API_URL=https://staging-api.example.com codeam pair.
CODEAM_TEST_MODE=1
Shortcut that routes every request at the dev preview (https://dev-api.codeagent-mobile.com) without you having to know the URL. Use this when pairing from dev.codeagent-mobile.com.
(none)
Defaults to production (https://api.codeagent-mobile.com).
The shortcut exists because prod + dev share Redis: a code generated against prod-api is also valid against dev-api, so a pair started in the dev webapp completes silently against prod (heartbeats keep going to the wrong host). CODEAM_TEST_MODE=1 flips every endpoint — pairing, command relay, SSE, chunk uploads, file watcher, history — in lockstep.
# Quick check it's active:
CODEAM_TEST_MODE=1 codeam doctor
# api https://dev-api.codeagent-mobile.com
# mode TEST_MODE — using dev preview
VS Code / JetBrains plugins read the same env vars from the host process — set them in your shell before launching the IDE. The apiBaseUrl setting in each plugin still works as a manual override (highest priority of all in the plugin context).
The CLI and VS Code extension share a small TypeScript package (packages/shared) that holds the chunk-protocol parser and the model-pricing tables. At build time tsup (CLI) and esbuild (VS Code) inline it into each consumer's bundle, so neither published artifact depends on a separate package at runtime. The JetBrains plugin is Kotlin and does not consume the shared package.
From 2.0.0 onwards all three clients ship under the same version line. Pushing a single tag vX.Y.Z releases [email protected] to npm, the VS Code extension X.Y.Z to both the VS Code Marketplace and Open VSX, and the JetBrains plugin X.Y.Z to the JetBrains Marketplace stable channel via the automated release workflow. Pre-release tags (vX.Y.Z-rc.N) skip the JetBrains marketplace push — the .zip is still attached to the GitHub Release for manual upload to a non-stable channel.
Publishing secrets (PAT, OVSX_TOKEN, CERTIFICATE_CHAIN, PRIVATE_KEY, PRIVATE_KEY_PASSWORD, PUBLISH_TOKEN) live in local .env files and are gitignored — they never land in this repo.
Release gate — next first, latest after the journey canary
A tag publishes codeam-cli and @codeam/shared to the npm dist-tag next
and the Box image to codeam-box:<version>. The gate job then points next
(npm + codeam-box:next, which the dev fleet runs) at that version and runs the
journey canary in codeagent-mobile against dev; the canary requires its
Box session to report that exact version. Only a green run moves latest
(npm + codeam-box:latest) — what every Box/host self-updates to, what new
Boxes and codespaces boot — and lets the VS Code / JetBrains publishes and the
GitHub Release proceed. A red run leaves latest alone, resets next and
alerts Discord. So npm view codeam-cli version can trail the newest tag by
the gate's ~10–20 min, or stay behind a tag whose gate failed — check
npm view codeam-cli dist-tags before suspecting the token. Break-glass: repo
variable CLI_RELEASE_GATE=bypass (delete it afterwards).
When a release doesn't show up on npm
The release workflow ends with a verify-published job that re-reads the
registry (npm view codeam-cli@<version> + npm view @codeam/shared@<version>)
and fails the run if either package is missing — a green release now means npm
actually serves it, not merely that the publish job exited 0.
⚠️ If npm view codeam-cli version lags the latest git tag, check NPM_TOKEN
expiry first — granular npm tokens expire after 90 days. That is what silently
broke v2.65.8 → v2.65.11 (four releases over four days: the publish jobs went
red, nobody watched the Actions tab, and npm stayed on 2.65.7). Mint a fresh
Automation token with publish rights on codeam-cliand the @codeam
scope, update the NPM_TOKEN repo secret, and re-run the failed jobs — the
publish steps are idempotent, so retries are safe.
Any failing job in the release workflow also posts to Discord via the
DISCORD_RELEASE_WEBHOOK repo secret (Settings → Secrets and variables →
Actions). If that secret is unset the workflow still fails, but only logs a
warning — set it so a broken release pings you the same day.
The clients never talk to each other. Each one connects to the backend relay and relays commands to whichever local agent (Claude Code via PTY, Copilot Chat via the VS Code API, IntelliJ terminal, etc.) the user has selected.
Contributing
Issues and pull requests are welcome. Please:
Open an issue first for non-trivial changes so we can align on scope.
Keep changes scoped to one app when possible.
Run npm run test:cli (CLI) and make sure npm run build:* succeeds before opening a PR.
For backend / mobile app / web dashboard issues, use the in-app Help & FAQ — those sources aren't in this repo.
Workflow-continuity bridge for AI coding agents. Wrap Claude Code or Codex in a PTY and supervise, approve, and redirect the session from any device — async. The terminal companion for CodeAgent Mobil
Workflow-continuity bridge for AI coding agents. Wrap Claude Code or Codex in a PTY and supervise, approve, and redirect the session from any device — async. The terminal companion for CodeAgent Mobile.
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Workflow-continuity bridge for AI coding agents. Wrap Claude Code or Codex in a PTY and supervise, approve, and redirect the session from any device — async. The terminal companion for CodeAgent Mobile.