claude-code - 💡(How to fix) Fix System prompt size grew ~70K tokens between v2.1.89 and v2.1.96, making sessions unusable without frequent manual /compact [4 comments, 3 participants]

Summary

Between Claude Code 2.1.89 and 2.1.96 (approximately 5 days, early April 2026), the initial system prompt size grew by approximately 70K tokens. This is large enough to make sessions effectively unusable: with auto-compact disabled (as I had it configured at the time), the context would fill before I could complete any non-trivial task, and Claude Code stopped accepting input entirely. I had to introduce a manual /compact workflow as an emergency measure just to keep working.

Environment

• Claude Code versions affected: 2.1.89 → 2.1.91 → 2.1.92 → 2.1.96
• OS: Windows 11 (Git Bash shell)
• Models: claude-opus-4-6 / claude-sonnet-4-6
• Setup: standard user install + a few user plugins (LSPs, code-review, feature-dev, hookify)

Measurement Method

I correlated the usage.cache_creation_input_tokens field of the first assistant message in each session JSONL against the version field, across all sessions under ~/.claude/projects/<id>/*.jsonl.

The first assistant message has no cache hit yet, so its cache_creation_input_tokens reflects the full initial system prompt assembled by the binary — independent of any additionalContext injected by UserPromptSubmit hooks.

import json
from pathlib import Path
from collections import defaultdict

proj = Path.home() / ".claude" / "projects" / "<your-project-id>"
by_version = defaultdict(list)

for jsonl in proj.glob("*.jsonl"):
    first_cache = None
    version = None
    with jsonl.open(encoding="utf-8") as f:
        for line in f:
            try:
                d = json.loads(line)
            except json.JSONDecodeError:
                continue
            if version is None and d.get("version"):
                version = d["version"]
            usage = (d.get("message") or {}).get("usage") or {}
            cct = usage.get("cache_creation_input_tokens")
            if cct and first_cache is None:
                first_cache = cct
                break
    if first_cache and version:
        by_version[version].append(first_cache)

for v in sorted(by_version):
    vals = sorted(by_version[v])
    print(f"{v}: n={len(vals):3d}  median={vals[len(vals)//2]:6d}  max={max(vals):6d}")

Observed Data

Two distinct step changes: +40K at 2.1.91, +30K at 2.1.96. Total growth: ~70K in 5 days.

Impact

I had auto-compact disabled during this period (I was testing with it off). As the system prompt grew past ~100K+, sessions would fill up before completing any multi-step task. Claude Code stopped accepting new input. I had to run manual /compact continuously as an emergency workaround just to keep the tool usable. This persisted until I re-enabled auto-compact and tuned the threshold.

Even with auto-compact enabled at the default threshold, the effective usable context has shrunk dramatically: a 70K larger baseline means 70K less room for actual conversation and tool output.

What I Already Ruled Out

• UserPromptSubmit hooks (additionalContext): affects later cache blocks, not the first cache_creation_input_tokens. Verified by disabling my hook chain — first-cache size unchanged.
• MCP servers: removed candidate MCPs, re-measured — first-cache size unchanged.
• Plugin count: removed 5 stale LSP plugins, re-measured — first-cache size unchanged.
• Session state / bistability: sessions started with /clear show ~50–60K smaller first-cache than sessions resuming work. Both classes show the same version-correlated step changes, so the jumps are not session-state artifacts.

The growth correlates exactly and exclusively with binary version bumps.

Suspected Sources of Growth

Based on inspection of what appears to have changed in the system prompt area between these versions:

• Skill listing attachment (skill_listing type) — my session shows ~7KB for 47 skills injected on every turn
• New or expanded injection-defense / safety layers
• New tool descriptions (Skill tool, browser-automation tool suite, Plugin subagent descriptions)

Asks

1. Confirm whether the ~70K growth between 2.1.89 and 2.1.96 is intentional and which components account for it.
2. Consider lazy-loading or deduplicating large fixed blocks (skill listings, agent descriptions, plugin metadata) so they only appear when the relevant capability is actually needed.
3. Expose first-cache / baseline system-prompt size in /status or a debug flag so users can monitor it without parsing session JSONLs.
4. Document the expected baseline range per version in the CHANGELOG so users can anticipate and plan around context budget changes.

Reproducibility

Anyone with multiple session JSONLs spanning versions 2.1.89–2.1.96 can run the script above and reproduce the version-vs-size correlation in a few seconds.