[BUG] Export includes max token fields for unsupported models

[hannesrudolph]

Type

Bug

Problem

Exported settings include values for max output tokens and max thinking tokens even for models that do not support a reasoning budget or do not show these settings in the UI.

Context

• In the Settings UI, token sliders only appear for models that support a reasoning budget.
• When exporting settings, these fields still appear in the JSON for other models, which is misleading and can create invalid/unused configuration.

Reproduction

1. Configure multiple providers/models, including at least one that does not show the max token/thinking token sliders in the UI.
2. Export settings.
3. Open the exported JSON and inspect those models.

Expected result

Only models that support a reasoning budget (and where the user explicitly set values) include these fields.

Actual result

The export includes these fields for models that do not support them or were never set in the UI.

[roomote]

I'm exploring a potential fix for this issue where exported settings incorrectly include max token fields for models that don't support them. I'll open a PR to share progress.

[roomote]

I've opened PR #7946 with a fix for this issue: #7946

The fix modifies the settings export logic to exclude modelMaxTokens and modelMaxThinkingTokens fields when they are undefined, preventing them from appearing in exported settings for models that don't support reasoning budgets.

The implementation includes comprehensive test coverage to ensure the fix works correctly across different scenarios. Feedback welcome!

[daniel-lxs]

#7946 (comment)