DevHub · Troubleshooting
DevHub stops responding while an agent searches a large repository
Symptom
An agent sends many files_search calls in one turn against a large repository. DevHub does not repaint or answer clicks until they finish. In the report, eight calls each took about a minute and a few seconds and finished together.
Cause
Text search reads files one after another inside the main process of DevHub, which also serves MCP and every window. Calls arrive together and wait behind each other, and the application has nothing free to repaint. A rare string reads every file in the repository, because the maximum number of results limits what is returned, not the work.
Solution
There is no fix to install. Until there is:
- Ask the agent to run one
files_searchat a time on a large repository. Other tools can be batched. - Prefer
repo_symbol_searchwhere the language is indexed. It answers from the Repository Index, not from the disk. - Wait. DevHub responds again when the searches finish.
Applies from
Since 0.8.1