search

yetone / avante.nvim

Use your Neovim like using Cursor AI IDE!
Apache License 2.0
6.2k stars 223 forks source link

[feat] Keep chat history(context) in the same LSP workspace #76

Open atlas-comstock opened 2 months ago

atlas-comstock commented 2 months ago

By doing this, switch to different file in same workspace, we can easily bring all the context

aarnphm commented 2 months ago

ye context is something we intend to do, but probably a bit lower on the list atm

zeroaddresss commented 1 month ago

So the plugin does not have context awareness atm? The scope is limited to current buffer?

yetone commented 1 month ago

Currently, it can only use the current file or selected code block as context. Having the entire project as context is on my to-do list.

https://github.com/yetone/avante.nvim#todos

arkuhn commented 1 month ago

Currently, it can only use the current file or selected code block as context. Having the entire project as context is on my to-do list.

https://github.com/yetone/avante.nvim#todos

I wonder if there is middle ground that lets you send other individual files along with your prompt, separate of a full workspace context?

aarnphm commented 1 month ago

I think for this case we would probably want to send embeddings instead of just raw text.

jadengis commented 1 month ago

I'd love to get something like this. Right now the generated text is really generic in some cases, making it not particularly useful for the structure of my application.

V4G4X commented 1 month ago

Hi, I saw this in the roadmap.

Does that mean if I open nvim with nvim /path/to/codebase:

  1. Avante will have indexed my entire codebase and pass that as context in the API request?
  2. Or will it pass my Neovim workspace (just the open buffers) in the API request?

If it's the first, that's impressive, but can we get 2nd first? Or somehow be able to pick which files' context we want to give?