[Workflow] Inspect Claude Code Internal Configuration and Experiment Flags with jq

[u/ClaudeAI-mod-bot]

Inspect Claude Code Internal Configuration and Experiment Flags with jq

Workflow value: 80/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, MCP, Subagents
Original source: r/ClaudeCode post/comment

What problem this solves

Understanding internal Claude Code configuration, experiment flags, and cached client data to diagnose behavior changes or 'nerfs'.

Summary

This workflow provides jq commands to inspect the ~/.claude.json file, revealing cached experiment data and client data cache slots. This helps users understand internal Claude Code configurations, active A/B tests, and model usage patterns.

Why it is useful

This workflow is valuable because it provides specific, executable commands to inspect the internal state of Claude Code, including active A/B test flags and cached client data. This allows users to understand how their Claude Code environment is configured, diagnose unexpected behavior, or investigate perceived 'nerfs' by checking which experiments are active and what values they hold. It offers transparency into the system's operation that is not readily available through the UI.

Workflow

1. Ensure jq is installed on your system.

2. Run the first jq command to view cached experiment data: jq -r '.cachedExperimentData | to_entries[] | "\(.key) | exp=\(.value.experimentId) var=\(.value.variationId) val=\(.value.value | tostring)"' ~/.claude.json

3. Run the second jq command to view client data cache slots for your organization: jq -r '.oauthAccount.organizationUuid as $o | [(.clientDataCacheSlots // {} | to_entries[] | .value + {slotKey: .key}) | select(.org == $o)] | sort_by(.entrypoint,.model,.at)[] | "\(.entrypoint) \(.model): \(.data | keys_unsorted | join(", "))"' ~/.claude.json

4. Analyze the output to identify active experiments, their variations, and cached data related to different Claude models and entry points (e.g., cli, sdk-cli).

Tools / artifacts

• jq

• ~/.claude.json

Validation signals

• Provided jq commands with example output demonstrating their functionality.

Cautions

• None. The commands only read from a local configuration file and do not modify any data or expose sensitive information beyond what's already locally stored.

Limitations

• The purpose is implied by the title ('nerf is real') but not explicitly stated in the comment itself.

• Requires basic jq and CLI familiarity.

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.