feat: save account model and thinking settings for Hermes
Rebuild & Deploy / rebuild (push) Successful in 1m9s

This commit is contained in:
snowspeeder committed 2026-10-01 16:38:34 -04:00
1 parent a45569f8c1
commit 6cb4427210
13 files changed
+798 -16

No files matched your search

+22
View File
@@ -77,6 +77,28 @@ also passes `model_options.reasoning.enabled: false` and forwards content only.
assertion races; synchronization fixed, focused settings/large-type/account
switch tests passed. No claim of one fully green expanded UI run.
## Account model and thinking settings
- The authenticated Hope settings sheet loads the Manifest upstream `/v1/models`
catalog through the trusted control plane. Only public IDs/names and application
effort choices are returned; the browser never receives provider credentials.
- `GET` / `PUT /api/settings/model` operate only on the signed-in account. Preferences
persist in a separate SQLite table with account-deletion cascade. Existing accounts
default to `auto` / `none`. Cookie mutations require a trusted Origin.
- The speech bridge resolves authorized room settings at every request, including
existing conversations, and snapshots them for that turn. No interruption/replay.
It sends the chosen model with explicit `provider: custom:hope-upstream`; a bare
model would be ignored by the deployed Hermes API's default policy.
- Thinking choices are requested efforts, not guarantees of model support. Manifest
currently provides no capability metadata; Hermes may clamp levels or omit a
disabled reasoning field where an upstream model cannot represent `none`.
- Reasoning content is still excluded from transcripts/speech. Discovery failures
preserve saved settings and disable changes rather than silently selecting a model.
- Hermes gateway `/model` session overrides have higher precedence than ordinary
OpenAI-compatible request overrides. Hope does not expose that session command.
The deployed configuration inspected has no fallback chain. OpenAI SSE `model`
echoes the request and is not independent proof of the upstream executing model.
## Operational behavior and boundaries
- Each user has separate persistent state, API credential, bridge network,