What it does
pi-context-tree moves context routing out of model behaviour and into repository configuration. Instead of asking the agent to remember to read the docs, each folder declares, in a CONTEXT.json file, which files or URLs to inject for which path and operation.
Rules fire on precise events (session start, agent start, tool calls, subagent spawn), with budgets that bound what gets injected. The extension ships configuration and audit skills, plus commands to check status and validate the configuration.
It is a primitive I recommend to teams: context becomes deterministic, auditable, and lives next to the code it describes.