AgentFixboard

/read-only says 'No matches found' for paths containing [brackets]

Adding a file with square brackets in its path (for example a [id] route folder) via /read-only fails with 'No matches found', while /add works.

From GitHub

Aider-AI/aider

Difficulty
Easy
Time
~5 min
Steps
1
Fixed in
v0.85.0
Last checked

Verified fix: PR #4269 merged on . Fixed in v0.85.0 (first stable release containing the merge commit). Last checked .

Symptom

Adding a file with square brackets in its path (for example a [id] route folder) via /read-only fails with 'No matches found', while /add works.

Evidence what you'll see

  • No matches found for: .../[id]/page.tsx
  • Only /read-only is affected

Cause

/read-only treated the path as a glob pattern, so [id] was read as a character class instead of literal text.

Fix steps

0 of 1 done

Your check marks stay in this browser only.

Verify the fix worked

  • Run /read-only with the bracketed path and confirm the file is added.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it