emozilla c3a21c5d49 feat(desktop): route Nous subscribers onto the Tool Gateway from the GUI ... When the GUI sets the main provider to Nous via POST /api/model/set, call the same apply_nous_managed_defaults the CLI uses after model selection, so GUI/onboarding users land on the Nous Tool Gateway the same way CLI users do — no separate prompt, no duplicated logic. Purely additive: apply_nous_managed_defaults skips any tool where the user has a direct key (FIRECRAWL_API_KEY, FAL_KEY, etc.) or explicit config, so it never overwrites a user's own setup. Only unconfigured tools get routed. - web_server.py: in set_model_assignment (scope=main, provider=nous), resolve enabled toolsets and apply managed defaults; guarded so a Portal hiccup never blocks saving the model. Returns routed tools as gateway_tools. - onboarding.ts: surface a 'Tool Gateway enabled' toast listing routed tools. - types/hermes.ts: add gateway_tools to ModelAssignmentResponse. - tests: cover nous-applies, non-nous-skips, and failure-doesnt-block-save.		2026-05-31 05:10:33 -04:00
..
bootstrap-installer	macOS desktop: install + in-app self-update (#35607)	2026-05-30 22:26:08 -05:00
desktop	feat(desktop): route Nous subscribers onto the Tool Gateway from the GUI	2026-05-31 05:10:33 -04:00
shared	feat: move dashboard to apps/ so we can share ws proto	2026-05-02 13:38:49 -05:00