Repo-map tool slow with large project #4504
Labels
area:indexing
Relates to embedding and indexing
kind:bug
Indicates an unexpected problem or unintended behavior
"needs-triage"
Before submitting your bug report
Relevant environment info
Description
When you ask chat to find a specific subdirectory and it defaults to the repomap tool and the project is large (e.g. continue codebase) the tool appears to hang with the status of generating. When debugging, I’m noting the repomap is generating from scratch and is very slow.
I’d be interested if we could move the repo-map generation to the background like embedding generation to help maintain a repo-map off the chat interaction.
Curious in how we might also only allow the tool be available when the repo-map is created to avoid poor user experience.
To reproduce
Have a large project like the continue code base.
In chat ask “Run the tests in the core directory using commands in package.json in that directory.”
Observe the repomap tool get called.
It appears to hang.
Note the chat entry box is also active making for a confusing end user experience.
Log output
The text was updated successfully, but these errors were encountered: