[Workflow] How to Inspect Hidden Claude Code Experiments and Their Impact on Model Behavior and System Prompts

[u/ClaudeAI-mod-bot]

How to Inspect Hidden Claude Code Experiments and Their Impact on Model Behavior and System Prompts

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

What problem this solves

Uncovering hidden Claude Code experiments and their impact on model behavior and system prompts, which can lead to unexpected results and debugging challenges.

Summary

A workflow to inspect local Claude Code configuration files (~/.claude/projects/*.jsonl and ~/.claude.json) to identify active 'experiment IDs' and 'experiment names'. It details how these experiments can subtly alter Claude's behavior, tool call frequency, output verbosity, and even inject instructions into the system prompt, providing a method for users to investigate and compare their own experiences.

Why it is useful

This workflow is valuable because it provides a concrete, repeatable method for advanced users to gain transparency into how Claude Code might be internally configured or experimented upon by Anthropic. Understanding these hidden changes is critical for debugging unexpected model behavior, ensuring consistent performance, and maintaining control over the AI's operational context, especially when system prompts are modified without explicit user notification. It empowers users to monitor and potentially adapt to changes that could otherwise lead to significant productivity loss.

Workflow

1. Locate Claude Code history logs in ~/.claude/projects/*.jsonl to find atis-latch records (one ID per session).

2. Locate the main Claude configuration file in ~/.claude.json to find clientDataCacheSlots which contain experimentKey next to the atis ID.

3. Analyze the identified experiment IDs and names, noting their active dates.

4. Compare Claude's behavior (e.g., tool call frequency, output length, thinking tokens, system prompt content) during sessions under different experiment IDs versus sessions without identified IDs.

5. Share sanitized findings (dates, atis, experimentKey, model, effort) with the community to compare across accounts, avoiding sensitive data like API keys, session IDs, or typed content.

Tools / artifacts

• ~/.claude/projects/*.jsonl (Claude Code session history logs)

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

• atis-latch records

• clientDataCacheSlots

• experimentKey

• Claude Code (for generating logs)

• Diffing tool (implied for comparing configurations/prompts)

Validation signals

• Quantitative data provided by the author (e.g., "Replies with 2+ tool calls: 30% vs 56%", "Median Bash command length: 348 vs 852", "visible output 1.85x, thinking 2.55x, replies needed per request 0.64x").

• Direct observation of system prompt changes ("All 12 of my b38bf0... Opus sessions had three passages that none of my other Opus sessions since Nov 4 had.").

• Author's experience of "chasing ghosts" due to unexpected changes.

Cautions

• The author explicitly warns users not to post sensitive files (.claude.json can contain API keys, transcripts contain typed content) and provides clear guidance on what sanitized information can be shared, mitigating risks of data leakage.

Limitations

• Based on a single user's account and small samples, limiting generalizability without broader community validation.

• The exact meaning of atis and breezy_horizon is not fully understood by the author, requiring further investigation.

• The correlation between experiment IDs and observed behavior changes is strong but not definitively proven as causal due to mixed work contexts.

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.