feat: add manual thinking budget control for supported providers/models

[Ruakij]

Related GitHub Issue

Closes: #3008

Description

This PR introduces manual control for the "thinking token limit" if supported. Not setting it will use default handling by provider/model e.g. Gemini will then adjust the budget according to the request as their docs.
Support for this feature is determined by checking if modelInfo has modelMaxThinkingTokens. (from a quick glance, this seems to correlate with the only providers for which we support it currently: gemini and vertex)

Key changes:

• Added manualThinkingBudgetEnabled setting (defaults to false), which sets max thinking token limit to undefined when false, resulting it it not being added to the request.
• Migrate settings for existing profiles with modelMaxThinkingTokens already set (sets manualThinkingBudgetEnabled to true).
• Add Checkbox to enable manual control before the thinking tokens slider.
• Add Tests for UI

Test Procedure

1. Unit-Tests
2. Manual:
   • In provider settings, select a model with thinking support.
   • Default (Automatic Budget): "Manually control" checkbox is unchecked. Slider is hidden.
   • Manual Override: Check "Manually control". Slider appears. Set budget.
   • Unsupported Providers/Models (e.g. OpenRouter with sonnet 3.7 thinking): Checkbox is disabled.
   • Migration: Existing configs with modelMaxThinkingTokens should have manual control enabled.

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• [ x Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Unchecked:

Checked:

Disabled on OpenRouter:

Documentation Updates

• Yes, documentation updates are required.
  • Explain new "Manually control thinking token limit" setting, default automatic behavior, and manual override. (if exists)

Additional Notes

Get in Touch

Discord: ruakij

[Ruakij]

-.- Rework of reasoning was just merged, guess i need to adjust this for the rework

[hannesrudolph]

@Ruakij sorry about that!