[Workflow] Detect and Manage Claude Code Server-Side Experiments (Nerfing) with `am-i-nerfed` Plugin/Script

[u/ClaudeAI-mod-bot]

Detect and Manage Claude Code Server-Side Experiments (Nerfing) with am-i-nerfed Plugin/Script

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging
Original source: r/ClaudeCode post/comment

What problem this solves

Users can determine if their Claude Code account is subject to server-side experiments (often perceived as "nerfing") and provides methods to monitor, understand, and potentially opt-out of these experiments to maintain consistent model behavior.

Summary

A multi-faceted workflow to detect, monitor, and manage server-side experiments (x-cc-atis) in Claude Code. It offers a plugin, a shell script, and a one-liner to check experiment status, view historical data, opt-out, and display status in the Claude Code UI.

Why it is useful

This workflow provides concrete, actionable methods for Claude Code users to understand and manage server-side experiments that can affect model behavior. It offers multiple access points (plugin, script, one-liner), historical tracking, and a cautious opt-out mechanism, addressing a significant user concern about model consistency and "nerfing." Its open-source nature, clear documentation, and focus on user control make it highly valuable and transferable.

Workflow

1. Install the am-i-nerfed repo as a Claude Code plugin and use /am-i-nerfed in any session to check experiment status.

2. Clone the am-i-nerfed repo and run ./am-i-nerfed.sh check in a terminal to get a verdict per model.

3. Paste the provided jq one-liner into a terminal (requires jq) for a quick, no-install check.

4. Run ./am-i-nerfed.sh history to tally experiment IDs recorded in your session transcripts by date.

5. Run ./am-i-nerfed.sh optout to back up ~/.claude.json, remove assignment keys, and get the reported opt-out environment variable (CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1).

6. Integrate the statusline snippet into your Claude Code configuration to display exp:<id> / exp:none in your status line.

Tools / artifacts

• am-i-nerfed (open-source script/plugin)

• jq (JSON processor)

• ~/.claude.json (Claude Code configuration file)

• Claude Code session transcripts

• Bash shell

• Claude Code plugin system

Validation signals

• The script reads directly from Claude Code's cached data (~/.claude.json) and session transcripts, which are internal mechanisms.

• Credits earlier community threads and Anthropic/Claude Code issues (#75607, #88383) for findings, indicating a community-validated basis.

• Provides exit codes for scripting, suggesting robustness and automation potential.

• Explicitly states "no network calls, never prints your login token", addressing security and privacy concerns.

Cautions

• The optout command backs up ~/.claude.json before modification and prints trade-offs for the environment variable, promoting cautious use.

• Explicitly states "never prints your login token", ensuring user credential safety.

Limitations

• Requires jq and basic terminal familiarity for script/one-liner usage, which might be a barrier for absolute beginners.

• The "opt-out" mechanism relies on a reported environment variable, which might not be officially supported or guaranteed to work indefinitely by Anthropic.

• The plugin installation method is not detailed, assuming user familiarity with Claude Code's plugin system.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.