Create diff visualization/chooser

[W3ND31]

Actually we don't have a way to choose which chunk of AI generated code will be accepted or not. This issue is to track this problem.

[W3ND31]

@joaopluigi @ericdallo

[ericdallo]

Currently ECA doesn't support that and I'm not sure the best way to handle that yet, I started a branch in eca to intercept the LLM message and check if it's a code block and provide a CodeContent or something, but we still won't have the file path

[ericdallo]

editor-code-assistant/eca#33

[tomgeorge]

codecompanion.nvim integrates with diffview.nvim, which I think would be a great way to do it, or fall back to the default vim diff handling.

Pending ECA implementation of course.

[ericdallo]

As a frontend solution sounds really good @tomgeorge, I will think how to solve this on eca server, I paused that as not a priority after tool call implementations (which change code too), but I can see how convenient it is

[W3ND31]

I was planning to use akinsho/git-conflict plugin but those are pretty good inspiration too, @tomgeorge

[tomgeorge]

I think it comes down to preference. Something like git-conflict or the default vim diff handler are very lightweight, diffview is very heavyweight, it opens the UI in a new tab, etc.

[tomgeorge]

@ericdallo I'm trying to look in the codecompanion and avante source to see how they do it. Of course the trick is making it a generalized solution across all of the LLMs, not an easy task! I totally understand deprioritizing that for tool call implementations.

[ericdallo]

@tomgeorge that research would help a ton, handling different LLM responses is not that hard as we have llm_api.clj kinda of adapting that, but yeah, the hardest part is know how to support that

[tomgeorge]

It looks like avante and codecompanion each create their own bespoke llm tools to edit files. See here and here

They parse the messages from the LLM and then make another LLM request (sometimes with a weaker model) asking for the edit to be formatted in a specific way. This new message is then handed off to the plugins so you can see the diff and approve the change:

local PROMPT = [[<editFileInstructions>
Before editing a file, ensure you have its content via the provided context or read_file tool.
Use the insert_edit_into_file tool to modify files.
NEVER show the code edits to the user - only call the tool. The system will apply and display the edits.
For each file, give a short description of what needs to be edited, then use the insert_edit_into_file tools. You can use the tool multiple times in a response, and you can keep writing text after using a tool.
The insert_edit_into_file tool is very smart and can understand how to apply your edits to the user's files, you just need to follow the patch format instructions carefully and to the letter.

## Patch Format
]] .. patch.prompt .. [[
The system uses fuzzy matching and confidence scoring so focus on providing enough context to uniquely identify the location.
</editFileInstructions>]]

[ericdallo]

This now is supported by eca and eca-emacs, I should add to eca-vscode soon, please let me know if issues to implement in eca-nvim.