Live data from Hacker News

Our decision on Cursor following its acquisition by SpaceX

openai.com

511–514 of 514 posts

Re: Our decision on Cursor following its acquisition by SpaceX

#511

Earlier quoted context omitted.

There will be a moment where the government will depend so much on the tech that if the tech cuts the supply, they are f... Who do you think will rule at that point? They just cannot fight that, they do not have the technology these companies have.

In that situation, it depends how much physical force the government has to compel the tech leader, and how much physical force the tech leader has to counter it. Usually, the number of bodies who will comply is the proxy for power, but with automation, it could be different in the near future. https://xkcd.com/538/

But it can clearly be seen that the power will not be as monopolistic as before indeed. The rebalance leans towards losing power for states vs tech in part.

Regulation alone cannot control if it cannot be made effective.

Re: Our decision on Cursor following its acquisition by SpaceX

#512

Earlier quoted context omitted.

I've never seen a product blow another product out of the water so hard as Claude Code did to Cursor.

The TUI version of Claude Code just isn't very good, though. The default keybindings do not work in the majority of terminals (because they generate the same byte sequences for key sequences assigned to different commands). Editing large prompts is rather painful because there doesn't seem to be in-prompt search commands. There is no source code browser, so source code references cannot checked by the users without a…

The Claude Code TUI is downright awful, and hostile.

Re: Our decision on Cursor following its acquisition by SpaceX

#514

Is there some kind of alternative to Cursor in these terms - fast because the code is already indexed no need to start every prompt rediscovering the world with rg - in editor/vscode review much better than relying on git diff at the very end. You can click on next button to jump there. Quick edit in place. Or a quick prompt (seconds) to fix something small - in editor completion / quick edits, when you do things by…

Cursor no longer indexes your codebase.

Do you know when they stopped and why?

EDIT - AI says:

Cursor seems to have intentionally dropped semantic/embedding-based codebase indexing. Their explanation is that newer coding agents are now good enough at searching repos directly. They can grep in parallel, inspect directories, read likely files, and refine the search themselves. Cursor says this now works as well or better for most cases. [1]

So the architecture shifted from something like “chunk → embed → vector DB → retrieve” to “local search index/ripgrep → agent explores.” There is still an index, but it’s a conventional local search index. No embeddings are involved in that retrieval path. [1]

The interesting part is that Cursor was still reporting a ~12.5% accuracy gain from semantic indexing in January 2026. [2] So this looks less like “semantic search never worked” and more like agentic search improving fast enough that the extra infrastructure stopped being worth it.

[1] https://forum.cursor.com/t/what-do-you-think-about-cursor-re...

[2] https://cursor.com/blog/secure-codebase-indexing

Post reply on HN