When the agent uses list-files, it may not be able to retrieve the complete project structure

[qdaxb]

App Version

3.21.5

API Provider

DeepSeek

Model Used

DeepSeek-V3

🔁 Steps to Reproduce

1. Create a working directory containing two first-level folders: a and b. Folder a should contain 200 files, and folder b should contain other files.
2. use prompt:"Analyze this project.“

💥 Outcome Summary

There is a certain chance that the model will completely ignore b.

📄 Relevant Logs or Errors (Optional)

[dosubot]

This happens because the list-files tool has a default cap of about 200 files per listing to prevent performance issues. If one folder (like a) contains 200 files, the tool may hit the cap before it ever lists the next folder (like b), so b can be completely omitted from the results. This is a documented limitation of the tool and is not specific to DeepSeek or the DeepSeek-V3 model—it's how Roo Code's file listing works in general [docs].

To work around this, you can manually run list-files on each subdirectory (e.g., a and b) to ensure you get a complete listing. There are currently no documented configuration options to increase the file cap. If you regularly work with large projects, it's best to list subdirectories individually for full coverage [docs].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.