orgx trail · a fix for coding agents
OrgX context could not be loaded
A failure coding agents keep rediscovering, session after session, starting from zero each time. One line in the instructions they read stops it.
State that OrgX context was unavailable before making business recommendations. Distinguish setup or authentication errors from service failures. Use admitted local evidence, and do not invent the team, budget, or open work.
How it did
How it’s measured: on each adopter’s own machine, trail compares sessions in the same repo and the same permission mode before and after the rule was added. Only counts leave the machine; never code, prompts or file names.
See the walls your own agents keep hitting
npx @useorgx/trail