Fix model selection not showing in resumed sessions in Agent Manager #5315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the issue where the model selection dropdown was not showing in resumed sessions in the Agent Manager.
Root Causes
Issue 1: Backend - Model not passed when resuming sessions
The
resumeSessionmethod inAgentManagerProvider.tswasn't passing themodeltospawnAgentWithCommonSetup, so when a session was resumed, the model information was lost.Issue 2: Frontend - Remote sessions missing model field
The webview's
RemoteSessioninterface was missing thelast_modelfield that comes from the API. When selecting a remote session (before resuming), the model selector couldn't display the model because the field wasn't being mapped.Changes
src/core/kilocode/agent-manager/AgentManagerProvider.tsmodel: session.modelto the parallel mode (worktree) resume pathmodel: session?.modelto the non-parallel mode resume pathwebview-ui/src/kilocode/agent-manager/state/atoms/sessions.tslast_model?: string | nullto theRemoteSessioninterfacetoAgentSessionto mapremote.last_modeltomodelTesting