Last used model not preserved for the session #15

daut commented 2026年01月18日 11:42:33 +01:00

Hey, thanks for this awesome package. I've been testing it lately and it works great so far!

I noticed a minor behavior difference between opencode TUI and this package: the last used model is not preserved when resuming a session. It seems to always revert to the default model

Is this a bug, or did I miss a configuration option?

Thanks!

Hey, thanks for this awesome package. I've been testing it lately and it works great so far! I noticed a minor behavior difference between opencode TUI and this package: the last used model is not preserved when resuming a session. It seems to always revert to the default model Is this a bug, or did I miss a configuration option? Thanks!

sczi commented 2026年01月18日 21:27:37 +01:00

I just added restoring the last model used when you resume a session. I also changed the model setting to be per agent per session, as the TUI is, rather than just per session as I had it before, so now you can set a different model for build and plan mode easier.

I just added restoring the last model used when you resume a session. I also changed the model setting to be per agent per session, as the TUI is, rather than just per session as I had it before, so now you can set a different model for build and plan mode easier.

daut commented 2026年01月18日 22:46:54 +01:00

Thanks!

One more thing I've noticed is that the TUI selects the most recently used model as the default for a new session. I'm not sure if that's ideal default behavior, but it's something I've gotten used to. Maybe it's worth supporting, at least via an optional flag.

Thanks! One more thing I've noticed is that the TUI selects the most recently used model as the default for a new session. I'm not sure if that's ideal default behavior, but it's something I've gotten used to. Maybe it's worth supporting, at least via an optional flag.

sczi commented 2026年01月18日 23:13:07 +01:00

The way I have it right now, new sessions will inherit the agent/model settings of the buffer you spawn it from. So if you call opencode-new-session from some existing session buffer, it will get the same model settings.
When you call opencode-new-session from anywhere else, it will get the default settings, which the default model you have configured in opencode for a given agent, and if one isn't configured, then opencode-default-model which you can configure in emacs and we default to big pickle.

The way I have it right now, new sessions will inherit the agent/model settings of the buffer you spawn it from. So if you call `opencode-new-session` from some existing session buffer, it will get the same model settings. When you call `opencode-new-session` from anywhere else, it will get the default settings, which the default model you have [configured in opencode for a given agent](https://opencode.ai/docs/agents/#model), and if one isn't configured, then `opencode-default-model` which you can configure in emacs and we default to big pickle.

sczi commented 2026年01月18日 23:35:48 +01:00

I realized my previous commit was pretty incomplete, ie if you had a session where you set build agent to glm 4.7 and plan mode to minimax, and the last message was using plan mode, when you reopen the session, it would now set the model to minimax but in build mode, and plan mode would still have the default model. Now it actually restores whatever model was last used with each agent in a session, and sets the agent to the one from the last message.

I realized my previous commit was pretty incomplete, ie if you had a session where you set build agent to glm 4.7 and plan mode to minimax, and the last message was using plan mode, when you reopen the session, it would now set the model to minimax but in build mode, and plan mode would still have the default model. Now it actually restores whatever model was last used with each agent in a session, and sets the agent to the one from the last message.

daut commented 2026年01月19日 00:01:06 +01:00

@daut wrote in #15 (comment):

Thanks!

One more thing I've noticed is that the TUI selects the most recently used model as the default for a new session. I'm not sure if that's ideal default behavior, but it's something I've gotten used to. Maybe it's worth supporting, at least via an optional flag.

To clarify a bit: This is default behavior when no default model has been selected in opencode.json. If there is one, then the TUI behaves the same way opencode.el does. So maybe having the most recently used model as a fallback, before relying on opencode-default-model, would more closely match how the TUI behaves.

@daut wrote in https://codeberg.org/sczi/opencode.el/issues/15#issuecomment-9961785: > Thanks! > > One more thing I've noticed is that the TUI selects the most recently used model as the default for a new session. I'm not sure if that's ideal default behavior, but it's something I've gotten used to. Maybe it's worth supporting, at least via an optional flag. To clarify a bit: This is default behavior when no default model has been selected in `opencode.json`. If there is one, then the TUI behaves the same way `opencode.el` does. So maybe having the most recently used model as a fallback, before relying on `opencode-default-model`, would more closely match how the TUI behaves.

sczi commented 2026年01月19日 00:24:56 +01:00

Yea that'd probably be slightly nicer, then opencode-default-model would never be used except on the very first run, it'd always fallback to the most recently used model. So I could just get rid of opencode-default-model and users have one less thing to configure, and if they want the behavior of opencode-default-model then they can just configure that in opencode.json

Yea that'd probably be slightly nicer, then `opencode-default-model` would never be used except on the very first run, it'd always fallback to the most recently used model. So I could just get rid of `opencode-default-model` and users have one less thing to configure, and if they want the behavior of `opencode-default-model` then they can just configure that in `opencode.json`

sczi commented 2026年01月20日 00:04:12 +01:00

it should work like that now

it should work like that now

daut commented 2026年01月22日 23:17:06 +01:00

works smoothly now

works smoothly now