Context Audit

Read-only, evidence-based context auditing and optimization for agent sessions.

Overview

Context auditing identifies what consumes the context window, distinguishes static prefix overhead (system prompts and tool schemas) from dynamic accumulation (conversation history and tool outputs), and measures actual token changes across iterations without guessing.

Russian reference: references/methodology.md covers methodology, attribution, and OMP runtime context internals. Additional schema details are documented in references/omp_schema_evidence.md.

Core Principles

1. Measure Before and After: Always establish a concrete baseline before recommending or applying context changes. Never claim savings without comparative measurements from the same workload.
2. Prefix Caching != Window Reduction: High prompt-cache hits reduce latency and cost, but do not free context space or reduce attention distraction.
3. Separate Static Prefix from Dynamic History: System prompts and tool schemas persist across all turns; message history grows per turn. A 500-token tool schema cut reduces every request, while conversation compaction addresses cumulative growth.
4. Physical Deduplication Saves Zero Prompt Tokens: Moving files to symlinks, pruning unread disk folders, or deduplicating storage has zero effect on prompt tokens unless those files were loaded into context or tool definitions.
5. Protect Critical Working State: During active debugging, never mask active error messages, failing test outputs, or user constraints. Mask only resolved intermediate steps.
6. No Silent Mutation: Context auditing is strictly read-only. Never disable tools or rewrite prompt files automatically.