[BUG] The `@` file picker in Claude Code TUI does not respect `.claudeignore` patterns. Files from `.next/` directories appear in the fuzzy search results even when explicitly ignored.
Resolved 💬 3 comments Opened Jan 30, 2026 by smerrill2 Closed Feb 3, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The @ file picker in Claude Code TUI does not respect .claudeignore patterns. Files from .next/ directories appear in the fuzzy search results even when explicitly ignored.
Expected Behavior
Files inside .next/ should not appear in the @ file picker results.
Actual Behavior
.next/ files appear in the fuzzy search results:
./.next/types/app/(landing)/page.ts./.next/types/app/(landing)/layout.ts./.next/server/app/(landing)/page/react-loadable-manifest.json./.next/server/app/(landing)/page/build-manifest.json- etc.
Environment
- Claude Code version: v2.1.25
- OS: macOS (Darwin 25.3.0)
- Terminal: Ghostty
Notes
- The
.next/directory is also in.gitignore respectGitignoreshould betrueby default- The
.claudeignorefile is correctly placed in the working directory whereclaudeis invoked
EOF
)"
What Should Happen?
The fuzzy search when doing '@/ file name' is broken. the .next files structures absorb all the list of the fuzzy search.
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce
- Create a Next.js project with a
.nextbuild directory - Create a
.claudeignorefile in the project root with:
````
.next
.next/**
- Run
claudefrom the project directory - Type
@followed by a search term that would match files in.next/(e.g.,@landing)
Claude Model
Other
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.25
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗