feat: Add variant cycle tooltip in session prompt
What does this PR do?
Add variant cycle tooltip in TUI prompt when model has variants available
How did you verify your code works?
Hey! Your PR title Add variant cycle tooltip in session prompt doesn't follow conventional commit format.
Please update it to start with one of:
-
feat:orfeat(scope):new feature -
fix:orfix(scope):bug fix -
docs:ordocs(scope):documentation changes -
chore:orchore(scope):maintenance tasks -
refactor:orrefactor(scope):code refactoring -
test:ortest(scope):adding or updating tests
Where scope is the package name (e.g., app, desktop, opencode).
See CONTRIBUTING.md for details.
The following comment was made by an LLM, it may be inaccurate:
No duplicate PRs found
You can just press ctrl + p and look for Variant cycle to see the keybind. There's no point in doing this except for UI bloat. I've seen the post on X, but people should really just RTFM.
You can just press
ctrl + pand look forVariant cycleto see the keybind. There's no point in doing this except for UI bloat. I've seen the post on X, but people should really just RTFM.
Variant is a new primitive that a lot of people aren't yet aware of, and lots of coding agents have a visible tool tip for thinking toggle so some people expect it.
Regarding the command palette, and speaking of ui bloat, I would be more inclined to add a command palette option to HIDE the thinking tool tip that is enabled by default. This will help new users find the keybind, and also satisfy people who complain about ui bloat.
Either way, the team can decide if they like the feature or not. I was mostly showing someone on twitter why opencode is cool- because they will review my PR in good faith, merge it if they like it, provide feedback if it needs improvement, or explain why they don't want to merge it.
+1 I changed my individual models with thinking token budgets into variants. I then struggled to find the former thinking levels because I didn't know the keyword in the interface would also be variants. I think at least for a little while showing this would help reduce confusion
Thanks for your contribution!
This PR doesn't have a linked issue. All PRs must reference an existing issue.
Please:
- Open an issue describing the bug/feature (if one doesn't exist)
- Add
Fixes #<number>orCloses #<number>to this PR description
See CONTRIBUTING.md for details.
implemented their own version in 1.1.15