Per the conversation in this slack thread in #eca - it would be nice if users could extend eca's tool call rendering to allow for richer introspection.
The proposal is to pass a defcustom function that receives the tool name, the args, result, etc and is then able to render itself. Ideally eca-emacs will implement its currently custom edit_file, etc. interactions using the same dispatch mechanism. Anything that isn't caught explicitly falls back to a somewhat generic tool call rendering (like we already have).
It might be worth considering using a lookup map that is from tool-name to render function, then users could register their functions in there and we would fallback. This could be simpler machinery than having to manage the dispatch / fallback inside a custom function itself.
Per the conversation in this slack thread in #eca - it would be nice if users could extend eca's tool call rendering to allow for richer introspection.
The proposal is to pass a
defcustomfunction that receives the tool name, the args, result, etc and is then able to render itself. Ideally eca-emacs will implement its currently customedit_file, etc. interactions using the same dispatch mechanism. Anything that isn't caught explicitly falls back to a somewhat generic tool call rendering (like we already have).It might be worth considering using a lookup map that is from tool-name to render function, then users could register their functions in there and we would fallback. This could be simpler machinery than having to manage the dispatch / fallback inside a custom function itself.