Anthropic · 2026-09-24 · major
Claude Code 2.1.282 — project settings can no longer switch on telemetry export
Claude Code 2.1.282 makes project and local settings ignore OpenTelemetry variables that turn on export, warns at startup about telemetry variables in a project's settings, and adds a maxProseWidth setting for wide terminals.
A cloned repo can no longer quietly turn on telemetry export, and Claude Code now tells you which telemetry variables it ignored.
Quick facts
| Version | v2.1.282 |
|---|---|
| Maker | Anthropic |
| Released | 2026-09-24 |
| Telemetry change | Project and local settings can't turn on OpenTelemetry export |
| New setting | maxProseWidth caps prose width in wide terminals |
| Auto mode | Server-side classifier by default when telemetry is off |
What is it?
Claude Code 2.1.282 changes project and local settings files to ignore OpenTelemetry variables that turn on export, set its endpoint, or capture content, such as CLAUDE_CODE_ENABLE_TELEMETRY and OTEL_LOG_*. A startup notice, plus new entries in /status and claude doctor, lists telemetry variables in a project's settings that were ignored or that turned telemetry off.
How does it work?
The rule covers the project and local settings files that sit inside a repository, so opening a cloned repo can no longer switch export on or point it at another endpoint. On a direct Anthropic API connection with telemetry off, auto mode now uses the server-side classifier by default, and CLAUDE_CODE_AUTO_MODE_SERVER=0 opts out. Several managed-settings fixes make admin locks apply even when one nested value is invalid or mistyped.
Why does it matter?
The telemetry change follows a week in which a remote feature flag tied to telemetry decided whether Claude Code read AGENTS.md, so teams are watching these switches closely. Long sessions also get sturdier: Anthropic fixed more resumed sessions that re-sent earlier messages in a changed form and dropped Claude's earlier reasoning, and a failed compaction now retries on a fallback model.
Who is it for?
Claude Code users and admins managing telemetry and settings
Frequently asked questions
- Can a repository's settings file still turn on Claude Code telemetry export?
- No. From Claude Code 2.1.282, project and local settings files ignore OpenTelemetry variables that turn on export, set the export endpoint, or capture content, like CLAUDE_CODE_ENABLE_TELEMETRY and OTEL_LOG_*. Claude Code shows a startup notice and lists these ignored variables in /status and claude doctor, so a user can see what a project tried to set.
- What does the new maxProseWidth setting in Claude Code do?
- The maxProseWidth setting in Claude Code 2.1.282 caps how wide Claude's prose is drawn in wide terminals. Tables and code blocks keep the full terminal width, so long explanations stay readable on large screens without squeezing code output or tables into a narrow column.
- Did Claude Code 2.1.282 change how auto mode works with telemetry off?
- Yes. Claude Code 2.1.282 makes auto mode use the server-side classifier by default on a direct Anthropic API connection when telemetry is off. Users who prefer the previous behaviour can set CLAUDE_CODE_AUTO_MODE_SERVER=0 to opt out.
- What changed for skills named anthropic-skills or claude-ai in Claude Code 2.1.282?
- Claude Code 2.1.282 reserves the anthropic-skills and claude-ai namespaces for skills synced from claude.ai. Local skill folders, command files and workflow commands in those namespaces no longer load, allow rules like Skill(claude-ai:*) no longer cover other skills, and MCP servers with those names list no skills or prompts until renamed, although their tools still work.
Try it
npm i -g @anthropic-ai/[email protected]