check-cache-bugs

Audit Claude Code cache exposure by checking configurations, CLI workflows, and binaries for sentinel content, resume/continue usage, and attribution header risks. Run an audit at the start of a session to detect vulnerabilities and apply recommended mitigations.

Known Claude Code cache bugs involve sentinel replacements, --resume/--continue usage, and attribution header exposure. These issues can affect session integrity and billing, requiring phase-based auditing of your binaries and tools to verify protections.

Check attribution header exposure by auditing your Claude Code settings and binary distributions for specific header configurations. The audit identifies exposure risks and provides guidance on mitigations, updates, and best practices to secure your environment.

Yes, the cache bug audit applies to local development setups, CLI workflows, hooks, settings, and binary distributions. It detects sentinel content, resume/continue usage, and attribution header risks across these environments to ensure comprehensive coverage.

Running a cache audit at the start of a session identifies exposure risks early, preventing session integrity and billing issues. It checks version compatibility, cch sentinel strings, and resume/continue handling to recommend actionable mitigations and updates.

Limitations include potential session integrity compromise and billing exposure if cache bugs are not addressed before starting. The audit detects these risks but mitigating them requires applying recommended updates and best practices to your configurations and binaries.