Related GitHub Issue

Closes: #9208

Roo Code Task Context (Optional)

No Roo Code task context for this PR

Description

This PR fixes a bug where switching to an API Profile that keeps the same provider/model did not apply changed settings (e.g., headers, baseUrl, service tier, reasoning tokens/budget). Previously, the API client (task.api) was only rebuilt when provider or model changed.

Implementation details:

• Added an options parameter with forceRebuild to the helper that updates the task API client. Now explicit profile switch/save forces a rebuild to apply all non-model-affecting settings immediately.
• Invocations from explicit profile activation and profile save paths pass forceRebuild: true.
• Task.apiConfiguration is still fully synchronized with the selected profile.

Key changes:

• src/core/webview/ClineProvider.ts
  • Added forceRebuild option to updateTaskApiHandlerIfNeeded()
  • Force rebuild on:
    • upsertProviderProfile() activation path
    • activateProviderProfile() path
• Tests updated to reflect new behavior:
  • src/core/webview/tests/ClineProvider.apiHandlerRebuild.spec.ts

Why this approach:

• User-initiated profile switches or saves are explicit intent to use the new configuration. Rebuilding the client ensures runtime parameters (headers/baseUrl/tier/reasoning, etc.) take effect even when provider/model are unchanged.

Test Procedure

Automated tests:

• Run targeted spec:
  • cd src && npx vitest run core/webview/tests/ClineProvider.apiHandlerRebuild.spec.ts
• Run full suite:
  • cd src && npx vitest run

What’s covered:

• Rebuild occurs when provider/model unchanged but settings differ during explicit activation/save
• Rebuild still occurs when provider or model changes
• Task.apiConfiguration is fully synchronized on every switch

Observed results locally:

• Targeted: 1 file, all tests passed
• Full suite: all tests passed (skipped tests unchanged)

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).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

No UI changes in this PR

Documentation Updates

• No documentation updates are required.

Additional Notes

No additional notes

Get in Touch

@hannesrudolph