lazy-context-injection-reuse

Lazy context injection uses a module-scope TTL-decayed trigger to gate content loading until needed, applying a first-full-then-short differential strategy to reduce per-turn overhead for listing-type and invariant content in third-party API mode.

TTL-decayed context injection is a module-scope trigger mechanism that gates content loading with a configurable time-to-live window, folding listing-type content via a dormant ranker to skip injection until explicitly needed.

Set up lazy loading triggers by implementing module-scope hooks across tool calls, slash commands, and REPL keyword surfaces, using a one-shot lazy stub and a dormant rescue path to gate content injection until triggered.

Yes, you can customize TTL trigger behavior and reset it on cache clear using environment variable knobs configured under the CLAUDE_CODE_* prefix to override default module-scope gating and decay settings.

Use deferred context injection when adding non-critical listing-type sections that should skip injection until needed, leveraging a folding mechanism, dormant gate, and ranker to minimize per-turn overhead for invariant content.

Yes, lazy context loading supports test isolation and cache clearing through a zero-serialization, resettable module-scope state pattern with explicit reset functions that flush the TTL trigger and dormant gate.