You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Custom Chat participants (formerly agents) such as @workspace #311
Are there plans to let us create custom Chat Participants (plugins) in the same vein as @buffer and @Buffers? If so would it be feasible to enable them, via a similar mechanism as cmp, as a list of repositories?
I think in this plugin scope it would be custom conext function I think? Even though custom selector also already can be used for same thing. I personally think the nvim-cmp "extension" system is terrible so I would def not want to go that route. For custom selector you can pass custom selection already as function, and I think for context we could do the same.
I think so too. Being able to specify custom contexts would fit. Something like:
contexts = {
new_context = {
-- Maybe it can receive the selection and if there is a parameter in the prompts section, for each prompt, to specify the context for that prompt, it could auto pass the selection the the context's callback function.
callback = function(selection) {...},
-- If the code is online
url = "",
description = "",
}
}
Would a rename to participants be a good idea?
Maybe the prompts should have a context/participant field to indicate which to use.
Activity
deathbeam commentedon May 11, 2024
I think in this plugin scope it would be custom conext function I think? Even though custom selector also already can be used for same thing. I personally think the nvim-cmp "extension" system is terrible so I would def not want to go that route. For custom selector you can pass custom selection already as function, and I think for context we could do the same.
DRKolev-code commentedon May 11, 2024
I think so too. Being able to specify custom contexts would fit. Something like:
Would a rename to participants be a good idea?
Maybe the prompts should have a context/participant field to indicate which to use.