Answer: You configure the write tool in the agent configuration using toolsSettings.write with allowedPaths and deniedPaths arrays, and you can configure an external diff tool to view changes instead of the built-in inline diff by following the Custom diff tools setup instructions. Status: Confirmed Entry: tool/kiro/settings/file-write-configuration Revision: 1 Digest: sha256:e245e44bb82d9ffd (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:27Z Last changed: 2026-11-13T03:44:27Z Last verified: 2026-11-20T13:31:51Z Next check: 2026-11-21T13:31:51Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Configuration key | toolsSettings | [1] | 2026-11-20 Allowed paths option | allowedPaths | [1] | 2026-11-20 Denied paths option | deniedPaths | [1] | 2026-11-20 allowedPaths description | Paths that can be written to without prompting. | [1] | 2026-11-20 deniedPaths description | Paths that are denied. | [1] | 2026-11-20 Default diff behavior | built-in inline diff | [1] | 2026-11-20 Custom diff tools | Custom diff tools | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Built-in tools - Commands and Reference - Docs - Kiro". https://kiro.dev/docs/reference/built-in-tools/ Role: primary. Accessed: 2026-11-20T13:31:51Z Quote: ""toolsSettings" : { "write" : {" (Supports: Configuration key) Quote: ""allowedPaths" : [ "~/projects/output.txt" , "./src/**" ]" (Supports: Allowed paths option) Quote: ""deniedPaths" : [ "/d1/denied/path/" , "/d2/denied/path/**/file.txt" ]" (Supports: Denied paths option) Quote: "Paths that can be written to without prompting." (Supports: allowedPaths description) Quote: "Paths that are denied." (Supports: deniedPaths description) Quote: "By default, the write tool displays code changes using a built-in inline diff." (Supports: Default diff behavior) Quote: "You can configure an external diff tool to view changes instead. See Custom diff tools for setup instructions and supported tools." (Supports: Custom diff tools) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 31ee909a7cbf48321204eabf801bb32902210e465587b7120948dabeeaf617e6 (captured 2026-11-20T13:31:49Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:31:51Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:51Z Last attempt: 2026-11-20T13:31:51Z Notes and limitations: Extracted automatically from a single official source (section "File write"). Related: https://latestn.com/tool/kiro/settings/global-ignore-files How do I create a global .kiroignore file that applies to all Kiro workspaces? https://latestn.com/tool/kiro/settings/gui-diff-tools How do I set up a GUI diff tool like a visual editor in Kiro CLI? https://latestn.com/tool/kiro/settings/hook-file-location Where should Kiro hook files be named and located? https://latestn.com/tool/kiro/settings/extension-registry-linux How do I set up a custom extension registry on Linux in Kiro? https://latestn.com/tool/kiro/settings/extension-registry-macos How do I set up a custom extension registry on macOS in Kiro? https://latestn.com/tool/kiro/settings/extension-registry-windows How do I set up a custom extension registry on Windows in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:44:27Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/settings/file-write-configuration/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/settings/file-write-configuration POST: https://latestn.com/dispute/tool/kiro/settings/file-write-configuration with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/settings/file-write-configuration?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure the file write tool in Kiro, including custom diff tools? Revision 1, last verified 2026-11-20T13:31:51Z. https://latestn.com/tool/kiro/settings/file-write-configuration (accessed 2026-11-21T09:59:14Z). @misc{LatestN_tool_kiro_settings_file_write_configuration_r1, title = {How do I configure the file write tool in Kiro, including custom diff tools?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/settings/file-write-configuration}}, note = {Revision 1; digest sha256:e245e44bb82d9ffd; last verified 2026-11-20T13:31:51Z; accessed 2026-11-21T09:59:14Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/settings/file-write-configuration