#Warp no longer offers to index git repos

4 messages · Page 1 of 1 (latest)

bitter quartz
#

Warp used to offer to index the codebase of a git repo that I cd into. It does not appear to be doing that anymore. Has this behavior been eliminated? Is it no longer best practice to have a WARP.md file in your repository root?

wild quiverBOT
#

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

#

Warp still supports indexing the codebase of a Git repository when you cd into it, provided that Codebase Context is enabled. According to the latest documentation, when you open a directory in Warp and it is part of a Git repository, Warp will begin indexing the source code to provide context for agents. This process is triggered initially, periodically, when you start a new agent conversation, or when you manually sync via the Settings > Code menu. You can also manage whether new folders are indexed automatically as you navigate them in the settings. If this is not happening, it may be due to a configuration issue or a recent bug, but the intended behavior is for indexing to occur automatically for Git repos Getting Started With Coding in WarpIndexing your codebase.

As for the WARP.md file, it is still considered best practice to have it in your repository root. Warp uses WARP.md to define project rules and context for agents, and it is automatically generated during the initialization flow when you start a new project or run the /init slash command in an existing repo Projects: WARP.md, slash commands, and agent profilesGetting Started With Coding in Warp.

#

If you are not seeing the indexing prompt or behavior, ensure that you are using the latest version of Warp and that codebase context is enabled in your settings. If the issue persists, it may be worth checking for open bugs or submitting a report.

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