[Bug] Error when using search tool in workspaces with 20 or more projects open

[mxalis]

Environment

• OS: Windows 11
• Eclipse Version: 2026-03
• Plugin Version: 0.16

Describe the bug
When Copilot is trying to search using the built in ripgrep tool in a larger-than-micro sized workspace (>= 20 projects, eg Maven or Gradle submodules) the tool fails with error messages related to task queue size exceeded:

[Error] [ripgrepProcessManager] Task queue limit reached: 20

To Reproduce
Steps to reproduce the behavior:

1. Open a workspace with at least 20 projects open
2. Assign a task to Copilot in Agent mode (task should require Copilot to search files)
3. Search files task fails and Copilot failovers to using findstr in command line, requiring user approval continuously.

This pretty much forces you to constantly babysit Copilot and click Approve on the approval requests for using findstr

Expected behavior
Built in search tool should work even in workspaces with >= 20 projects

I understand the 20 queue limit is hard coded somewhere and it may be difficult to have it being adjustable. But it would be very much appreciated if at least the hard coded limit could be raised to something like 100 or 200.

[iloveeclipse]

I've also encountered few times that agents started to search my entire workstation content (started searchat /), which makes no sense (and of course failed later while looking on all NFS mounts) if the only files needed were located inside the specific project.

I wonder if the plugin can use a wrapper around "built in" Eclipse text search engine API and told agents to use that wrapper instead of external grep? See org.eclipse.search.core.text.TextSearchEngine & friends. It would not be only faster but more accurate.

[jdneo]

@iloveeclipse

If I use

copilot-for-eclipse/com.microsoft.copilot.eclipse.core/src/com/microsoft/copilot/eclipse/core/utils/WorkspaceUtils.java

Line 26 in f94e037

public static List<IProject> listTopLevelProjects() {

to find 'workspacefolders' instead of one IProject, one workspace folder, will it breaks your case?

Or in other words, in your workspace setup, does each sub-module also contains its own .md?

[iloveeclipse]

Or in other words, in your workspace setup, does each sub-module also contains its own .md?

I believe the question belongs to another ticket? #62

In any case: we don't use nested projects, but all projects are inside one single and huge git repository.