Configure Claude Code to work with multiple LLM providers (DeepSeek, z.ai/GLM, Kimi, OpenRouter) in PowerShell.

Open PowerShell and run:

Claude Code is a powerful command-line interface that allows developers to interact with Anthropic's Claude AI models for coding assistance. This guide provides two battle-tested methods to configure Claude Code to work with multiple LLM providers beyond just Anthropic, including models from DeepSeek, z.ai (GLM), Kimi, and OpenRouter.

This empowers you to switch between the best model for any given task without ever leaving your terminal. Two Approaches to Flexibility

• Shell Functions: A simple, lightweight, and robust method for switching providers before starting a session. Perfect for most use cases.

Zero to three parameters maximum, with related data grouped into USTRUCT types rather than passed as individual arguments.

Functions would be extremely small (2–4 lines ideally, never more than 20) with single responsibilities.

Blueprint-exposed functions (UFUNCTION) would especially benefit—complex parameter lists create unwieldy Blueprint nodes.

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

• feat: new feature
• fix(scope): bug in scope
• feat!: breaking change / feat(scope)!: rework API
• chore(deps): update dependencies

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries