Description
In the TUI, switching between conversations can silently change a conversation's model. Open conversation A (recorded on model X), then conversation B (recorded on model Y), then return to A: the prompt now selects Y, and the next message in A goes to Y's provider. A's earlier messages still show X, so nothing signals the switch. Restarting the TUI clears it.
It happens when the first model stored for the agent in that launch comes from opening a conversation, which is the normal case when you open an existing conversation before picking a model.
Plugins
None
OpenCode version
altimate-code v0.12.3
Steps to reproduce
- With two providers available, create one conversation on each, e.g.
altimate run -m <provider>/<model> "A" and altimate run -m altimate-free/altimate-base "B".
- Launch the TUI. Before picking any model, open conversation A from the session list (
ctrl+x l). The prompt shows A's model.
- Open conversation B. The prompt shows B's model.
- Open conversation A again. The prompt shows B's model, while A's messages still show A's model.
Screenshot and/or share link
No response
Operating System
Linux (WSL2)
Terminal
tmux
Description
In the TUI, switching between conversations can silently change a conversation's model. Open conversation A (recorded on model X), then conversation B (recorded on model Y), then return to A: the prompt now selects Y, and the next message in A goes to Y's provider. A's earlier messages still show X, so nothing signals the switch. Restarting the TUI clears it.
It happens when the first model stored for the agent in that launch comes from opening a conversation, which is the normal case when you open an existing conversation before picking a model.
Plugins
None
OpenCode version
altimate-code v0.12.3
Steps to reproduce
altimate run -m <provider>/<model> "A"andaltimate run -m altimate-free/altimate-base "B".ctrl+x l). The prompt shows A's model.Screenshot and/or share link
No response
Operating System
Linux (WSL2)
Terminal
tmux