当文件目录太深，>= 6 层的时候使用 @ 或者 control + p 无法检索到文件

[simuusang]

Description

Steps to reproduce

Expected behavior

Actual behavior

Impact

Environment

• OS:
• codewhale version:
• Install method:
• codewhale doctor summary:
• Model/provider:
• Terminal app:
• Shell:

Logs, screenshots, or recordings

[Hmbown]

Thanks @simuusang. This is useful timing-wise because v0.8.49 added configurable mention walk depth after v0.8.48: in ~/.codewhale/config.toml, [tui] mention_walk_depth = 0 disables the depth cap, or you can set a larger number than the default 6.

I am leaving this open rather than closing it as “configuration exists,” because the product question is whether deep-file projects need a better default or clearer UI hint. If you can retest on v0.8.49 with mention_walk_depth = 0, that would tell us whether the remaining issue is only the default limit or also the search/ranking path.

[Hmbown]

A UX slice for this is now in the v0.8.50 harvest branch #2504.

The branch harvested @cyq1017's #2530 as a97675824 / 29f57665e. Deep path-like @ completion misses now show a targeted mention_walk_depth hint instead of the generic no-match status, so users can discover /config set mention_walk_depth 0 --save when they need unlimited depth. The actual autocomplete search behavior and default depth are unchanged.

Verified locally with:

• cargo test -p codewhale-tui --all-features --locked try_autocomplete_file_mention_no_match -- --nocapture
• cargo clippy -p codewhale-tui --all-targets --all-features --locked -- -D warnings
• ./scripts/release/check-versions.sh

Live #2504 CI is green across Ubuntu, macOS, Windows, lint, version drift, CodeQL, mobile smoke, npm smoke, and GitGuardian.

Leaving this issue open because the branch adds discoverability for the depth cap, not a broader change to default search depth or indexing behavior. Thanks @simuusang for the clear report.

[simuusang]

我更新到了0.8.50尝试搜索了一下还是不行，在我的项目里面有个叫 room_chat_shell.dart 的文件，通过搜索没办法直接搜到。

同时我也修改了 mention_walk_depth 参数 这是我在vscode中的搜索截图

该功能的用户体验部分已经包含在 v0.8.50 版本的开发分支中，路径为 #2504 。

该分支实现了对' #2530 '的补全，补全结果分别为 a97675824 和 29f57665e 。类似深层路径的 @ 补全现在会显示目标值 mention_walk_depth 的提示信息，而不是常见的“无匹配结果”状态。这样，用户在需要无限深度时就能找到目标值 /config set mention_walk_depth 0 --save 。不过，实际的自动补全行为以及默认深度设置仍然保持不变。

已在当地进行验证：

• cargo test -p codewhale-tui --all-features --locked try_autocomplete_file_mention_no_match -- --nocapture
• cargo clippy -p codewhale-tui --all-targets --all-features --locked -- -D warnings
• ./scripts/release/check-versions.sh

在 Ubuntu、macOS、Windows 平台上，使用 CI 进行持续集成时，Live #2504 CI 的结果都是绿色的。同时，在 Lint、版本漂移、CodeQL、移动端测试、npm 测试以及 GitGuardian 方面也表现良好。

这个问题暂时保留不变，因为该分支只是增加了对深度限制的可发现性，并没有对默认的搜索深度或索引行为做出任何重大改变。感谢您的详细报告。

[Hmbown]

Fixed on the v0.8.51 branch (claude/busy-mayer-b66rA, commit 478bae4).

Root cause: both the @-mention index and the Ctrl+P picker walked with ignore's max_depth(Some(6)). A file inside a 6-level-deep directory sits at component depth 7, so it was excluded — exactly the "≥ 6 层" cutoff you hit.

Fix:

• Default walk depth raised 6 → 10 (mention_walk_depth / DEFAULT_COMPLETIONS_WALK_DEPTH), which covers conventionally nested Java/.NET/web trees.
• The Ctrl+P picker now honors the configurable mention_walk_depth too (it previously ignored it), including 0 = unlimited — matching @-mention behavior and the existing "set mention_walk_depth 0 to search deeper" guidance.

The walk stays bounded by .gitignore and the candidate cap. Added a regression test covering depth-6 miss / default reach / unlimited. For very deep trees you can still set mention_walk_depth = 0.

---

Generated by Claude Code