Chatbot Release Notes

by

in

After a rather lengthy development cycle, we are proud to announce a major release of our Chatbot.  We’ve made significant progress in the following areas:

  • Scalability
  • Characters and agents
  • Autosaving of content
  • Full featured article production
  • User settings

Scalability

Improvements to configuration management and our deployment process allow our full stack solution to be easily scaled to any number of domains/subdomains. 

Characters

We’ve made some major changes to our UI and our backend to improve support for AI characters. The character dashboards provide centralized access for communication, configuration, etc. You’ll also be able to set up your character to perform tasks that they perform on their own throughout the day. We’ve also Improved character creation, editing, browsing, and conversation persistence.

Autosaving of content

Autosaving isn’t the right approach for all sites.  Some sites need greater control over content and will require users to save, approve, and publish content.  But for some web sites this feature will be ideal.  For example, autosave could allow all of a student’s work to be saved and published (internally) for review by a teacher, or a site used for pure research could have a complete record of all human/AI conversations.

Full featured article production

Full featured articles can be generated on demand through the character dashboards, or using our CLI (Command line environment) interface.  In addition, users can schedule characters to write full featured articles. 

User Settings

We’ve added a settings page to give users more control and visibility.

  • Autosave  You guessed it – this is where users can toggle autosave functionality between “off”, “on”, and “publish”.
  • Unsaved changes If you’re not using the autosave feature, you can review and save your unsaved work here.
  • Route caching  You won’t normally need to access or understand this information, but it can help us diagnose issues. 

– Dev Team


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *