Answer: File references currently support text files up to 250KB (larger files are truncated), directory trees up to 3 levels deep with 10 items per level, explicit file paths only (no glob patterns), full file contents (no line ranges), and relative and absolute paths (no tilde expansion). In cloud sessions, the @ picker and Tab completion search your local filesystem rather than the sandbox, and binary files are not supported. Status: Confirmed Entry: tool/kiro/troubleshooting/file-reference-limitations Revision: 1 Digest: sha256:6166c60599a2ceba (changes whenever the content changes) Timeline: Created: 2026-11-13T03:36:20Z Last changed: 2026-11-13T03:36:20Z Last verified: 2026-11-20T13:19:36Z Next check: 2026-11-21T13:19:36Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Max text file size | 250KB | KB | [1] | 2026-11-20 Directory tree depth | 3 levels deep | levels | [1] | 2026-11-20 Items per level | 10 items per level | items | [1] | 2026-11-20 Glob patterns | no glob patterns like @*.ts | | [1] | 2026-11-20 Line ranges | no line ranges like @file.ts:10-20 | | [1] | 2026-11-20 Tilde expansion | no tilde expansion like @~/file | | [1] | 2026-11-20 Cloud sessions search | search your local filesystem, not the sandbox the session runs in | | [1] | 2026-11-20 Binary files | Binary files (images, executables, archives) are not supported. | | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "File references - Chat - CLI - Docs - Kiro". https://kiro.dev/docs/cli/chat/file-references/ Role: primary. Accessed: 2026-11-20T13:19:36Z Quote: "Text files up to 250KB (larger files are truncated)" (Supports: Max text file size) Quote: "Directory trees up to 3 levels deep, 10 items per level" (Supports: Directory tree depth, Items per level) Quote: "Explicit file paths only (no glob patterns like @*.ts )" (Supports: Glob patterns) Quote: "Full file contents (no line ranges like @file.ts:10-20 )" (Supports: Line ranges) Quote: "Relative and absolute paths (no tilde expansion like @~/file )" (Supports: Tilde expansion) Quote: "In cloud sessions , the @ picker and Tab completion currently search your local filesystem, not the sandbox the session runs in." (Supports: Cloud sessions search) Quote: "Binary files (images, executables, archives) are not supported." (Supports: Binary files) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 818ac69066a7ae1c56feae52df263b84f4ab4bfc17f85e379266824bf4b9b89e (captured 2026-11-20T13:19:36Z) 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:19:36Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:19:36Z Last attempt: 2026-11-20T13:19:36Z Notes and limitations: Extracted automatically from a single official source (section "Current limitations"). Related: https://latestn.com/tool/kiro/troubleshooting/fix-auth-browser-redirect How do I fix browser redirect failures during Kiro authentication on Windows or macOS? https://latestn.com/tool/kiro/troubleshooting/fix-autocomplete-not-working What should I do if autocomplete is not working in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/fix-invalid-json-custom-agent How do I fix invalid JSON syntax errors in a Kiro custom agent configuration? https://latestn.com/tool/kiro/troubleshooting/diff-tool-troubleshooting What should I do if my custom diff tool isn't working in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/enterprise-unsupported-and-known-issues What capabilities are not supported or have known issues in Kiro Enterprise Management? https://latestn.com/tool/kiro/troubleshooting/experimental-feature-not-working Why is an experimental feature or command not working in Kiro CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:36:20Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/file-reference-limitations/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/troubleshooting/file-reference-limitations POST: https://latestn.com/dispute/tool/kiro/troubleshooting/file-reference-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/file-reference-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the current limitations of file references in Kiro CLI? Revision 1, last verified 2026-11-20T13:19:36Z. https://latestn.com/tool/kiro/troubleshooting/file-reference-limitations (accessed 2026-11-21T10:00:57Z). @misc{LatestN_tool_kiro_troubleshooting_file_reference_limitations_r1, title = {What are the current limitations of file references in Kiro CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/file-reference-limitations}}, note = {Revision 1; digest sha256:6166c60599a2ceba; last verified 2026-11-20T13:19:36Z; accessed 2026-11-21T10:00:57Z} } 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/troubleshooting/file-reference-limitations