Before opening, please confirm:
Operating System
Tahoe 26.5(25F71)
Kiro Version
0.12.263
Bug Description
Description:
Global steering files placed in ~/.kiro/steering/ are not being loaded into the agent's context, despite the docs and changelog (v0.5) confirming this is a supported feature.
Environment:
- Kiro IDE version: 0.12.263
- OS: macOS arm64 (Darwin 25.5.0)
- VSCode version: 1.107.1
Steps to Reproduce
- Create ~/.kiro/steering/my-global-context.md with the following front-matter and some content:
---
inclusion: always
---
# My Global Context
Some rules and guidelines here...
- Open a workspace that has NO .kiro/steering/ directory
- Start a new chat and ask a question that the steering file covers
- Agent searches the workspace instead of using the global steering content
Expected Behavior
Expected behavior: The agent should receive the content of ~/.kiro/steering/my-global-context.md as global context (shown with [Global] tag), as documented at https://kiro.dev/docs/steering/#global-steering
Actual behavior:
- The agent does NOT receive global steering content
- Agent says "no steering files found" and searches the workspace
- The file IS recognized by the UI — using "Generate a custom steering document" → "Global agent steering" with the same name prompts "file already exists, overwrite?"
- The Agent Steering sidebar section remains empty
Workaround: Adding the folder containing the steering file as a workspace folder causes it to load as workspace-level steering.
Conversation ID
No response
Additional Context
Before opening, please confirm:
Operating System
Tahoe 26.5(25F71)
Kiro Version
0.12.263
Bug Description
Description:
Global steering files placed in
~/.kiro/steering/are not being loaded into the agent's context, despite the docs and changelog (v0.5) confirming this is a supported feature.Environment:
Steps to Reproduce
Expected Behavior
Expected behavior: The agent should receive the content of
~/.kiro/steering/my-global-context.mdas global context (shown with [Global] tag), as documented at https://kiro.dev/docs/steering/#global-steeringActual behavior:
Workaround: Adding the folder containing the steering file as a workspace folder causes it to load as workspace-level steering.
Conversation ID
No response
Additional Context