You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce a system that will allow users to select from a list of personalities Navi can use in day to day operations.
Reasons
Some people want Navi's personality. Others dont.
At the end of the day. I want Navi to be customized to what the users want. Make her yours.
The easiest thing we can do to remedy this is to give the users agency over how Navi presents herself.
Shipped Shards:
Navi will come with some shards by default
OG Navi / Navi-chan (Pumpkin Spice and Neon Drip)
Cybersec / Professional (Navi CLI)
Straight Facts (Navi research model)
Delphine (The Navi GF Mod meme)
It should be noted that Llama 3.2 is censored and guard railed so she wont get too out of pocket. However I intend our in house model to be uncensored.
System Outline / TODO
Ship Navi with a few custom personalities.
Make them listable
Make them swapable /default like memories
Give users a chip creator like system that to build custom shards.
Allow users the ability to upload shards to github.
Give the cli app the following options: List, Search, Create, Edit, Remove, Set-Active, Set-Default
When the user creates a new chip. Give them the ability to build the shard right from the command line. Else open in default code editor.
When working with shards users should have certain default headers to put customizations under.
[info] | [knowledge] | [forbidden] | [custom] to name a few however the user can make their own this is more or less for organization more than anything. Not sucks like having to filter through a whole text wall of customization trying to find the one line you want to edit to fix why your model is too obsessed with giraffes or PSL's.
The text was updated successfully, but these errors were encountered:
Goal
Introduce a system that will allow users to select from a list of personalities Navi can use in day to day operations.
Reasons
The easiest thing we can do to remedy this is to give the users agency over how Navi presents herself.
Shipped Shards:
Navi will come with some shards by default
It should be noted that Llama 3.2 is censored and guard railed so she wont get too out of pocket. However I intend our in house model to be uncensored.
System Outline / TODO
When working with shards users should have certain default headers to put customizations under.
[info] | [knowledge] | [forbidden] | [custom] to name a few however the user can make their own this is more or less for organization more than anything. Not sucks like having to filter through a whole text wall of customization trying to find the one line you want to edit to fix why your model is too obsessed with giraffes or PSL's.
The text was updated successfully, but these errors were encountered: