Create system tags & record system tag message when using to multi-prompt bot

[stephherbers]

Creates a new the of tag called a "System Tag" that is when a tag is created and added automatically and without a user

What's unique:

• No user is needed during creation
• They cannot be edited or deleted by a user
• Current use is to add which bot is used during a chat session, but can be applied to future uses

Example session with a multi-prompt bot:

Resulting tags added:

Example of the "Select a Tag..." multi-select where the system tags are shown, but cannot be added by user

[SmittieC]

I like these changes! We can now easily use these changes to tackle this ticket. General thoughts:

• I think we should keep a list of "reserved" tags that users are not allowed to duplicate. So if users goes to the tag management page and try and create a tag with the same name as a system tag, we should tell them that this is reserved.
• This makes me wonder about the following scenario: Since experiment names are now potential system tags, should we disallow users from the get-go to create tags with an experiment name?
• What about future experiments with the same name as existing tags? If I have a tag named "X" and I create an experiment named "X" later on, then this tag will be used when we tag a message. Should the user be allowed to delete this tag then?

~I'm starting to wonder if we shouldn't make system tags even more distinguised. Maybe by prefixing system tags with "system:". This way, we should only disallow users to create tags prefixed with "system:". Thoughts?~

Update

I chatted with @snopoke and a few things came up:

• Instead of using the Experiment name as the tag name, let's rather use the keyword from the ExperimentRoute as the tag name. Since this keyword is only used internally, we can keep this static.
• We should not use a system prefix like I mentioned above, since we already know when it's a system message. This did lead to a discussion about namespacing tags.
• Namespacing tags: We can do this by adding a new category like column to the Tag model. These categories will be used to show if the tags are related to a bot response, a safety layer violation or whatever we dream up in the future. We can use a CharField with an Enum for the categories.
• We need to add is_system_tag to the unique_together family. This will allow users to create tags with the same name as a system tag and not throw a unique constraint DB error. (If we're adding a category column, I'm guessing we'll need to add this there are well)

@snopoke I think this is everything we covered

[stephherbers]

thanks for the feedback everyone. Main design changes implemented today:

• added Category to Tag model
• added category and is_system_tag to unique_together in Tag model
• changes system tag name to the ExpRoute keyword
• removed system tags from dropdowns
• only adds system tags when using a multi-prompt bot

[stephherbers]

leaving the remain unblocking comments to a separate PR since this one is already very big 👍

[sentry-io[bot]]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ BadRequestError: Error code: 400 - {'error': {'message': "This model's maximum context length is 8192 tokens. Howe... apps.experiments.tasks.get_response_for_webchat... View Issue

_{Did you find this useful? React with a 👍 or 👎}