Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

Overview

Some organizations use multiple LLM models that are fine-tuned for different tasks. Currently, the initial AI Copilot release supports multiple models, but they cannot be used for the same function across the workspace and end users cannot opt to change the default model for AI Copilot interactions once configured in the system console.

A differentiator with Mattermost’s AI plugin is the flexibility being offered. The aim is to enhance that flexibility even further by allowing multiple LLM models in the following ways:

  • Configure multiple bots/models for use throughout the workspace

  • Provide the ability for end users to see the bot their interacting with and change that if there are multiple bots configured in the workspace

  • Provide ability to tag/mention different bots to engage with specific pre-configured LLMs

Configuring bots/models in the system console

Empty state - no bots added yet

Before any bots have been added, the empty state looks like below.

image-20240320-211845.png

Bots added state

Once bots are added, they will show in the list like below.

image-20240320-205954.png

Collapsable bot items

Each bot in the list is a collapsable element.

Collapsed - default state

image-20240320-204730.png

Collapsed - hover state

image-20240320-204405.png

Expanded state

image-20240322-184409.png

For each bot added to the plugin, admins can configure the following:

  • Display name: How the bot will display in the configuration and how users will see the bot displayed

    • NOTE: This does not change the “AI copilot” name - this is just the name that is displayed in the bot tag/dropdown

  • Service: The LLM provider (e.g. Open AI, Anthropic, etc)

  • API Key: The API key provided by the LLM provider

  • Default Model: A model that you can access with your API key (e.g. gpt-4)

  • Bot icon: The bot’s avatar image that will be displayed for replies directly from the bot

  • Team access: By default all teams are added, but admins can remove specific teams to restrict access to specific bots

  • Instructions: Admins can provide specific instructions to fine-tune the bot responses in order for the bot to respond or act in specific ways.

Enterprise-only notice

For non-enterprise workspaces, they cannot add multiple bots and a notice will display.

image-20240320-210009.png

Deleting a bot

Users can delete an AI bot by clicking the delete icon on the right side of an AI bot item. A confirmation modal displays to confirm they want to remove the bot.

image-20240320-213538.pngimage-20240320-213343.png

AI functions section

The ‘AI functions’ section is hidden until the first bot has been added. If only one bot is added, the bot function dropdowns are disabled (since there is only one option).

Displaying the active bot to end users

If there is only one bot configured in the system console, don’t display the dropdown/label to end users - except in the user profile popover.

If there is more than one bot configured in the system console, then we display the AI bot to end users. in the following locations:

In the context menus

image-20240320-183823.pngimage-20240320-183827.png

In the AI Copilot RHS

image-20240320-184101.png

In the AI Copilot profile popover

image-20240320-184227.png

In the Chat history

A label is added to the footer of each chat history preview to show the bot it uses.

image-20240320-184507.png

Changing bots/models for end users

A bot label appears in the top-right of the AI copilot header. In a new chat with now response yet from the AI, this label becomes a dropdown which can be clicked to change the bot before chatting.

image-20240320-205812.png

Once a chat has a response from AI, this label cannot be changed and the dropdown arrow is hidden.

image-20240320-211536.png

  • No labels