continuedev / continuedev/continue

Repo-map tool slow with large project

Open
#4,504 0 comments 0 reactions 1 assignee View on GitHub

@Patrick-Erichsen is already working on this.

Since Mar 6, 2025.

area:indexing kind:bug needs-triage os:mac
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.