Answer: You use terminal context in Kiro chat by typing #terminal to reference recent output from your active terminal. #terminal always refers to the currently active/visible terminal window, so make sure the terminal you want to reference is active before using it. Status: Confirmed Entry: tool/kiro/features/use-terminal-context Revision: 2 Digest: sha256:1bf9676b5c5746f6 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:38Z Last changed: 2026-11-20T13:29:22Z (Example usage: — → #terminal analyze the error from the last npm run build) Last verified: 2026-11-20T13:29:22Z Next check: 2026-11-21T13:29:22Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Command | #terminal | [1] | 2026-11-20 Active terminal requirement | #terminal always refers to the currently active/visible terminal window | [1] | 2026-11-20 Example usage | #terminal analyze the error from the last npm run build | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Terminal - Chat - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/chat/terminal/ Role: primary. Accessed: 2026-11-20T13:29:22Z Quote: "Reference recent output from your active terminal in your conversations with #terminal ." (Supports: Command) Quote: "#terminal always refers to the currently active/visible terminal window." (Supports: Active terminal requirement) Quote: "#terminal analyze the error from the last npm run build" (Supports: Example usage) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: a048abbdddcd47b965b35ccd50abaee5fad4bf9ec341b3d116a61b4c7565aed1 (captured 2026-11-20T13:29:19Z) 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:29:22Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:22Z Last attempt: 2026-11-20T13:29:22Z Notes and limitations: Extracted automatically from a single official source (section "Using terminal context"). Related: https://latestn.com/tool/kiro/features/verify-refactor-results How do I verify the results of a refactor in Kiro? https://latestn.com/tool/kiro/features/vibe-refactoring-workflow How do I refactor code with Kiro's vibe refactoring workflow? https://latestn.com/tool/kiro/features/web-fetch-limitations What are the limitations of Kiro's web_fetch tool? https://latestn.com/tool/kiro/features/upload-existing-designs How do I upload an existing design when creating a Kiro feature spec? https://latestn.com/tool/kiro/features/use-checkpoints-and-rewind How do I use checkpoints and rewind in Kiro? https://latestn.com/tool/kiro/features/use-specs-for-complex-work How do I use specifications in Kiro for complex work? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:29:22Z | changed | Example usage: — → #terminal analyze the error from the last npm run build | [1] 2026-11-20T13:29:22Z | changed | Active terminal requirement: — → #terminal always refers to the currently active/visible terminal window | [1] 2026-11-20T13:29:22Z | changed | Command: — → #terminal | [1] 2026-11-20T13:29:22Z | changed | example usage: #terminal analyze the error from the last npm run build → — | [1] 2026-11-20T13:29:22Z | changed | active terminal requirement: #terminal always refers to the currently active/visible terminal window → — | [1] 2026-11-20T13:29:22Z | changed | syntax: #terminal → — | [1] 2026-11-13T03:42:38Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/use-terminal-context/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/features/use-terminal-context POST: https://latestn.com/dispute/tool/kiro/features/use-terminal-context with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/use-terminal-context?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use terminal context in Kiro chat? Revision 2, last verified 2026-11-20T13:29:22Z. https://latestn.com/tool/kiro/features/use-terminal-context (accessed 2026-11-21T10:00:53Z). @misc{LatestN_tool_kiro_features_use_terminal_context_r2, title = {How do I use terminal context in Kiro chat?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/use-terminal-context}}, note = {Revision 2; digest sha256:1bf9676b5c5746f6; last verified 2026-11-20T13:29:22Z; accessed 2026-11-21T10:00:53Z} } 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/features/use-terminal-context