Changing model in Settings doesn't update model on Agent Manager

[imanolmzd-svg]

Description

If I change a model in Settings, the sidebar chat is updated correctly, however AgentManager still uses the old model, even if I create a new worktree after the settings change.

AgentManager should update and use the latest model selected by the user in Settings. We should also check other settings are updated correctly.

If I restart the extension, AgentManager uses the selected model correctly.

Plugins

No response

Kilo version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[kilo-code-bot]

Root Cause Analysis

The issue has two layers:

1. Per-session model overrides persist after config change

When a worktree session is created via the Agent Manager (AgentManagerProvider.ts:1051, AgentManagerApp.tsx:1337), or when the user manually selects a model via the model selector (session.tsx:465), a per-session model override is stored in store.sessionOverrides[sessionID].

In session.tsx:432-440, the selected() memo checks sessionOverrides first:

const session = store.sessionOverrides[sid]
if (session) return session

This override never updates when config changes. When the user changes the model in Settings (modifying config.model), the global.config.updated SSE event fires and updates the config() signal in all webviews. But existing Agent Manager sessions with overrides continue using the old model because the override short-circuits before config-based resolution.

2. NewWorktreeDialog captures stale model from overridden session

In NewWorktreeDialog.tsx:80:

const [model, setModel] = createSignal(session.selected())

This captures session.selected() at dialog creation time. If the currently active session has a sessionOverride (from layer 1), the dialog pre-fills with the old model. When submitted, this stale model is passed to agentManager.createMultiVersion, which sets it as the override for new sessions — propagating the stale model to newly created worktrees.

Why the sidebar works

The sidebar doesn't set sessionOverrides during session creation (no setSessionModel call). Its selected() falls through to resolveModel() which reads config().model — this IS updated reactively via configUpdated.

Why restarting the extension fixes it

On restart, all sessionOverrides are cleared (in-memory only in the webview's SolidJS store), and fresh config is fetched.