switch-provider

Switch OpenClaw AI providers between AWS Bedrock and MiniMax.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill switch-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switch-provider
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/openclaw/switch-provider
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill switch-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, docker.

What problem does it solve?

Manually updating OpenClaw's AI provider configuration across individual agents and team member containers is tedious and error-prone, especially when switching between AWS Bedrock and MiniMax for different testing or workflow needs.

Core Features & Use Cases

  • Dual Provider Support: Seamlessly switch between AWS Bedrock (Claude Opus, Sonnet models) and MiniMax (M2.5 model) for all OpenClaw instances.
  • Flexible Targeting: Update the provider for your current agent or any named team member container with a single command.
  • Automated Workflow: Automatically restarts team member containers after switching, and preserves existing provider configurations to avoid redundant setup.
  • Use Case: If you need to test a code generation workflow on MiniMax M2.5 for your team's code-expert container, this skill handles the config update and container restart without manual file editing.

Quick Start

Use the switch-provider skill to switch your current OpenClaw agent to use the AWS Bedrock AI provider.

Frequently Asked Questions about switch-provider

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch the AI provider for OpenClaw between AWS Bedrock and MiniMax?

Switching the OpenClaw AI provider between AWS Bedrock and MiniMax requires updating configuration files and setting up provider-specific credentials. This process can be automated to handle both the current user agent and named team member containers without manual file editing.

Can I update the AI provider configuration for a specific team member container in OpenClaw?

Yes, updating the AI provider configuration for a specific team member container in OpenClaw is supported. You can target named containers directly, which will automatically update their configuration and restart the container to apply the new provider settings.

Do I need Docker and Node.js to automate OpenClaw provider switching?

Yes, Docker and Node.js are required dependencies for automating OpenClaw provider switching. Docker manages and restarts team member containers, while Node.js executes the configuration updates for switching between AWS Bedrock and MiniMax providers.

What happens to existing provider configurations when I switch OpenClaw to MiniMax?

When switching OpenClaw to MiniMax, existing provider configurations are preserved to avoid redundant setup. The tool updates the necessary credentials and config files, then automatically restarts team member containers to apply the new provider settings.