Thanks for the correction — removing the quotes fixed it. We tested all three syntax variants:
- `globs: **/database/**` (no quotes) — **works**
- `globs: “**/database/**”` (quoted string) — does not work
- `globs:` with `- “**/database/**”` (YAML list) — does not work
We also confirmed that having a matching file open in an editor tab without the agent reading it does **not** trigger the rule, which matches what you described.
One issue we did find: glob rules created mid-conversation don’t take effect until you open a new chat. We created the test rule, had the agent read a matching file in the same chat, and the rule never injected. Opening a fresh chat and having the agent read the same file worked immediately. This could be confusing if someone creates a new glob rule and expects it to apply right away — it silently doesn’t until the next chat.
The syntax sensitivity is worth calling out in the docs. The YAML list format (`- “pattern”`) and quoted strings (`“pattern”`) are both natural things to write and both silently fail. A validation warning when a glob pattern contains quotes or brackets would save people a lot of debugging.
Thanks for the quick responses.