Discource-C
/
discourse-ai
mirror of https://github.com/discourse/discourse-ai.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse-ai/config/locales/client.en.yml

224 lines
8.8 KiB
YAML
Raw Normal View History

Initial commit
2023-02-17 09:33:47 -05:00
en:
DEV: Categorize plugin settings into discourse_ai (#144) Moving the plugin settings into a more specific category makes them easier to find in the plugin UI and removes them from the generic "Plugins" tab.
2023-08-21 13:46:34 -04:00
admin_js:
admin:
site_settings:
categories:
discourse_ai: "Discourse AI"
Initial commit
2023-02-17 09:33:47 -05:00
js:
FEATURE: automation rule for triaging posts using LLM (#236) The new automation rule can be used to perform llm based classification and categorization of topics. You specify a system prompt (which has %%POST%% as an input), if it returns a particular piece of text then we will apply rules such as tagging, hiding, replying or categorizing. This can be used as a spam filter, a "oops you are in the wrong place" filter and so on. Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
2023-10-02 17:55:30 -04:00
discourse_automation:
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
ai_models:
gpt_4_turbo: GPT 4 Turbo
gpt_4: GPT 4
gpt_3_5_turbo: GPT 3.5 Turbo
claude_2: Claude 2
gemini_pro: Gemini Pro
FEATURE: automation rule for triaging posts using LLM (#236) The new automation rule can be used to perform llm based classification and categorization of topics. You specify a system prompt (which has %%POST%% as an input), if it returns a particular piece of text then we will apply rules such as tagging, hiding, replying or categorizing. This can be used as a spam filter, a "oops you are in the wrong place" filter and so on. Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
2023-10-02 17:55:30 -04:00
scriptables:
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
llm_report:
fields:
sender:
label: "Sender"
description: "The user that will send the report"
receivers:
label: "Receivers"
FEATURE: allow sending AI based report to a topic (#377) This makes the reporting far more flexible cause it can target a far wider audience by pointing it at a topic in a secure category or an existing PM
2023-12-21 19:46:23 -05:00
description: "The users that will receive the report (emails will be sent direct emails, usernames will be sent a PM)"
topic_id:
label: "Topic ID"
description: "The topic id to post the report to"
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
title:
label: "Title"
description: "The title of the report"
days:
label: "Days"
description: "The timespan of the report"
offset:
label: "Offset"
description: "When testing you may want to run the report historically, use offset to start the report in an earlier date"
instructions:
label: "Instructions"
description: "The instructions provided to the large language model"
sample_size:
label: "Sample Size"
description: "The number of posts to sample for the report"
tokens_per_post:
label: "Tokens per post"
description: "The number of llm tokens to use per post"
model:
label: "Model"
description: "LLM to use for report generation"
categories:
label: "Categories"
FIX: typo (#432)
2024-01-18 10:38:29 -05:00
description: "Filter topics only to these categories"
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
tags:
label: "Tags"
description: "Filter topics only to these tags"
FEATURE: allow excluding tags and categories from LLM report (#447) Also - Better diagnostics, output model being used - Prompt LLM that true content is being injected in <context> tag
2024-01-29 23:55:05 -05:00
exclude_tags:
label: "Exclude Tags"
description: "Exclude topics with these tags"
exclude_categories:
label: "Exclude Categories"
description: "Exclude topics with these categories"
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
allow_secure_categories:
label: "Allow secure categories"
description: "Allow the report to be generated for topics in secure categories"
debug_mode:
label: "Debug Mode"
description: "Enable debug mode to see the raw input and output of the LLM"
priority_group:
label: "Priority Group"
FEATURE: even smoother streaming (#420) Account properly for function calls, don't stream through <details> blocks - Rush cooked content back to client - Wait longer (up to 60 seconds) before giving up on streaming - Clean up message bus channels so we don't have leftover data - Make ai streamer much more reusable and much easier to read - If buffer grows quickly, rush update so you are not artificially waiting - Refine prompt interface - Fix lost system message when prompt gets long
2024-01-15 02:51:14 -05:00
description: "Prioritize content from this group in the report"
FEATURE: fine tune llm report to follow instructions more closely (#451) - Allow users to supply top_p and temperature values, which means people can fine tune randomness - Fix bad localization string - Fix bad remapping of max tokens in gemini - Add support for top_p as a general param to llms - Amend system prompt so persona stops treating a user as an adversary
2024-01-30 17:58:25 -05:00
temperature:
label: "Temperature"
description: "Temperature to use for the LLM, increase to increase randomness (0 to use model default)"
top_p:
label: "Top P"
description: "Top P to use for the LLM, increase to increase randomness (0 to use model default)"
FEATURE: LLM based peroidical summary report (#357) Introduce a Discourse Automation based periodical report. Depends on Discourse Automation. Report works best with very large context language models such as GPT-4-Turbo and Claude 2. - Introduces final_insts to generic llm format, for claude to work best it is better to guide the last assistant message (we should add this to other spots as well) - Adds GPT-4 turbo support to generic llm interface
2023-12-18 20:04:15 -05:00
FEATURE: automation rule for triaging posts using LLM (#236) The new automation rule can be used to perform llm based classification and categorization of topics. You specify a system prompt (which has %%POST%% as an input), if it returns a particular piece of text then we will apply rules such as tagging, hiding, replying or categorizing. This can be used as a spam filter, a "oops you are in the wrong place" filter and so on. Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
2023-10-02 17:55:30 -04:00
llm_triage:
fields:
system_prompt:
label: "System Prompt"
description: "The prompt that will be used to triage, be sure for it to reply with a single word you can use to trigger the action"
search_for_text:
label: "Search for text"
description: "If the following text appears in the llm reply, apply this actions"
category:
label: "Category"
description: "Category to apply to the topic"
tags:
label: "Tags"
description: "Tags to apply to the topic"
canned_reply:
label: "Reply"
description: "Raw text of canned reply to post on the topic"
canned_reply_user:
label: "Reply User"
description: "Username of the user to post the canned reply"
hide_topic:
label: "Hide topic"
description: "Make topic non visible to the public if triggered"
model:
label: "Model"
description: "Either gpt-4 or gpt-3-5-turbo or claude-2"
FEATURE: Composer AI helper (#8) * FEATURE: Composer AI helper This change introduces a new composer button for the group members listed in the `ai_helper_allowed_groups` site setting. Users can use chatGPT to review, improve, or translate their posts to English. * Add a safeguard for PMs and don't rely on parentView
2023-03-15 16:02:20 -04:00
discourse_ai:
FEATURE: UI to update ai personas on admin page (#290) Introduces a UI to manage customizable personas (admin only feature) Part of the change was some extensive internal refactoring: - AIBot now has a persona set in the constructor, once set it never changes - Command now takes in bot as a constructor param, so it has the correct persona and is not generating AIBot objects on the fly - Added a .prettierignore file, due to the way ALE is configured in nvim it is a pre-req for prettier to work - Adds a bunch of validations on the AIPersona model, system personas (artist/creative etc...) are all seeded. We now ensure - name uniqueness, and only allow certain properties to be touched for system personas. - (JS note) the client side design takes advantage of nested routes, the parent route for personas gets all the personas via this.store.findAll("ai-persona") then child routes simply reach into this model to find a particular persona. - (JS note) data is sideloaded into the ai-persona model the meta property supplied from the controller, resultSetMeta - This removes ai_bot_enabled_personas and ai_bot_enabled_chat_commands, both should be controlled from the UI on a per persona basis - Fixes a long standing bug in token accounting ... we were doing to_json.length instead of to_json.to_s.length - Amended it so {commands} are always inserted at the end unconditionally, no need to add it to the template of the system message as it just confuses things - Adds a concept of required_commands to stock personas, these are commands that must be configured for this stock persona to show up. - Refactored tests so we stop requiring inference_stubs, it was very confusing to need it, added to plugin.rb for now which at least is clearer - Migrates the persona selector to gjs --------- Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com> Co-authored-by: Martin Brennan <martin@discourse.org>
2023-11-21 00:56:43 -05:00
title: "AI"
FEATURE: Chat channel summarization. (#32) * start summary module * chat channel summarization * FEATURE: modal for channel summarization --------- Co-authored-by: Roman Rizzi <rizziromanalejandro@gmail.com>
2023-04-04 10:24:09 -04:00
modals:
select_option: "Select an option..."
FEATURE: UI to update ai personas on admin page (#290) Introduces a UI to manage customizable personas (admin only feature) Part of the change was some extensive internal refactoring: - AIBot now has a persona set in the constructor, once set it never changes - Command now takes in bot as a constructor param, so it has the correct persona and is not generating AIBot objects on the fly - Added a .prettierignore file, due to the way ALE is configured in nvim it is a pre-req for prettier to work - Adds a bunch of validations on the AIPersona model, system personas (artist/creative etc...) are all seeded. We now ensure - name uniqueness, and only allow certain properties to be touched for system personas. - (JS note) the client side design takes advantage of nested routes, the parent route for personas gets all the personas via this.store.findAll("ai-persona") then child routes simply reach into this model to find a particular persona. - (JS note) data is sideloaded into the ai-persona model the meta property supplied from the controller, resultSetMeta - This removes ai_bot_enabled_personas and ai_bot_enabled_chat_commands, both should be controlled from the UI on a per persona basis - Fixes a long standing bug in token accounting ... we were doing to_json.length instead of to_json.to_s.length - Amended it so {commands} are always inserted at the end unconditionally, no need to add it to the template of the system message as it just confuses things - Adds a concept of required_commands to stock personas, these are commands that must be configured for this stock persona to show up. - Refactored tests so we stop requiring inference_stubs, it was very confusing to need it, added to plugin.rb for now which at least is clearer - Migrates the persona selector to gjs --------- Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com> Co-authored-by: Martin Brennan <martin@discourse.org>
2023-11-21 00:56:43 -05:00
ai_persona:
name: Name
description: Description
system_prompt: System Prompt
save: Save
saved: AI Persona Saved
enabled: Enabled
commands: Enabled Commands
allowed_groups: Allowed Groups
confirm_delete: Are you sure you want to delete this persona?
new: New
title: "AI Personas"
delete: Delete
priority: Priority
priority_help: Priority personas are displayed to users at the top of the persona list. If multiple personas have priority, they will be sorted alphabetically.
FEATURE: allow personas to provide command options (#331) Personas now support providing options for commands. This PR introduces a single option "base_query" for the SearchCommand. When supplied all searches the persona will perform will also include the pre-supplied filter. This can allow personas to search a subset of the forum (such as documentation) This system is extensible we can add options to any command trivially.
2023-12-07 16:42:56 -05:00
command_options: "Command Options"
FEATURE: UI to update ai personas on admin page (#290) Introduces a UI to manage customizable personas (admin only feature) Part of the change was some extensive internal refactoring: - AIBot now has a persona set in the constructor, once set it never changes - Command now takes in bot as a constructor param, so it has the correct persona and is not generating AIBot objects on the fly - Added a .prettierignore file, due to the way ALE is configured in nvim it is a pre-req for prettier to work - Adds a bunch of validations on the AIPersona model, system personas (artist/creative etc...) are all seeded. We now ensure - name uniqueness, and only allow certain properties to be touched for system personas. - (JS note) the client side design takes advantage of nested routes, the parent route for personas gets all the personas via this.store.findAll("ai-persona") then child routes simply reach into this model to find a particular persona. - (JS note) data is sideloaded into the ai-persona model the meta property supplied from the controller, resultSetMeta - This removes ai_bot_enabled_personas and ai_bot_enabled_chat_commands, both should be controlled from the UI on a per persona basis - Fixes a long standing bug in token accounting ... we were doing to_json.length instead of to_json.to_s.length - Amended it so {commands} are always inserted at the end unconditionally, no need to add it to the template of the system message as it just confuses things - Adds a concept of required_commands to stock personas, these are commands that must be configured for this stock persona to show up. - Refactored tests so we stop requiring inference_stubs, it was very confusing to need it, added to plugin.rb for now which at least is clearer - Migrates the persona selector to gjs --------- Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com> Co-authored-by: Martin Brennan <martin@discourse.org>
2023-11-21 00:56:43 -05:00
no_persona_selected: |
## What are AI Personas?
AI Personas are a powerful feature that allows you to customize the behavior of the AI engine in your Discourse forum. They act as a 'system message' that guides the AI's responses and interactions, helping to create a more personalized and engaging user experience.
## Why use AI Personas?
With AI Personas, you can tailor the AI's behavior to better fit the context and tone of your forum. Whether you want the AI to be more formal for a professional setting, more casual for a community forum, or even embody a specific character for a role-playing game, AI Personas give you the flexibility to do so.
## Group-Specific Access to AI Personas
Moreover, you can set it up so that certain user groups have access to specific personas. This means you can have different AI behaviors for different sections of your forum, further enhancing the diversity and richness of your community's interactions.
FEATURE: attempt to include related topics above suggested (#28) Allows related topics to show up for logged on users - Introduces a new "Related Topics" block above suggested when related topics exist - Renames `ai_embeddings_semantic_suggested_topics_anons_enabled` -> `ai_embeddings_semantic_suggested_topics_enabled` (given it is only deployed on 1 site not bothering with a migration) - Adds an integration test to ensure data arrives correctly on the client
2023-03-30 18:07:22 -04:00
related_topics:
FIX: Use "Related Topics" label consistently (#221)
2023-09-12 15:23:24 -04:00
title: "Related Topics"
UX: Update related-topics to follow <MoreTopics/> conventions (#118)
2023-07-31 17:33:37 -04:00
pill: "Related"
FEATURE: Composer AI helper (#8) * FEATURE: Composer AI helper This change introduces a new composer button for the group members listed in the `ai_helper_allowed_groups` site setting. Users can use chatGPT to review, improve, or translate their posts to English. * Add a safeguard for PMs and don't rely on parentView
2023-03-15 16:02:20 -04:00
ai_helper:
title: "Suggest changes using AI"
description: "Choose one of the options below, and the AI will suggest you a new version of the text."
selection_hint: "Hint: You can also select a portion of the text before opening the helper to rewrite only that."
FEATURE: Additional AI suggestion options (#176)
2023-09-01 20:10:58 -04:00
suggest: "Suggest with AI"
FIX: Show warning when trying to generate suggestions without content (#175)
2023-08-29 14:58:45 -04:00
missing_content: "Please enter some content to generate suggestions."
FEATURE: AI Helper Context Menu (#148)
2023-08-23 13:35:40 -04:00
context_menu:
FEATURE: Create custom prompts with composer AI helper (#214) * DEV: Add icon support * DEV: Add basic setup for custom prompt menu * FEATURE: custom prompt backend * fix custom prompt param check * fix custom prompt replace * WIP * fix custom prompt usage * fixes * DEV: Update front-end * DEV: No more custom prompt state * DEV: Add specs * FIX: Title/Category/Tag suggestions Suggestion dropdowns broke because it `messages_with_user_input(user_input)` expects a hash now. * DEV: Apply syntax tree * DEV: Restrict custom prompts to configured groups * oops * fix tests * lint * I love tests * lint is cool tho --------- Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com>
2023-09-25 14:12:54 -04:00
back: "Back"
FEATURE: AI Helper Context Menu (#148)
2023-08-23 13:35:40 -04:00
trigger: "AI"
undo: "Undo"
loading: "AI is generating"
cancel: "Cancel"
regen: "Try Again"
DEV: Add review menu state (#159)
2023-08-24 20:49:24 -04:00
view_changes: "View Changes"
confirm: "Confirm"
revert: "Revert"
changes: "Changes"
FEATURE: Create custom prompts with composer AI helper (#214) * DEV: Add icon support * DEV: Add basic setup for custom prompt menu * FEATURE: custom prompt backend * fix custom prompt param check * fix custom prompt replace * WIP * fix custom prompt usage * fixes * DEV: Update front-end * DEV: No more custom prompt state * DEV: Add specs * FIX: Title/Category/Tag suggestions Suggestion dropdowns broke because it `messages_with_user_input(user_input)` expects a hash now. * DEV: Apply syntax tree * DEV: Restrict custom prompts to configured groups * oops * fix tests * lint * I love tests * lint is cool tho --------- Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com>
2023-09-25 14:12:54 -04:00
custom_prompt:
title: "Custom Prompt"
placeholder: "Enter a custom prompt..."
submit: "Send Prompt"
FEATURE: AI helper on posts (#244) Adds an AI Helper function when selecting text while viewing a topic. --------- Co-authored-by: Keegan George <kgeorge13@gmail.com> Co-authored-by: Roman Rizzi <roman@discourse.org>
2023-10-23 10:41:36 -04:00
post_options_menu:
trigger: "Ask AI"
UX: Add title to button (#334)
2023-12-05 15:33:10 -05:00
title: "Ask AI"
FEATURE: AI helper on posts (#244) Adds an AI Helper function when selecting text while viewing a topic. --------- Co-authored-by: Keegan George <kgeorge13@gmail.com> Co-authored-by: Roman Rizzi <roman@discourse.org>
2023-10-23 10:41:36 -04:00
loading: "AI is generating"
close: "Close"
UX: Add copy button to generated suggestion (#296)
2023-11-17 12:25:41 -05:00
copy: "Copy"
copied: "Copied!"
FEATURE: Add streaming to post AI helper's explain option (#344) Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com> Co-authored-by: Roman Rizzi <roman@discourse.org>
2023-12-12 12:28:39 -05:00
cancel: "Cancel"
FEATURE: Proofread with post AI helper (#359)
2023-12-14 22:30:52 -05:00
fast_edit:
suggest_button: "Suggest Edit"
FEATURE: Generate post illustrations (#367)
2023-12-19 14:17:34 -05:00
thumbnail_suggestions:
title: "Suggested Thumbnails"
select: "Select"
selected: "Selected"
FEATURE: Use dedicated reviewables for AI flags. (#4) This change adds two new reviewable types: ReviewableAIPost and ReviewableAIChatMessage. They have the same actions as their existing counterparts: ReviewableFlaggedPost and ReviewableChatMessage. We'll display the model used and their accuracy when showing these flags in the review queue and adjust the latter after staff performs an action, tracking a global accuracy per existing model in a separate table. * FEATURE: Dedicated reviewables for AI flags * Store and adjust model accuracy * Display accuracy in reviewable templates
2023-03-07 13:39:28 -05:00
reviewables:
model_used: "Model used:"
accuracy: "Accuracy:"
FEATURE: port to use claude-2 for chat bot (#114) Claude 1 costs the same and is less good than Claude 2. Make use of Claude 2 in all spots ... This also fixes streaming so it uses the far more efficient streaming protocol.
2023-07-26 21:24:44 -04:00
FEATURE: Semantic assymetric full-page search (#34) Depends on discourse/discourse#20915 Hooks to the full-page-search component using an experimental API and performs an assymetric similarity search using our embeddings database.
2023-03-31 14:29:56 -04:00
embeddings:
semantic_search: "Topics (Semantic)"
FEATURE: HyDE-powered semantic search. (#136) * FEATURE: HyDE-powered semantic search. It relies on the new outlet added on discourse/discourse#23390 to display semantic search results in an unobtrusive way. We'll use a HyDE-backed approach for semantic search, which consists on generating an hypothetical document from a given keywords, which gets transformed into a vector and used in a asymmetric similarity topic search. This PR also reorganizes the internals to have less moving parts, maintaining one hierarchy of DAOish classes for vector-related operations like transformations and querying. Completions and vectors created by HyDE will remain cached on Redis for now, but we could later use Postgres instead. * Missing translation and rate limiting --------- Co-authored-by: Roman Rizzi <rizziromanalejandro@gmail.com>
2023-09-05 10:08:23 -04:00
semantic_search_loading: "Searching for more results using AI"
DEV: Only allow semantic search on "Relevance" sort mode (#306)
2023-11-23 14:30:17 -05:00
semantic_search_disabled_sort: "AI Search disabled for this sort order, sort by Relevance to enable."
FEATURE: HyDE-powered semantic search. (#136) * FEATURE: HyDE-powered semantic search. It relies on the new outlet added on discourse/discourse#23390 to display semantic search results in an unobtrusive way. We'll use a HyDE-backed approach for semantic search, which consists on generating an hypothetical document from a given keywords, which gets transformed into a vector and used in a asymmetric similarity topic search. This PR also reorganizes the internals to have less moving parts, maintaining one hierarchy of DAOish classes for vector-related operations like transformations and querying. Completions and vectors created by HyDE will remain cached on Redis for now, but we could later use Postgres instead. * Missing translation and rate limiting --------- Co-authored-by: Roman Rizzi <rizziromanalejandro@gmail.com>
2023-09-05 10:08:23 -04:00
semantic_search_results:
DEV: Mix semantic search results with normal results (#278)
2023-11-17 15:46:59 -05:00
toggle: "Showing %{count} results found using AI"
toggle_hidden: "Hiding %{count} results found using AI"
FEATURE: HyDE-powered semantic search. (#136) * FEATURE: HyDE-powered semantic search. It relies on the new outlet added on discourse/discourse#23390 to display semantic search results in an unobtrusive way. We'll use a HyDE-backed approach for semantic search, which consists on generating an hypothetical document from a given keywords, which gets transformed into a vector and used in a asymmetric similarity topic search. This PR also reorganizes the internals to have less moving parts, maintaining one hierarchy of DAOish classes for vector-related operations like transformations and querying. Completions and vectors created by HyDE will remain cached on Redis for now, but we could later use Postgres instead. * Missing translation and rate limiting --------- Co-authored-by: Roman Rizzi <rizziromanalejandro@gmail.com>
2023-09-05 10:08:23 -04:00
none: "Sorry, our AI search found no matching topics."
FIX: Prevent no results label from showing when untrue (#384)
2023-12-27 19:42:13 -05:00
new: "Press 'Search' to begin looking for new results with AI"
A11Y: Add title attribute to sparkles icon for AI search results (#317)
2023-11-27 17:25:33 -05:00
ai_generated_result: "Search result found using AI"
FEATURE: Chat channel summarization. (#32) * start summary module * chat channel summarization * FEATURE: modal for channel summarization --------- Co-authored-by: Roman Rizzi <rizziromanalejandro@gmail.com>
2023-04-04 10:24:09 -04:00
FEATURE: Introduce the ai-bot module (#52) This module lets you chat with our GPT bot inside a PM. The bot only replies to members of the groups listed on the ai_bot_allowed_groups setting and only if you invite it to participate in the PM.
2023-05-05 14:28:31 -04:00
ai_bot:
FEATURE: optional warning attached to all AI bot conversations (#137) * FEATURE: optional warning attached to all AI bot conversations This commit introduces `ai_bot_enable_chat_warning` which can be used to warn people prior to starting a chat with the bot. In particular this is useful if moderators are regularly reading chat transcripts as it sets expectations early. By default this is disabled. Also: - Stops making ajax call prior to opening composer - Hides PM title when starting a bot PM Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com>
2023-08-16 16:29:58 -04:00
pm_warning: "AI chatbot messages are monitored regularly by moderators."
UX: Add missing label translation (#64)
2023-05-16 15:56:30 -04:00
cancel_streaming: "Stop reply"
FEATURE: Less friction for starting a conversation with an AI bot. (#63) * FEATURE: Less friction for starting a conversation with an AI bot. This PR adds a new header icon as a shortcut to start a conversation with one of our AI Bots. After clicking and selecting one from the dropdown menu, we'll open the composer with some fields already filled (recipients and title). If you leave the title as is, we'll queue a job after five minutes to update it using a bot suggestion. * Update assets/javascripts/initializers/ai-bot-replies.js Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com> * Update assets/javascripts/initializers/ai-bot-replies.js Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com> --------- Co-authored-by: Rafael dos Santos Silva <xfalcox@gmail.com>
2023-05-16 13:38:21 -04:00
default_pm_prefix: "[Untitled AI bot PM]"
UX: Add missing label translation (#64)
2023-05-16 15:56:30 -04:00
shortcut_title: "Start a PM with an AI bot"
FEATURE: allow easy sharing of bot conversations (#385) * FEATURE: allow easy sharing of bot conversations * Lean on new core API i * Added system spec for copy functionality * Update assets/javascripts/initializers/ai-bot-replies.js Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com> * discourse later insted of setTimeout * Update spec/system/ai_bot/share_spec.rb Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com> * feedback from review just check the whole payload * remove uneeded code * fix spec --------- Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com>
2023-12-29 03:47:47 -05:00
share: "Share AI conversation"
UX: copy change (#390)
2023-12-29 10:26:03 -05:00
conversation_shared: "Conversation copied"
FEATURE: allow easy sharing of bot conversations (#385) * FEATURE: allow easy sharing of bot conversations * Lean on new core API i * Added system spec for copy functionality * Update assets/javascripts/initializers/ai-bot-replies.js Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com> * discourse later insted of setTimeout * Update spec/system/ai_bot/share_spec.rb Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com> * feedback from review just check the whole payload * remove uneeded code * fix spec --------- Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com>
2023-12-29 03:47:47 -05:00
ai_label: "AI"
ai_title: "Conversation with AI"
share_modal:
title: "Share AI conversation"
copy: "Copy"
context: "Interactions to share:"
FEATURE: Introduce the ai-bot module (#52) This module lets you chat with our GPT bot inside a PM. The bot only replies to members of the groups listed on the ai_bot_allowed_groups setting and only if you invite it to participate in the PM.
2023-05-05 14:28:31 -04:00
UX: Improvements to the AI Bot header shortcut (#66) - Humanize model names - Focus composer editor when starting a PM with a bot - Correctly close the models dropdown when clicking outside
2023-05-17 14:59:48 -04:00
bot_names:
gpt-4: "GPT-4"
FEATURE: implement GPT-4 turbo support (#345) Keep in mind: - GPT-4 is only going to be fully released next year - so this hardcodes preview model for now - Fixes streaming bugs which became a big problem with GPT-4 turbo - Adds Azure endpoing for turbo as well Co-authored-by: Martin Brennan <martin@discourse.org>
2023-12-10 22:59:57 -05:00
gpt-4-turbo: "GPT-4 Turbo"
UX: Improvements to the AI Bot header shortcut (#66) - Humanize model names - Focus composer editor when starting a PM with a bot - Correctly close the models dropdown when clicking outside
2023-05-17 14:59:48 -04:00
gpt-3:
5-turbo: "GPT-3.5"
FEATURE: port to use claude-2 for chat bot (#114) Claude 1 costs the same and is less good than Claude 2. Make use of Claude 2 in all spots ... This also fixes streaming so it uses the far more efficient streaming protocol.
2023-07-26 21:24:44 -04:00
claude-2: "Claude 2"
FEATURE: AI Bot Gemini support. (#402) It also corrects the syntax around tool support, which was wrong. Gemini doesn't want us to include messages about previous tool invocations, so I had to shuffle around some code to send the response it generated from those invocations instead. For this, I created the "multi_turn" context, which bundles all the context involved in the interaction.
2024-01-04 16:15:34 -05:00
gemini-pro: "Gemini"
FEATURE: Add Mixtral support for AI Bot (#396)
2024-01-04 10:22:43 -05:00
mixtral-8x7B-Instruct-V0:
"1": "Mixtral-8x7B V0.1"
FEATURE: Expose sentiment classifications via the admin dashboard. (#284) This PR adds new reports for displaying information about post sentiments grouped by date and emotions group by TL. Depends on discourse/discourse#24274
2023-11-08 08:50:37 -05:00
sentiments:
dashboard:
title: "Sentiment"
FEATURE: Use dedicated reviewables for AI flags. (#4) This change adds two new reviewable types: ReviewableAIPost and ReviewableAIChatMessage. They have the same actions as their existing counterparts: ReviewableFlaggedPost and ReviewableChatMessage. We'll display the model used and their accuracy when showing these flags in the review queue and adjust the latter after staff performs an action, tracking a global accuracy per existing model in a separate table. * FEATURE: Dedicated reviewables for AI flags * Store and adjust model accuracy * Display accuracy in reviewable templates
2023-03-07 13:39:28 -05:00
review:
types:
FIX: Fix reviewable title translations (#18)
2023-03-20 09:09:20 -04:00
reviewable_ai_post:
FEATURE: Use dedicated reviewables for AI flags. (#4) This change adds two new reviewable types: ReviewableAIPost and ReviewableAIChatMessage. They have the same actions as their existing counterparts: ReviewableFlaggedPost and ReviewableChatMessage. We'll display the model used and their accuracy when showing these flags in the review queue and adjust the latter after staff performs an action, tracking a global accuracy per existing model in a separate table. * FEATURE: Dedicated reviewables for AI flags * Store and adjust model accuracy * Display accuracy in reviewable templates
2023-03-07 13:39:28 -05:00
title: "AI-Flagged post"
FIX: Fix reviewable title translations (#18)
2023-03-20 09:09:20 -04:00
reviewable_ai_chat_message:
FEATURE: Use dedicated reviewables for AI flags. (#4) This change adds two new reviewable types: ReviewableAIPost and ReviewableAIChatMessage. They have the same actions as their existing counterparts: ReviewableFlaggedPost and ReviewableChatMessage. We'll display the model used and their accuracy when showing these flags in the review queue and adjust the latter after staff performs an action, tracking a global accuracy per existing model in a separate table. * FEATURE: Dedicated reviewables for AI flags * Store and adjust model accuracy * Display accuracy in reviewable templates
2023-03-07 13:39:28 -05:00
title: "AI-Flagged chat message"