[Feature Request] - Define multiple customised assistants

[ga-it]

It would be very useful to define assistants with custom handles and custom prompts.

This should allow us to call the custom assistant by the handle as we currently do using the [at]assistant and for it to behave in line with its custom prompt.

[edward-ly]

I'm not sure if I understand the value a user-specified handle would bring to the app. Could you provide an example use case where changing the handle would be useful? Or do you just want to change the current default handle to something else?

[ga-it]

Having different custom prompts for different assistants would allow these to operate as specialist assistants - kind of like "Custom GPTs"

So, an assistant might be defined to manage knowledge on a specific topic - e.g. meeting etiquette, domain expertise (e.g. industry expert), etc. If the assistant has access to context chat this starts becoming very powerful - e.g. a company policy expert.

Defining these with separate handles allows calling them the way openai custom-gpts can be called

[edward-ly]

Ah OK, so it looks like what you are actually requesting is having separate handles that each process a different task (for example, @summarize or @contextualize for summarizing or contextualizing the input prompt, respectively). Sounds like a cool idea, although we can only support tasks that are available in the Task Processing API. More complex tasks outside of that API or tasks that require additional input/modifications might require a separate bot/app altogether. I'd be inclined to go that route anyway even for the more basic tasks, as that would allow each bot to have their own dedicated handle. Otherwise, having a single bot control multiple handles means that, for one, it's not possible to enable/disable individual handles.

If you still want to include a few extra tasks in this talk bot and not in a separate app, here's what the code changes might look like:

1. Replace assistant in the matching regular expression with a capture group, allowing you to reference it later.
2. Change the desired Task Processing task depending on whatever assistant is changed to, and update the input parameters accordingly.
3. Update any relevant documentation.

PRs are welcome and we'd be happy to review it if you decide to submit one. Let us know what you decide to do.

[ga-it]

Yes - that is what I am suggesting

Effectively it allows the redefinition of the bot as a custom agent. I realise that begs the question as to whether you go the full route to adopting a full agentic framework with handoffs, etc. I think that does deserve some thought given the rapid development in that space and the move towards agent use in Nextcloud

Essential to that task is then the ability to properly define agents

From a handle perspective, it could perhaps be as a suffix to the app bot - e.g. @assistant_summarize - or some format that makes interfacing with the NC user naming system and routing to the right agent easy