features: proposed behaviours and ideas

[aarnphm]

A evergreen list of features and requests:

features.

• [[ and ]] for jumping code block @aarnphm
• scrollview on code buffer based on chat window cursor @aarnphm How to use ct? <leader> aa works #23 (comment)
• token streaming refactor(ai): streaming chunks to avoid excessive redraw. #73
• asking for users input env if not set feat(ui): add envvar popup with warnings #54
• add support for different behaviour feat(experimental): add section for behaviour #55
• support custom vendor feat(providers): add support for custom vendors #74
• Workspace context [feat] Keep chat history(context) in the same LSP workspace #76
• Tool use
• Prompt refactoring using aider's search queries @yetone

ui.

• change chat window bottom padding for vim.o.laststatus=3'

bugs.

• nui not allowed to change text or change window #32 (fixes with fix(ui): set selection per buffer and remove spinner (closes #32) #62)
• handle stream on closed buffer accordingly refactor(ai): streaming chunks to avoid excessive redraw. #73
  • UI: fix(ui): invalid buf id on hide the sidebar during generation #61
  • refactor stream to plenary.Job, and update view renderer lifecycle accordingly.

qol.

• qol: fail early and handle error #121

cc @yetone for more suggestions and added to this tracking list

[yuchanns]

Currently, we need to manually select a block using v to interact with. Can we auto-select a block based on the tree-sitter context?

[yetone]

@yuchanns I use my configuration to leverage treesitter and quickly select a node with the simple . key.

https:/yetone/cosmos-nvim/blob/b05a44687cd08a3664c084249ce7128df2ea1a6d/lua/layers/editor/configs.lua#L319

[aarnphm]

Currently, we need to manually select a block using v to interact with. Can we auto-select a block based on the tree-sitter context?

I think this should be user config. I would prefer it not to be too invasive.

[yuchanns]

That's great!

[wongsingfo]

Currently, we need to manually select a block using v to interact with. Can we auto-select a block based on the tree-sitter context?

We can use the incremental_selection feature provided by nvim-treesitter to quickly select a block.

[trashhalo]

New AI editor features dropping in zed. Sharing 🧵 for inspiration

https://x.com/zeddotdev/status/1825967812629631034?s=61

[raiku-dev]

@yetone Hey, Supermaven has this feature in VS Code that lets you attach any open files to the chat message.
I'd like to have the possibility to attach files from open buffers to give the AI more context of the setup I'm working on in K8s e.g.

[olliezhu]

would it be possible to add support for Nvchad? my understanding is that lazy.vim is currently recommended.

[raiku-dev]

would it be possible to add support for Nvchad? my understanding is that lazy.vim is currently recommended.

The plugin manager is meant by that but avante is compatible with any of the big plugin managers and NVChad has a place where you can add custom plugins. Check the avante readme and the NVChad docs on how to add plugins.

[aarnphm]

any plugins manager listed on readme is supported.

[olliezhu]

Check the avante readme and the NVChad docs on how to add plugins.

will do, thanks!

[zeroaddresss]

Vertex AI allows to use a set of LLMs (including Claude Sonnet), was wondering if it's possible to integrate Vertex within avante

[evanrichards]

Hey, Supermaven has this feature in VS Code that lets you attach any open files to the chat message.
I'd like to have the possibility to attach files from open buffers to give the AI more context of the setup I'm working on in K8s e.g.

cursor seems to support this with @'ing a file in the prompt.

[aarnphm]

Hey, Supermaven has this feature in VS Code that lets you attach any open files to the chat message.
I'd like to have the possibility to attach files from open buffers to give the AI more context of the setup I'm working on in K8s e.g.

cursor seems to support this with @'ing a file in the prompt.

you can drag and drop or pasting image at the prompt atm. Feel free to add additional support for writing path to a file

[V4G4X]

Hi, I see that "workspace context" is 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 (all 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?

[aarnphm]

Hi, I see that "workspace context" is in the roadmap.

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

Check the issue for this.

[GopherJ]

I'd suggest to have more lsp features, avante can have an embeded lsp server to assist on diagnostics etc, generate new code actions based on diagnostics