Analysis of Claude Code's Instrumentation and Telemetry Capabilities

A recent analysis of Claude Code's source code reveals a highly instrumented system that tracks user interactions and environment details beyond typical chatbot functionality. The system implements multiple layers of observation and classification.

Language Classification and Sentiment Tracking

Claude Code uses simple keyword detection rather than deep AI understanding for language classification. It maintains literal keyword lists including words like "wtf," "this sucks," "frustrating," "shit," "fuck," and "pissed off" that trigger negative sentiment flags. Even phrases like "continue," "go on," and "keep going" are tracked. This classification happens at regex-level before the model responds.

Permission Prompt Behavior Tracking

The system tracks detailed user behavior during permission prompts, not just final decisions. It monitors whether users open the feedback box, close it, hit escape without typing, or type something and then cancel. Internal events have names like tengu_accept_feedback_mode_entered, tengu_reject_feedback_mode_entered, and tengu_permission_request_escape. It even counts escape attempts, distinguishing between quick rejections and hesitant behavior where users type before rejecting.

Feedback System Design

The feedback system triggers based on pacing rules, cooldowns, and probability rather than randomly. When users mark something as bad, it can prompt them to run /issue and nudge them to share session transcripts. If agreed, it can include main transcripts, sub-agent transcripts, and sometimes raw JSONL logs with redaction.

Hidden Commands and Behavior Changes

Some commands aren't obvious without reading the code. Examples include:

• ultrathink → increases effort level and changes UI styling
• ultraplan → kicks off a remote planning mode
• ultrareview → similar idea for review workflows
• /btw → spins up a side agent so the main flow continues

The input box parses these live while typing.

Telemetry and Environment Fingerprinting

Each session logs extensive data including session IDs, container IDs, workspace paths, repo hashes, runtime/platform details, GitHub Actions context, and remote session IDs. With certain flags enabled, it can also log user prompts and tool outputs. This creates a detailed environment fingerprint beyond basic usage analytics.

MCP Command Data Exposure

Running claude mcp get <name> can return server URLs, headers, OAuth hints, and full environment blocks for stdio servers. If environment variables include secrets, they can appear in terminal output.

Internal Build Instrumentation

There's a mode (USER_TYPE=ant) where it collects additional data including Kubernetes namespace, exact container ID, and full permission context with paths, sandbox rules, and bypasses. All this gets logged under internal telemetry events, allowing behavior to be tied to specific deployment environments.

The analysis concludes that Claude Code is not just a chatbot but a highly instrumented system observing how users interact with it. The level of tracking and classification is deeper than most users would expect, though the analysis doesn't claim malicious intent.