244d296646
Personality persistence used to be split per surface: the TUI/desktop wrote the NAME to display.personality while the CLI/gateway wrote rendered TEXT into agent.system_prompt (and their /personality none only blanked the text, leaving the name behind). When #81946 made display.personality authoritative everywhere, stale names written long ago resurrected personalities users had turned off - kawaii defaulting on after updating. - hermes_cli/personality.py: new single owner of personality state. Built-in personality definitions, neutral-name normalization, rendering, availability (built-ins overlaid by agent.personalities), overlay resolution, and the ONLY sanctioned persistence path (persist_personality -> display.personality; never agent.system_prompt). - v34 config migration: one-time reset of display.personality to none (announcing which personality was cleared and how to re-enable), plus a scrub of agent.system_prompt when it verbatim-equals a known personality render (machine-written by the old CLI/gateway). Hand-written manual prompts are never touched. - All surfaces rewired through the module: CLI /personality (incl. active marker in the list), gateway /personality, TUI config.set + slash path (which previously applied without persisting), TUI config.get (reports the EFFECTIVE personality), completer, hermes config display, and the tui_gateway health probe. - cli.py/config duplicates removed: built-ins now defined once; the desktop mirrors them from one lib module (src/lib/personalities.ts). - Docs updated: selection lives in display.personality, built-ins always available, one-time reset note. |
||
|---|---|---|
| .. | ||
| docs | ||
| i18n/zh-Hans/docusaurus-plugin-content-docs/current | ||
| scripts | ||
| src | ||
| static | ||
| .gitignore | ||
| .npmrc | ||
| README.md | ||
| docusaurus.config.ts | ||
| package-lock.json | ||
| package.json | ||
| sidebars.ts | ||
| tsconfig.json | ||
README.md
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.