#Code base too large

4 messages · Page 1 of 1 (latest)

ashen galleon
#

5000 files but doesn't actually say how many files so I have no idea what plan to upgrade to, is there any way to find out?

radiant mauveBOT
#

Hi @ashen galleon. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I understand your frustration with the "codebase too large" message. You're right that Warp doesn't currently display the exact file count, which makes it difficult to know which plan you need.

Finding Your File Count

To determine how many files Warp is trying to index, you can run this command in your terminal:

git ls-files | wc -l

This will show you the number of Git-tracked files in your repository, which is what Warp uses for indexing.

Plan Limits

According to the pricing page, here are the file limits per codebase for each plan:

  • Free: 5,000 files per codebase
  • Pro: 10,000 files per codebase
  • Turbo: 20,000 files per codebase
  • Lightspeed: 100,000 files per codebase

Reducing File Count

Before upgrading, you might be able to reduce the file count using ignore files. Warp respects several ignore patterns including .gitignore and .warpindexingignore. According to the Codebase Context documentation, files excluded by these ignore rules do not count toward your file limit.

Common directories to exclude include:

  • node_modules/
  • venv/ or virtual environments
  • Build artifacts (/bin, /obj)
  • .git/ (already excluded by default)

Create a .warpindexingignore file in your repository root with the directories you want to exclude, then click the sync 🔄 button in Settings > Code to re-index.

This approach has helped many users bring their file count under their plan's limit without needing to upgrade.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@ashen galleon Kapa.ai is still learning and improving, please let me know how I did by reacting below.