Closed
Conversation
|
Important Review skippedToo many files! This PR contains 299 files, which is 149 over the limit of 150. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (299)
You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughAdds a new local Changes
Sequence DiagramsequenceDiagram
participant User
participant ProviderCmd as Provider Command
participant ProviderUtil as Provider Utility
participant Settings as Settings Store
participant ConfigApp as Config Applier
User->>ProviderCmd: invoke `provider` / `api` (arg)
ProviderCmd->>ProviderUtil: getAPIProvider()
ProviderUtil->>Settings: read getInitialSettings().modelType / env
Settings-->>ProviderUtil: return current provider
ProviderUtil-->>ProviderCmd: current provider
alt unset
ProviderCmd->>Settings: clear userSettings.modelType
ProviderCmd->>Settings: remove provider env toggles
ProviderCmd-->>User: confirm unset (env fallback)
else switch to provider
ProviderCmd->>Settings: set userSettings.modelType (or env toggle)
ProviderCmd->>ConfigApp: applyConfigEnvironmentVariables()
ConfigApp->>Settings: write env/config as needed
ConfigApp-->>ProviderCmd: applied
ProviderCmd-->>User: confirm new provider (or warn missing vars)
end
Estimated Code Review Effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
src/commands/provider.ts (2)
57-72: Consider blocking switch when required env vars are missing.When
OPENAI_API_KEYorOPENAI_BASE_URLis missing, the command still setsmodelType: 'openai'and returns. This leaves the system in a state where subsequent API calls will fail.Also note: the early return skips
applyConfigEnvironmentVariables()(line 85), so any provider-specific env vars fromsettings.envwon't be applied.♻️ Option: Apply config env vars before checking
if (arg === 'openai') { + // Apply settings.env first so user-configured vars are available + applyConfigEnvironmentVariables() const mergedEnv = getMergedEnv() const hasKey = !!mergedEnv.OPENAI_API_KEY const hasUrl = !!mergedEnv.OPENAI_BASE_URL if (!hasKey || !hasUrl) { updateSettingsForSource('userSettings', { modelType: 'openai' })🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/commands/provider.ts` around lines 57 - 72, The current logic in the provider switch (when arg === 'openai') sets updateSettingsForSource('userSettings', { modelType: 'openai' }) and returns even if getMergedEnv() is missing OPENAI_API_KEY or OPENAI_BASE_URL, leaving the app in a broken state and skipping applyConfigEnvironmentVariables(); fix by applying provider-specific config env vars first (call applyConfigEnvironmentVariables() before reading getMergedEnv()), then validate mergedEnv for OPENAI_API_KEY and OPENAI_BASE_URL and only call updateSettingsForSource('userSettings', { modelType: 'openai' }) if both are present; if missing, return the warning without changing settings and avoid the early return that prevents env application.
1-6: Usesrc/*path alias for imports.Per coding guidelines, TypeScript files should use
src/*path alias for imports.♻️ Suggested change
import type { Command } from '../commands.js' import type { LocalCommandCall } from '../types/command.js' -import { getAPIProvider } from '../utils/model/providers.js' -import { updateSettingsForSource } from '../utils/settings/settings.js' -import { getSettings_DEPRECATED } from '../utils/settings/settings.js' -import { applyConfigEnvironmentVariables } from '../utils/managedEnv.js' +import { getAPIProvider } from 'src/utils/model/providers.js' +import { updateSettingsForSource, getSettings_DEPRECATED } from 'src/utils/settings/settings.js' +import { applyConfigEnvironmentVariables } from 'src/utils/managedEnv.js'As per coding guidelines: "Use
src/*path alias for imports in TypeScript files".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/commands/provider.ts` around lines 1 - 6, Update the import statements in provider.ts to use the project path alias instead of relative paths: replace imports that bring in Command, LocalCommandCall, getAPIProvider, updateSettingsForSource, getSettings_DEPRECATED, and applyConfigEnvironmentVariables so they import from the corresponding "src/..." modules (e.g., src/commands, src/types/command, src/utils/model/providers, src/utils/settings/settings, src/utils/managedEnv) while preserving the same named symbols; this ensures TypeScript path-alias rules are followed without changing the imported identifiers or behavior.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/commands/provider.ts`:
- Around line 22-29: getMergedEnv currently spreads process.env
(Record<string,string|undefined>) into a Record<string,string> return which is a
type mismatch; either change getMergedEnv's signature to return
Record<string,string|undefined> to match process.env or ensure all merged values
are coerced/filtered to strings before returning (e.g., iterate merged and
convert undefined to '' or String(value), or remove keys with undefined). Update
the function body and its return type accordingly and keep references to
getMergedEnv and getSettings_DEPRECATED when making the change so callers/types
remain consistent.
- Around line 87-98: The branch that handles cloud providers is both deleting
global OpenAI env vars and mutating saved settings; change it to only remove the
CLAUDE_CODE_USE_OPENAI flag from process.env (do not delete OPENAI_API_KEY or
OPENAI_BASE_URL) and stop overwriting user settings via
updateSettingsForSource('userSettings', { modelType: 'anthropic' }); instead
leave settings.json untouched (or only set modelType when a validation error
forces a fallback, with clear comment/documentation). Ensure
applyConfigEnvironmentVariables() is still called so provider-specific envs are
applied, and update any log/comments to reflect that only CLAUDE_CODE_USE_OPENAI
is cleared and settings.json is not modified by the cloud-provider branch.
---
Nitpick comments:
In `@src/commands/provider.ts`:
- Around line 57-72: The current logic in the provider switch (when arg ===
'openai') sets updateSettingsForSource('userSettings', { modelType: 'openai' })
and returns even if getMergedEnv() is missing OPENAI_API_KEY or OPENAI_BASE_URL,
leaving the app in a broken state and skipping
applyConfigEnvironmentVariables(); fix by applying provider-specific config env
vars first (call applyConfigEnvironmentVariables() before reading
getMergedEnv()), then validate mergedEnv for OPENAI_API_KEY and OPENAI_BASE_URL
and only call updateSettingsForSource('userSettings', { modelType: 'openai' })
if both are present; if missing, return the warning without changing settings
and avoid the early return that prevents env application.
- Around line 1-6: Update the import statements in provider.ts to use the
project path alias instead of relative paths: replace imports that bring in
Command, LocalCommandCall, getAPIProvider, updateSettingsForSource,
getSettings_DEPRECATED, and applyConfigEnvironmentVariables so they import from
the corresponding "src/..." modules (e.g., src/commands, src/types/command,
src/utils/model/providers, src/utils/settings/settings, src/utils/managedEnv)
while preserving the same named symbols; this ensures TypeScript path-alias
rules are followed without changing the imported identifiers or behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1d8a510d-ee1a-420e-b583-0615d32c2e6e
📒 Files selected for processing (3)
src/commands.tssrc/commands/provider.tssrc/utils/model/providers.ts
Comment on lines
+22
to
+29
| function getMergedEnv(): Record<string, string> { | ||
| const settings = getSettings_DEPRECATED() | ||
| const merged = { ...process.env } | ||
| if (settings?.env) { | ||
| Object.assign(merged, settings.env) | ||
| } | ||
| return merged | ||
| } |
There was a problem hiding this comment.
Type mismatch: process.env values can be undefined.
process.env is Record<string, string | undefined>, but getMergedEnv returns Record<string, string>. This type assertion is incorrect and could mask runtime issues.
🛡️ Suggested fix
-function getMergedEnv(): Record<string, string> {
+function getMergedEnv(): Record<string, string | undefined> {
const settings = getSettings_DEPRECATED()
- const merged = { ...process.env }
+ const merged: Record<string, string | undefined> = { ...process.env }
if (settings?.env) {
Object.assign(merged, settings.env)
}
return merged
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| function getMergedEnv(): Record<string, string> { | |
| const settings = getSettings_DEPRECATED() | |
| const merged = { ...process.env } | |
| if (settings?.env) { | |
| Object.assign(merged, settings.env) | |
| } | |
| return merged | |
| } | |
| function getMergedEnv(): Record<string, string | undefined> { | |
| const settings = getSettings_DEPRECATED() | |
| const merged: Record<string, string | undefined> = { ...process.env } | |
| if (settings?.env) { | |
| Object.assign(merged, settings.env) | |
| } | |
| return merged | |
| } |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/commands/provider.ts` around lines 22 - 29, getMergedEnv currently
spreads process.env (Record<string,string|undefined>) into a
Record<string,string> return which is a type mismatch; either change
getMergedEnv's signature to return Record<string,string|undefined> to match
process.env or ensure all merged values are coerced/filtered to strings before
returning (e.g., iterate merged and convert undefined to '' or String(value), or
remove keys with undefined). Update the function body and its return type
accordingly and keep references to getMergedEnv and getSettings_DEPRECATED when
making the change so callers/types remain consistent.
There was a problem hiding this comment.
Actionable comments posted: 4
♻️ Duplicate comments (2)
src/commands/provider.ts (2)
22-29:⚠️ Potential issue | 🟡 MinorFix
getMergedEnvtyping; env values are nullable in TS.
process.envvalues arestring | undefined, so returningRecord<string, string>is unsound.🛠️ Proposed fix
-function getMergedEnv(): Record<string, string> { +function getMergedEnv(): Record<string, string | undefined> { const settings = getSettings_DEPRECATED() - const merged = { ...process.env } + const merged: Record<string, string | undefined> = { ...process.env } if (settings?.env) { Object.assign(merged, settings.env) } return merged }In TypeScript definitions for Node.js/Bun compatibility, what is the value type of `process.env` (`ProcessEnv`)?🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/commands/provider.ts` around lines 22 - 29, getMergedEnv currently declares a return type of Record<string, string> but copies from process.env whose values are string | undefined, which is unsound; change the function signature and internal typing to return Record<string, string | undefined> (or alternatively coerce/filter undefined values to strings if you want to guarantee no undefineds), update the merged variable to reflect ProcessEnv typing, and ensure any callers of getMergedEnv handle the string | undefined value; refer to getMergedEnv, getSettings_DEPRECATED, merged and process.env when making the change.
89-91:⚠️ Potential issue | 🟠 MajorDo not delete user OpenAI credentials when selecting cloud providers.
Removing
OPENAI_API_KEY/OPENAI_BASE_URLis destructive and can break other tooling in the same session.♻️ Proposed fix
delete process.env.CLAUDE_CODE_USE_OPENAI - delete process.env.OPENAI_API_KEY - delete process.env.OPENAI_BASE_URL process.env[getEnvVarForProvider(arg)] = '1'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/commands/provider.ts` around lines 89 - 91, The code currently deletes user OpenAI environment variables (process.env.OPENAI_API_KEY and process.env.OPENAI_BASE_URL) in provider selection; remove those delete calls and stop mutating global process.env in provider.ts (specifically the lines deleting CLAUDE_CODE_USE_OPENAI, OPENAI_API_KEY, OPENAI_BASE_URL). Instead, implement provider-specific overrides using local variables or a scoped config object (e.g., use a local const/openaiConfig or providerConfig passed into functions that need credentials) so other tools relying on OPENAI_* are not affected; if temporary overrides are required, set and restore them locally rather than permanently deleting them.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/commands/provider.ts`:
- Around line 62-71: The early-return branch that handles missing OpenAI env
vars leaves previous cloud-provider flags set, so
updateSettingsForSource('userSettings', { modelType: 'openai' }) should also
clear any cloud-specific toggles; modify the missing-env branch (the conditional
using hasKey/hasUrl) to call updateSettingsForSource with additional keys that
reset cloud providers (e.g., set bedrockEnabled/vertexEnabled/foundryEnabled or
equivalent flags to false or remove them) so the effective provider is truly
switched to OpenAI before returning the warning.
- Around line 42-43: The command currently calls
updateSettingsForSource('userSettings', ...) and other persistence helpers
without checking their returned { error }, so it may report success even when
persistence fails; update the command flow (where updateSettingsForSource is
called and the subsequent provider-specific env clearing calls at the other
occurrences) to capture the result, check for error/failed status, and
return/throw or log an appropriate failure message instead of proceeding to the
success text; ensure each call (e.g., updateSettingsForSource in the provider
command handler and the similar calls at the other locations) validates the
returned value and propagates the error to the user before printing success.
- Around line 1-6: Replace the relative imports at the top of this file with the
repository's TypeScript path alias imports (src/*); specifically import Command
and LocalCommandCall via "src/..." instead of '../commands.js' and
'../types/command.js', and replace getAPIProvider, updateSettingsForSource,
getSettings_DEPRECATED, and applyConfigEnvironmentVariables imports to use their
"src/..." module paths (e.g., "src/utils/model/providers",
"src/utils/settings/settings", "src/utils/managedEnv") so the file uses the
canonical src/* alias imports.
- Around line 77-86: The code currently deletes provider env toggles from
process.env and then calls applyConfigEnvironmentVariables(), which can
reintroduce those toggles; to fix, call applyConfigEnvironmentVariables() first,
then enforce the provider-specific env flags (delete
process.env.CLAUDE_CODE_USE_... or set the appropriate ones) after applying
config, and keep calling updateSettingsForSource('userSettings', { modelType:
arg }) as before; apply the same ordering change in the other branch that
handles the alternate provider (the block referenced around lines 92-95) so
config is applied first and provider flags are enforced last.
---
Duplicate comments:
In `@src/commands/provider.ts`:
- Around line 22-29: getMergedEnv currently declares a return type of
Record<string, string> but copies from process.env whose values are string |
undefined, which is unsound; change the function signature and internal typing
to return Record<string, string | undefined> (or alternatively coerce/filter
undefined values to strings if you want to guarantee no undefineds), update the
merged variable to reflect ProcessEnv typing, and ensure any callers of
getMergedEnv handle the string | undefined value; refer to getMergedEnv,
getSettings_DEPRECATED, merged and process.env when making the change.
- Around line 89-91: The code currently deletes user OpenAI environment
variables (process.env.OPENAI_API_KEY and process.env.OPENAI_BASE_URL) in
provider selection; remove those delete calls and stop mutating global
process.env in provider.ts (specifically the lines deleting
CLAUDE_CODE_USE_OPENAI, OPENAI_API_KEY, OPENAI_BASE_URL). Instead, implement
provider-specific overrides using local variables or a scoped config object
(e.g., use a local const/openaiConfig or providerConfig passed into functions
that need credentials) so other tools relying on OPENAI_* are not affected; if
temporary overrides are required, set and restore them locally rather than
permanently deleting them.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
Comment on lines
+1
to
+6
| import type { Command } from '../commands.js' | ||
| import type { LocalCommandCall } from '../types/command.js' | ||
| import { getAPIProvider } from '../utils/model/providers.js' | ||
| import { updateSettingsForSource } from '../utils/settings/settings.js' | ||
| import { getSettings_DEPRECATED } from '../utils/settings/settings.js' | ||
| import { applyConfigEnvironmentVariables } from '../utils/managedEnv.js' |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Use src/* alias imports in this TypeScript file.
These relative imports violate the repository import rule for TS files.
♻️ Proposed fix
-import type { Command } from '../commands.js'
-import type { LocalCommandCall } from '../types/command.js'
-import { getAPIProvider } from '../utils/model/providers.js'
-import { updateSettingsForSource } from '../utils/settings/settings.js'
-import { getSettings_DEPRECATED } from '../utils/settings/settings.js'
-import { applyConfigEnvironmentVariables } from '../utils/managedEnv.js'
+import type { Command } from 'src/commands.js'
+import type { LocalCommandCall } from 'src/types/command.js'
+import { getAPIProvider } from 'src/utils/model/providers.js'
+import { updateSettingsForSource } from 'src/utils/settings/settings.js'
+import { getSettings_DEPRECATED } from 'src/utils/settings/settings.js'
+import { applyConfigEnvironmentVariables } from 'src/utils/managedEnv.js'As per coding guidelines, "Use src/* path alias for imports in TypeScript files."
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| import type { Command } from '../commands.js' | |
| import type { LocalCommandCall } from '../types/command.js' | |
| import { getAPIProvider } from '../utils/model/providers.js' | |
| import { updateSettingsForSource } from '../utils/settings/settings.js' | |
| import { getSettings_DEPRECATED } from '../utils/settings/settings.js' | |
| import { applyConfigEnvironmentVariables } from '../utils/managedEnv.js' | |
| import type { Command } from 'src/commands.js' | |
| import type { LocalCommandCall } from 'src/types/command.js' | |
| import { getAPIProvider } from 'src/utils/model/providers.js' | |
| import { updateSettingsForSource } from 'src/utils/settings/settings.js' | |
| import { getSettings_DEPRECATED } from 'src/utils/settings/settings.js' | |
| import { applyConfigEnvironmentVariables } from 'src/utils/managedEnv.js' |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/commands/provider.ts` around lines 1 - 6, Replace the relative imports at
the top of this file with the repository's TypeScript path alias imports
(src/*); specifically import Command and LocalCommandCall via "src/..." instead
of '../commands.js' and '../types/command.js', and replace getAPIProvider,
updateSettingsForSource, getSettings_DEPRECATED, and
applyConfigEnvironmentVariables imports to use their "src/..." module paths
(e.g., "src/utils/model/providers", "src/utils/settings/settings",
"src/utils/managedEnv") so the file uses the canonical src/* alias imports.
Comment on lines
+42
to
+43
| updateSettingsForSource('userSettings', { modelType: undefined }) | ||
| // Also clear all provider-specific env vars to prevent conflicts |
There was a problem hiding this comment.
Handle updateSettingsForSource failures before returning success text.
All writes ignore { error }, so this command can report success even when persistence fails.
🛠️ Proposed fix pattern
- updateSettingsForSource('userSettings', { modelType: undefined })
+ const unsetResult = updateSettingsForSource('userSettings', {
+ modelType: undefined,
+ })
+ if (unsetResult.error) {
+ return {
+ type: 'text',
+ value: `Failed to clear API provider: ${unsetResult.error.message}`,
+ }
+ }Also applies to: 63-64, 83-85
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/commands/provider.ts` around lines 42 - 43, The command currently calls
updateSettingsForSource('userSettings', ...) and other persistence helpers
without checking their returned { error }, so it may report success even when
persistence fails; update the command flow (where updateSettingsForSource is
called and the subsequent provider-specific env clearing calls at the other
occurrences) to capture the result, check for error/failed status, and
return/throw or log an appropriate failure message instead of proceeding to the
success text; ensure each call (e.g., updateSettingsForSource in the provider
command handler and the similar calls at the other locations) validates the
returned value and propagates the error to the user before printing success.
Comment on lines
+62
to
+71
| if (!hasKey || !hasUrl) { | ||
| updateSettingsForSource('userSettings', { modelType: 'openai' }) | ||
| const missing = [] | ||
| if (!hasKey) missing.push('OPENAI_API_KEY') | ||
| if (!hasUrl) missing.push('OPENAI_BASE_URL') | ||
| return { | ||
| type: 'text', | ||
| value: `Switched to OpenAI provider.\nWarning: Missing env vars: ${missing.join(', ')}\nConfigure them via /login or set manually.`, | ||
| } | ||
| } |
There was a problem hiding this comment.
Clear cloud-provider toggles in the early OpenAI warning path.
When env vars are missing, this branch returns early and leaves prior cloud flags intact, which can keep the effective provider on bedrock/vertex/foundry.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/commands/provider.ts` around lines 62 - 71, The early-return branch that
handles missing OpenAI env vars leaves previous cloud-provider flags set, so
updateSettingsForSource('userSettings', { modelType: 'openai' }) should also
clear any cloud-specific toggles; modify the missing-env branch (the conditional
using hasKey/hasUrl) to call updateSettingsForSource with additional keys that
reset cloud providers (e.g., set bedrockEnabled/vertexEnabled/foundryEnabled or
equivalent flags to false or remove them) so the effective provider is truly
switched to OpenAI before returning the warning.
Comment on lines
+77
to
+86
| if (arg === 'anthropic' || arg === 'openai') { | ||
| // Clear any cloud provider env vars to avoid conflicts | ||
| delete process.env.CLAUDE_CODE_USE_BEDROCK | ||
| delete process.env.CLAUDE_CODE_USE_VERTEX | ||
| delete process.env.CLAUDE_CODE_USE_FOUNDRY | ||
| // Update settings.json | ||
| updateSettingsForSource('userSettings', { modelType: arg }) | ||
| // Ensure settings.env gets applied to process.env | ||
| applyConfigEnvironmentVariables() | ||
| return { type: 'text', value: `API provider set to ${arg}.` } |
There was a problem hiding this comment.
Provider env toggles can be overwritten by applyConfigEnvironmentVariables().
You mutate process.env and then call applyConfigEnvironmentVariables(), which reassigns env from config/settings and can reintroduce conflicting toggles. Apply config first, then enforce provider flags.
Also applies to: 92-95
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/commands/provider.ts` around lines 77 - 86, The code currently deletes
provider env toggles from process.env and then calls
applyConfigEnvironmentVariables(), which can reintroduce those toggles; to fix,
call applyConfigEnvironmentVariables() first, then enforce the provider-specific
env flags (delete process.env.CLAUDE_CODE_USE_... or set the appropriate ones)
after applying config, and keep calling updateSettingsForSource('userSettings',
{ modelType: arg }) as before; apply the same ordering change in the other
branch that handles the alternate provider (the block referenced around lines
92-95) so config is applied first and provider flags are enforced last.
Contributor
Author
|
神经claude code把项目代码全部格式化了一遍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
provider(alias:api) command to view, switch, or unset the active API provider (Anthropic, OpenAI, Bedrock, Vertex, Foundry).