-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AI Assistant should have embedding context of the entire codebase #15924
Comments
I still hop between Cursor and Zed for this very reason. The full codebase indexing capabilities of Cursor are invaluable in a large codebase where one person can't understand / know where things are at. It makes my entire team way more independent than they would otherwise be. |
I've reached the point with Zed and ollama that I now need the editor to have more context about what I'm talking about. Please take a look at integrating swiftide. It's specifically designed for this task. It would be huge if all rustdocs, posix man pages, code from dependent crates, and previous code revisions from the git history were searchable in a vector db for providing query context. |
Same here ! It is the missing feature for me |
I believe this is the most important but overlooked feature for Zed editor to become a effective meaningful AI-native editor. |
Exact same thing, always coming back to Cursor for that and their Composer feature, even when my heart wants me to make the full switch to Zed, Why is this so low in the Requested features ? it genuinely feels like the most important |
This is definitely necessary. A lot of newer models like Gemini 2 can handle a lot more than a full code base. Manually adding individual files is too cumbersome |
Check for existing issues
Describe the feature
For complex projects, expkicitly adding code context of relevant files becomes insufficient since changes and context gets too distributed and out of direct coverage and Assistant's suggestions have reduced marginal utility.
Continuously updated code context embeddings always available to chat assistant solves this problem.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: