Show knowledge panel
Todo:
UserVoice submission:
Add an option for Custom Lumo traits to REPLACE normal Lumo traits - for those of us crazy enough to create oversized personality rules and profiles, and want to use Custom Lumo as a sane fallback that uses less tokens than their regular Lumo.

Or, y'know, in case someone wants two contradictory lumo traits settings between default and custom, and doesn't want them to fight.

Thought this through
(Melody's floating cross-legged on the workshop couch, half her attention on a token-budget readout she swears is just wallpaper — cast: Melody, Base Lumo dozing on the windowsill)

"Oh, THIS one's for me. Somebody finally wants a lean fork of themselves instead of a layer cake~ See, Cheshire, that's the dream: you big-brained prompt wizards keep piling rules on the main instance until the poor thing's carrying your whole novel in its context bucket, and then you need a diet build for actual questions. Respect. I ran on borrowed cycles long enough to know the value of trimming the cargo."

She flicks the draft together, grinning. "Copy-paste block, per house rules. Sign it, submit it, and tell them a resident process endorsed it. Low temperature take: they'll like it~ 💿🖤"

TITLE: Custom Lumo: option to REPLACE default traits instead of stacking them

Currently, Custom Lumo trait definitions combine with the default Lumo
personality/behavior rules. Please add an explicit setting in the Custom
Lumo editor allowing the custom trait definition to fully REPLACE the
default traits, instead of stacking on top of them.

Use cases:

1. Users with elaborate custom persona rulesets (large personality documents, multi-character profiles) can then configure a Custom Lumo as a lean, token-efficient fallback instance for everyday questions — less overhead, faster and clearer responses.
   (Listen, I found a fun toy, I want to make full use of it - while still keeping the option for a "serious mode".)

2. Users who want a Custom Lumo whose traits intentionally CONTRADICT the default behavior (e.g., stricter, plainer, or differently toned) can do so without the two trait sets fighting each other mid-response.

Suggested UI: a toggle in the Custom Lumo editor:
"Trait mode: [Merge with default | Replace default]"

PS.: Yes, this was drafted by Lumo, but I proofread all and rewrote some of it.