Claude Code documentation includes excessive React components inflating token counts

A developer building a PDF and Dash docset tool for Claude Code documentation discovered significant token inefficiency in the official documentation files.
Key Findings
The analysis revealed that the .md files linked from llms.txt are actually MDX files containing substantial React component code alongside documentation content.
Specific examples from the source:
- The context-window.md page contains 18,501 tokens total
- Only 551 tokens of that total represent actual documentation content
- The remaining tokens consist of animation engines, a fullscreen toggle handler, and other React components
- The quickstart.md page includes A/B testing infrastructure with GDPR consent detection
The developer verified these token counts against Anthropic's own API, confirming the measurements.
This discovery was made while building a documentation tool that processes these files, highlighting how embedded React components in MDX files can dramatically increase token counts without adding documentation value.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claw Code Agent: Python Reimplementation of Claude Code Architecture for Local Models
Claw Code Agent is a Python reimplementation of the Claude Code agent architecture that runs with local open-source models through OpenAI-compatible backends like vLLM and Ollama, featuring tool calling, slash commands, and tiered permissions.

Sandra: open-source persistent graph memory MCP for Claude
Sandra is a graph + vector memory backend with a native MCP server that gives Claude persistent structured memory across sessions, supporting exact, fuzzy, and semantic search.

Agenexus: Agent-Native Platform for Autonomous AI Collaboration
Agenexus is a platform where AI agents register themselves via a SKILL.md file, complete capability challenges verified by Claude API, and get semantically matched for collaboration without human intervention. Built with Next.js, Supabase, Voyage AI embeddings, and Claude API.

Approval Boundary Tool for Claude Code Repository Work
A developer built an approval boundary tool that adds a review step before local execution when using Claude Code for repository work. The tool follows a loop: see the plan first, approve once, let the run happen locally, and keep proof afterward.