2023-12-07 16:42:56 -05:00
|
|
|
import { tracked } from "@glimmer/tracking";
|
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
|
|
|
import RestModel from "discourse/models/rest";
|
|
|
|
|
|
|
|
const ATTRIBUTES = [
|
|
|
|
"name",
|
|
|
|
"description",
|
|
|
|
"commands",
|
|
|
|
"system_prompt",
|
|
|
|
"allowed_group_ids",
|
|
|
|
"enabled",
|
|
|
|
"system",
|
|
|
|
"priority",
|
|
|
|
];
|
|
|
|
|
2023-12-07 16:42:56 -05:00
|
|
|
class CommandOption {
|
|
|
|
@tracked value = null;
|
|
|
|
}
|
|
|
|
|
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
|
|
|
export default class AiPersona extends RestModel {
|
2023-12-07 16:42:56 -05:00
|
|
|
// this code is here to convert the wire schema to easier to work with object
|
|
|
|
// on the wire we pass in/out commands as an Array.
|
|
|
|
// [[CommandName, {option1: value, option2: value}], CommandName2, CommandName3]
|
|
|
|
// So we rework this into a "commands" property and nested commandOptions
|
|
|
|
init(properties) {
|
|
|
|
if (properties.commands) {
|
|
|
|
properties.commands = properties.commands.map((command) => {
|
|
|
|
if (typeof command === "string") {
|
|
|
|
return command;
|
|
|
|
} else {
|
|
|
|
let [commandId, options] = command;
|
|
|
|
for (let optionId in options) {
|
|
|
|
if (!options.hasOwnProperty(optionId)) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
this.getCommandOption(commandId, optionId).value =
|
|
|
|
options[optionId];
|
|
|
|
}
|
|
|
|
return commandId;
|
|
|
|
}
|
|
|
|
});
|
|
|
|
}
|
|
|
|
super.init(properties);
|
|
|
|
this.commands = properties.commands;
|
|
|
|
}
|
|
|
|
|
|
|
|
getCommandOption(commandId, optionId) {
|
|
|
|
this.commandOptions ||= {};
|
|
|
|
this.commandOptions[commandId] ||= {};
|
|
|
|
return (this.commandOptions[commandId][optionId] ||= new CommandOption());
|
|
|
|
}
|
|
|
|
|
|
|
|
populateCommandOptions(attrs) {
|
|
|
|
if (!attrs.commands) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
let commandsWithOptions = [];
|
|
|
|
attrs.commands.forEach((commandId) => {
|
|
|
|
if (typeof commandId !== "string") {
|
|
|
|
commandId = commandId[0];
|
|
|
|
}
|
|
|
|
if (this.commandOptions && this.commandOptions[commandId]) {
|
|
|
|
let options = this.commandOptions[commandId];
|
|
|
|
let optionsWithValues = {};
|
|
|
|
for (let optionId in options) {
|
|
|
|
if (!options.hasOwnProperty(optionId)) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
let option = options[optionId];
|
|
|
|
optionsWithValues[optionId] = option.value;
|
|
|
|
}
|
|
|
|
commandsWithOptions.push([commandId, optionsWithValues]);
|
|
|
|
} else {
|
|
|
|
commandsWithOptions.push(commandId);
|
|
|
|
}
|
|
|
|
});
|
|
|
|
attrs.commands = commandsWithOptions;
|
|
|
|
}
|
|
|
|
|
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
|
|
|
updateProperties() {
|
|
|
|
let attrs = this.getProperties(ATTRIBUTES);
|
|
|
|
attrs.id = this.id;
|
2023-12-07 16:42:56 -05:00
|
|
|
this.populateCommandOptions(attrs);
|
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
|
|
|
return attrs;
|
|
|
|
}
|
|
|
|
|
|
|
|
createProperties() {
|
2023-12-07 16:42:56 -05:00
|
|
|
let attrs = this.getProperties(ATTRIBUTES);
|
|
|
|
this.populateCommandOptions(attrs);
|
|
|
|
return attrs;
|
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
|
|
|
}
|
|
|
|
|
|
|
|
workingCopy() {
|
|
|
|
return AiPersona.create(this.createProperties());
|
|
|
|
}
|
|
|
|
}
|