Repository navigation
v2.3.4
Patch release — two Settings fixes that complete the Gemini-agent enablement path.
Fixes
- #937 — Changing an agent's Command in Settings reset the model (#931) but not
mcp_inject, so converting an agent to Gemini left a stale"flag"and the CLI crashed on launch (spawned with--mcp-config, which Gemini doesn't accept). Command-change andsave()now reconcilemcp_injectfrom the command, and the backend→mode mapping is centralized in a new sharedsrc/lib/injectMode.js(wizard, add-project route, and spawn default all use it). This is the fix that makes a Gemini agent actually enablable from the UI. (PR #938) - #935 —
SettingsPage.save()now runs the butler model throughsanitizeModel, so an invalid butler model (hand-edited / never command-changed) no longer re-persists. (PR #936)
Context
Builds on the Gemini integration shipped in v2.3.3 (#931 provider-aware model dropdown, #932 chat_read fix). With #937, the full "switch a team slot to command: gemini in Settings" flow works end to end.