Copilot's instruction file is read at the repository root only, and every instruction file left out says why, in words, in context.get and the session's log¶
Decision 806 · accepted · 2026-10-06 · issue #123 · supersedes 706
Superseded in part
In part by 828.
- Copilot's file at the root only. At the repository root it is the fourth alias,
as before: read when it is the only name there, skipped behind the others. In any
other directory it is not an alias at all: it hides nothing, and it is listed as
skippedwithnot read: Copilot's file counts only at the root, so nobody debugs a file that was never loaded. Not read from the person's own<config>either, and listed the same way if one is there: Copilot's file is a repository's, and the person's own file is<config>/AGENTS.md. Not chosen: reading it nested as well (706's), which reads what Copilot does not; dropping it everywhere, which leaves a repository with only a Copilot file with nothing. This is the part of 706 it supersedes. The maintainer's choice. - A reason, in words. Every file in
context.getand in theinstructions_loadedevent carriesreason: null for a file that reached the prompt (and the brief when it isabsentordisabled), and for one left out, why, in the words a person reads:not read: outside the repository(outside the config directoryfor the person's own file, Decision 798's edge),skipped: AGENTS.md is used in this directory,not read: Copilot's file counts only at the root,left out: the budget was spent on nearer files. Words rather than codes, so that every client says the same thing without a table of its own to keep in step with this one;statusstays the code a program branches on. - A skipped alias is a file of its own. Each alias the first name hid is listed
right after that file and what it imports, with
status: skipped,sizeandchars0 andhashnull, as anoutsidefile is, and its reason naming the first:is usedwhen that one was read,comes firstwhen it was not (a link out, which still hides the others, Decision 798). The first file'sskippedkeeps naming them, since a v1 field is never dropped or retyped, and a client that reads only it is right as it was. A skipped file is not counted as read: an@import may still bring it in. - An import not followed keeps its code.
unfollowed[].reasonis v1's already (missing,outside,depth,cycle) and is not retyped;/contextputs it in words (TUI Decision 148). - Additive to v1. A new key on each file, a new
statusvalue and new entries infiles. Neither the result ofcontext.getnor the event'sfilesitems are in the committed schema, andmix troupe.schema.difffinds nothing.
Governs: apps/troupe_core/lib/troupe/instructions.ex