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

[atlas-comstock]

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

[aarnphm]

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

[zeroaddresss]

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

[yetone]

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:/yetone/avante.nvim#todos

[arkuhn]

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:/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]

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

[jadengis]

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]

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?