continuedev / continuedev/continue
Repo-map tool slow with large project
@Patrick-Erichsen is already working on this.
Since Mar 6, 2025.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I believe this is a bug. I'll try to join the Continue Discord for questions
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: MacOS
- Continue version: 1.1.1
- IDE version: latest
- Model:
- config:
OR link to assistant in Continue hub:
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.