Files
codegraph/__tests__
danusha2345andClaude Opus 5.5 47526d2078 feat(serve): --no-telemetry turns telemetry off for one MCP server entry
A team that shares an MCP config had no way to opt one server entry out of
telemetry without an environment variable, which not every client lets a
shared config set. Issue 1908 asked for a flag.

serve --no-telemetry sets CODEGRAPH_TELEMETRY=0 for the process, the same
chokepoint --no-watch uses for CODEGRAPH_NO_WATCH, so there is no new
telemetry code path: telemetry reads the variable on every check, and the
background daemon a server spawns inherits its environment. A daemon that is
already running keeps its own setting until it exits, which TELEMETRY.md
states; codegraph telemetry off covers every process.

Changes on top of the contributor's commit: the test spawns the server with
the WASM runtime flags, as AGENTS.md requires on Windows (without them the
re-exec'd grandchild keeps the temp dir open past the child's exit), and the
changelog bullet states the limit and credits the author.

Validated with real proxy-to-daemon runs on Windows against opted-in private
homes, reading the telemetry queue each daemon left on exit:
- a flagged client starts the daemon: nothing recorded;
- control, no flag: the tool call is recorded;
- a flagged client joins a running unflagged daemon: its call is recorded,
  the documented limit;
- an unflagged client joins a flagged daemon: nothing recorded;
- codegraph telemetry off with a daemon running: nothing recorded.

Original PR #1923 by @danusha2345.
Fixes #1908

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 19:31:16 +00:00
..