Is Codeam CLI safe and trustworthy?

tashan scores Codeam CLI on public evidence — tashan score 71.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Codeam CLI?

In Claude Code: run `claude mcp add codeam-cli -- npx -y codeam-cli`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Codeam CLI?

source: edgar-durand/codeagent-mobile-clients.

‹ The Index

Codeam CLI

npm

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.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Dev Tools & CI — see all ranked ›

Work: Agent configuration

Who it is for: Agent operator

Install (Claude Code):

claude mcp add codeam-cli -- npx -y codeam-cli

solid

“3 worked examples; short of deep on per-tool docs and a stated limitation”

This grade is wrong ›

tashan score: 71.0
Instruction depth: 63.0 (solid — documents the job properly, with examples you could follow)
Adoption: 2.4k/wk
Upkeep: 73.0
Freshness: 99.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 2.75.0 — this package, not its dependency tree

Runs a script at install timecodenode dist/postinstall.js || true

Reads and writes filesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-10 codeam-cli now reaches filesystem Its declared dependencies reach further into your machine than they did before.
2026-08-17 codeam-cli published 2.65.7, was 2.61.96 A new release is available.
2026-08-27 codeam-cli published 2.67.6, was 2.65.7 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Codeam CLI in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-codeam-cli.svg)](https://tashan.sh/capability/pkg-codeam-cli.html)

npm ↗ · source ↗ · pkg:codeam-cli

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?