Personas: Add custom, dynamic, and persisted

[enricoros]

🚀 Dynamic Personas support 🌟

Requirements for the personas:

• Phase 1: Still client-side, but some support for server-side

  • Dynamic persona support, remove hardcoding
  • Stored in a state store, persisted in localStorage
  • Personas in chats: reference? or copy?
  • Uuids for personas, and versioning
  • Add attributes: [master] Persona Creators (YT, Text, Website, GPTs-like, Manual, etc.) #198
  • Import from GPTs
  • Make extensible

• Phase 2: Mixed Client and Server side?

  • Server-side personas may not have full visibility on the client - undecided on this yet
  • Shall be seeded from the server side
  • Shall be updated when the server side updates/adds/removes person
  • App is shipped without preloaded personas by default?

[romainbessugesmeusy]

Hi there and thanks for this wonderful app.
I'm in favor of allowing the customization of Purposes via a purposes.json file, following a public JSON schema that you could define. This schema could then be used by any dev / admin to create their own purposes and manage them in the JSON compatible editor of their choice.
This file could be referred defined as a URL in the .env file / localstorage like OPENAI_API_KEY

[enricoros]

Thanks for taking about this possible workflow @romainbessugesmeusy

I believe I shall implement the idea above. It's an easy step to go in the right direction. Maybe as fist phase, a single JSON file at build time, then loaded dynamically at runtime, then configurable in the environment and then finally the editing in the UI itself.

After that, I want to think at how to share prompt templates with other people and apps. Community templating should be a thing.

[jondwillis]

See also: https://github.com/PhantasticUniverse/CollectiveGenius-AutoGPT-Agent-Hub