{"version":"2.1.275","anchor":"subagent-file-report-note-wording-changed-for-zero-directory","canonical_anchor":"subagent-file-report-note-wording-changed-for-zero-directory","heading":"Subagent file-report note wording changed for zero-directory runs","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/subagent-file-report-note-wording-changed-for-zero-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Subagent file-report note wording changed for zero-directory runs\n\nSubagent file-report note now distinguishes zero-directory runs from restricted-but-listed file access\n\n**What**\n\nWhen a subagent (a Claude Code task delegated to a separate agent) finishes, its tool results include a note about which files it's allowed to claim as its own work. This note now has different wording depending on the situation: if no save directories are configured at all, it says the subagent produced \"no files during this run\"; if saves are restricted but some files are still trustworthy, it now says the subagent may claim \"only the files this note lists or counts.\"\n\n**Why**\n\nThis makes the file-attribution note more precise, so it's clearer whether a subagent had no file output at all versus limited, specifically listed file output.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}