# Cmd+k Codebase indexing is broken

**URL:** <https://forum.cursor.com/t/cmd-k-codebase-indexing-is-broken/66343>\
**Category:** Bug Reports\
**Created:** [March 18, 2025, 6:42pm UTC](https://forum.cursor.com/t/cmd-k-codebase-indexing-is-broken/66343 "2025-03-18T18:42:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![itsleonwu](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/itsleonwu/32/7906_2.png) [@itsleonwu](https://forum.cursor.com/u/itsleonwu)\
**Post date:** [March 18, 2025, 6:42pm UTC](https://forum.cursor.com/t/cmd-k-codebase-indexing-is-broken/66343/1 "2025-03-18T18:42:43Z")

</div>

Unclear how exactly to reproduce this reliably, but cmd+k fails to find files that it consistently used to. cmd+L sidebar still works for this file. Possibly related to latest version update, which I noticed because my color theme changed. This is a near-showstopper for the cmd+k feature for me, which I use consistently for small edits when I don’t want the AI to go regenerating huge parts of code from scratch.

Happy to pull up other debug information if needed.

Cursor version:  
Version: 0.47.5  
VSCode Version: 1.96.2  
Commit: 53d6da1322f934a1058e7569ee0847b24879d180  
Date: 2025-03-14T21:41:01.221Z  
Electron: 32.2.6  
Chromium: 128.0.6613.186  
Node.js: 20.18.1  
V8: 12.8.374.38-electron.0  
OS: Darwin arm64 24.2.0

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 17, 2025, 6:42pm UTC](https://forum.cursor.com/t/cmd-k-codebase-indexing-is-broken/66343/2 "2025-04-17T18:42:56Z")

</div>

Closed on April 17, 2025, 6:42pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.