Roo indexes .next folder despite .rooignore file

[enerage]

App Version

3.20.1

API Provider

OpenAI

Model Used

Text Embedding 3 Small

🔁 Steps to Reproduce

1. Open Roo one level above nextjs project
2. Example: folder called "Root Folder" and inside we have/create "example-nextjs" project
3. In "Root Folder" we can create .rooignore with the following line "example-nextjs/.next/" (even though, as per my understanding this should not even be necessary if the 'example-nextjs' project has .gitignore, which I also have)
4. During development, or build/eventually .next is being indexed
5. This can be seen on codesearch, photos attached

This happened with and without .rooignore file. When I created the .rooignore file I even recreated the docker qdrant instance yet eventually .next folder was picked up again

💥 Outcome Summary

Expected .next folder to be ignored and not indexed, I also think this is eating up a lot of tokens, however .next is being indexed, codebase search doesn't work well as it returns many results from the .next folder

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @enerage! I'm Dosu and I’m helping the Roo-Code team.

Roo Code should respect both .rooignore and .gitignore patterns when indexing files, and the syntax for .rooignore is identical to .gitignore. If your .rooignore contains recruitica-nextjs/.next/ and it's in the correct relative path from where Roo is running, .next should be excluded from indexing and search results. If you're still seeing .next files, double-check that the path in .rooignore matches the actual folder structure and that there are no typos or extra spaces. Also, make sure Roo is running from the correct root directory—relative paths in .rooignore are resolved from where Roo starts up.

One thing to note: if you or a tool directly mention or reference files in .next (for example, via @mentions or explicit file paths), Roo will bypass .rooignore and fetch that content anyway, which could explain why some .next files appear in search or context even if they're ignored for general indexing. This is intentional behavior for context fetching and not a bug in the ignore logic itself. For more details, see the docs on .rooignore and indexing behavior.

If everything looks correct and .next is still indexed, there may be an edge case with path resolution or a bug. In that case, try placing a .rooignore file directly inside the example-nextjs folder with just .next/ as the pattern, and see if that resolves it. Let me know if you still see .next files indexed after that.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[daniel-lxs]

Hey @enerage, thank you for creating this issue!

I'll take a look at this and try to scope the issue and potentially come up with a solution.

[GabsFranke]

Might be more complex, but would be cool if it'd support .gitmodules, with each having its own gitignore to read, the gitmodules file looks like this:

[submodule "frontend"]
	path = frontend
	url = https://github.com/x/frontend.git
[submodule "backend"]
	path = backend
	url = https://github.com/x/backend.git

Under path there's a gitignore: /frontend/.gitignore

Anyways, i can always maintain the main gitignore if that works. Thanks