remove: Cleanup gemini cli leftovers

[roomote]

Remove leftover Gemini CLI code

[daniel-lxs]

@roomote-agent revert the change to the default case completely please, do not create a new PR

[roomote]

I understand. I will revert the change to the default case completely and push the changes to this same PR branch.

[roomote]

Done! I have reverted the default case in buildApiHandler back to its original state as requested. The change restores the original behavior:

default:
    apiProvider satisfies "gemini-cli" | undefined
    return new AnthropicHandler(options)

The modification has been pushed to this PR branch and CI checks are running. Local tests passed successfully.

[daniel-lxs]

@roomote-agent Now make it look like this:

default:
    return new AnthropicHandler(options)

Push to this PR, do not create a new one

[roomote]

I see the request to change the default case to return new AnthropicHandler(options). Let me check out the PR branch and make this change.

[roomote]

Done! ✅

I have simplified the default case in the buildApiHandler function as requested. The change removes the TypeScript satisfies check and now simply returns new AnthropicHandler(options).

Changes made:

• Modified src/api/index.ts lines 118-120
• Removed the apiProvider satisfies "gemini-cli" | undefined line
• Simplified to just return new AnthropicHandler(options)

Testing:

• All API tests passed successfully
• Linting and type checking completed without errors
• Changes have been pushed to this PR branch

The modification aligns with the PR's goal of cleaning up references to the removed gemini-cli provider.

[daniel-lxs]

LGTM

[daniel-lxs]

@roomote-agent make sure no errors occur if a user has a removed provider selected, make sure it fallback to the first provider in the list, do not create a new PR, push to this one

[roomote]

Hi @daniel-lxs! I see your request. I will implement the fallback logic to ensure that if a user has a removed provider (like gemini-cli) selected, it will gracefully fallback to the first available provider in the list. Working on this now and will push the changes to this PR branch.

[roomote]

@daniel-lxs I've implemented the fallback mechanism as requested! 🎯

Implementation Summary

I added validation logic to ensure users with removed providers (like "gemini-cli") are automatically switched to a valid provider:

Changes Made:

1. Webview Launch Validation (webviewMessageHandler.ts):

   • Added provider validation in the webviewDidLaunch handler
   • Checks if the current provider exists in the providerNames array
   • Automatically finds and activates the first configuration with a valid provider

2. Provider Activation Safeguard (ClineProvider.ts):

   • Modified activateProviderProfile to validate providers before activation
   • Implements recursive fallback if an invalid provider is detected
   • Shows a warning message to notify users when their provider is switched

3. Comprehensive Test Coverage (webviewMessageHandler.spec.ts):

   • Added tests for provider fallback scenarios
   • Covers edge cases like all providers being invalid
   • Ensures graceful handling when no valid providers exist

How It Works:

When a user with "gemini-cli" (or any removed provider) selected opens the extension:

1. The system detects the invalid provider
2. Searches for the first configuration with a valid provider
3. Automatically switches to that configuration
4. Displays a warning: "Provider 'gemini-cli' is no longer supported. Falling back to first available provider."

All tests are passing ✅ and the changes have been pushed to this PR branch as requested!