fix(web): find a keyless primary's provider from the model id (UF-054, UF-055)
A provider without its key lists no models, so Model Pilot could not tell the primary needed a key, and it compared a prefixed active id with a bare one. The provider now also comes from the id's prefix or family name, and prefixed and bare ids count as the same model. The account row's fallback initial is A for Account, not W.
This commit is contained in:
@@ -546,7 +546,7 @@ Entries UF-010 to UF-019 come from the UI audit `anti-slop/audit-001-2026-10-14.
|
||||
- Where: at commit `b20b138`, `apps/web/src/components/os/ModelPilotCard.tsx:361` (the Primary lane) and `apps/web/src/components/os/StatusBar.tsx:160` ("Default model:")
|
||||
- Symptom: Settings → Models shows Claude Sonnet 4.6 as the primary model, while the status bar says "Default model: Llama3.1 (8b)".
|
||||
- Cause: both are true. The primary has no API key, so the server's usable-model check routes new chats to the local model, and the status bar shows that model. Model Pilot only shows the configured primary and never says it cannot answer.
|
||||
- What we did: when the primary's provider needs a key the vault lacks, Model Pilot says so under Primary and names the model new chats use until a key is added. Settings reads that model from the server. A test covers the keyless, unknown and keyed cases.
|
||||
- What we did: when the primary's provider needs a key the vault lacks, Model Pilot says so under Primary and names the model new chats use until a key is added. A keyless provider lists no models, so the provider comes from the model id (prefix or family name), and ids with and without the provider prefix count as the same model. Settings reads the active model from the server. Tests cover the keyless, prefixed, unknown and keyed cases.
|
||||
- Recommendation: apply the same change in the main project.
|
||||
|
||||
### UF-055. Home greets the user by the assistant's name
|
||||
@@ -555,7 +555,7 @@ Entries UF-010 to UF-019 come from the UI audit `anti-slop/audit-001-2026-10-14.
|
||||
- Where: at commit `b20b138`, `packages/server/src/local/routes/home.ts:265` (the greeting name) and `apps/web/src/components/os/AppShell.tsx:206` (the sidebar account row); the default comes from `packages/agent/src/auto-identity.ts`
|
||||
- Symptom: a user who left their name empty during onboarding sees "Welcome, Waggle" on Home and "Waggle" as the account name in the sidebar.
|
||||
- Cause: both read the name from the identity row. At startup the sidecar fills that row with the assistant's own identity, named "Waggle", and onboarding only overwrites it when the user types a name.
|
||||
- What we did: the name comes from profile.json, which the user states. The identity row is a fallback and its default assistant name is ignored, so with no name the greeting has none and the account row reads "Account". The agent package exports the default name as `DEFAULT_AGENT_NAME`. Server and web tests cover a profile name, a real identity name and the default.
|
||||
- What we did: the name comes from profile.json, which the user states. The identity row is a fallback and its default assistant name is ignored, so with no name the greeting has none and the account row reads "Account" with the initial A. The agent package exports the default name as `DEFAULT_AGENT_NAME`. Server and web tests cover a profile name, a real identity name and the default.
|
||||
- Recommendation: apply the same change in the main project, and keep the assistant's identity apart from the user's.
|
||||
|
||||
### UF-056. Home calls the last 24 hours "While you slept"
|
||||
|
||||
Reference in New Issue
Block a user