{"version":"2.1.280","anchor":"write-tool-now-accepts-file-textfile-content-and-path-as-al","canonical_anchor":"write-tool-now-accepts-file-textfile-content-and-path-as-al","heading":"Write tool now accepts file_text\/file_content and path as aliases","tier":"soon","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/write-tool-now-accepts-file-textfile-content-and-path-as-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Write tool now accepts file_text\/file_content and path as aliases\n\nWrite tool now accepts file_text, file_content, and path as aliases for content and file_path, rewriting input before plugin hooks see it\n\n**Unclear.** Whether the tengu_noble_mountain gate controls this behavior is unread for this account, so it's not stated here.\n\n**What**\n\nThe Write tool now coerces certain input fields before they reach plugin hooks:\n\n- a `path` field is read as `file_path` if `file_path` is absent\n\n- either `file_text` or `file_content` (but not both) is read as `content` if `content` is absent\n\n- a `description` field, if present, is silently dropped\n\nA note explaining what was coerced is attached to the result.\n\n**Why**\n\nThis makes the Write tool more tolerant of slightly different field names, so calls using `path` or `file_text`\/`file_content` instead of the exact expected field names still work rather than failing outright.\n\n- Flag `tengu_noble_mountain`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Elsewhere\n- Names: `file_text`, `file_content`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}