GitHub search tool returns zero matching GitHub Issues despite there being many

[jruales]

Problem

The github-pull-request_doSearch language-model tool returns zero results when searching a repository that is not the active workspace repository, even when actually such results do exist.

Specific example:

• Repository parameter: microsoft/vscode
• Query: is:issue is:open assignee:jruales
• Actual result: totalIssues: 0
• Known matching issue: When opening FastAPI's docs in the integrated browser, it shows up blank vscode#332663 is open and currently assigned to jruales. The issue_fetch tool also returns that assignee correctly.

Equivalent queries such as is:issue assignee:jruales, assignee:jruales, and is:issue is:open involves:jruales also return zero.

The tool itself includes an Open on GitHub.com link. Opening that link shows the expected assigned issues, while the tool's structured result for the same query reports zero.

Expected

The explicit repo parameter should scope the search independently of whichever repository is open in the workspace. Alternatively, if the requested repository cannot be searched, the tool should return an explicit error explaining why rather than a successful-looking empty result.

Likely cause

SearchTool resolves or creates the requested repository, but then calls FolderRepositoryManager.getIssues(). Its paging path filters repositories against active workspace remotes, which may exclude the synthetic repository created for the explicit repo parameter. The tool then returns a successful-looking empty result.