context-budget

To audit your Codex context window, scan loaded workspace components like agents, skills, rules, and MCP servers to estimate token usage and identify bloat. This process flags oversized descriptions and overlapping rules, generating a ranked report of the biggest token-saving opportunities.

Your Codex session feels crowded because heavy agent files, redundant skills, and MCP configurations consume excessive context window tokens. Auditing workspace components detects this bloat and identifies overlapping rules, showing exactly where the token budget is being wasted.

The best way to check context headroom before adding new MCP servers is to run a pre-expansion capacity planning audit. This estimates current token consumption across agents and rules, ensuring you have enough available context budget for the new tooling.

Detect overlapping rules and redundant skills by running an overlap detection analysis on your workspace components. This classifies loaded agents and rules, highlighting redundant configurations that waste context budget so you can remove or lazy-load them.

You can troubleshoot session performance issues by analyzing context budget consumption to find heavy agent files and oversized descriptions. This workspace maintenance audit identifies components causing performance degradation, providing ranked recommendations to optimize token usage.