Provider Switch

Manage Agent/Provider combinations as named, independently validated packages. Prefer temporary profiles that preserve the agent's default configuration and login state.

Core Rules

• Verify current official documentation for both the agent and provider before changing files. Treat models, endpoints, CLI flags, schemas, and minimum versions as unstable.
• Inventory the current CLI version, config paths, login state, command resolution, and existing target files without printing secrets.
• Default to a temporary side-load, profile, or wrapper. Modify global defaults only when the user explicitly requests a persistent switch.
• Keep provider credentials separate from the agent's own account login. Never add global login-policy fields to a provider profile merely to send a provider API key.
• Preview all target files and behavioral effects before writing. Back up changed files, preserve existing non-placeholder secrets, and use atomic writes.
• After a successful interactive install, open a dedicated provider config when its credential placeholder still needs user input. Do not open it when a real credential is already present, and provide an opt-out for automation.
• Treat any bundled YOLO launcher as an explicit package contract: log mode=yolo, document that permissions and safety checks are bypassed, and never apply that mode to the agent's ordinary command or global settings.
• Keep Claude provider context guardrails explicit in dedicated settings: disable nonessential traffic and set the auto-compaction calculation window when the cataloged profile requires it. Use a settings-level effort default when native /model and /effort controls must remain available; do not lock those controls with the higher-precedence CLAUDE_CODE_EFFORT_LEVEL environment variable. Document the exact values, scope, and residual context-overflow risk.
• Log stable action names, targets, modes, and validation results. Never log credential values or authorization headers.
• Stop on unsupported protocols, invalid downloaded metadata, version incompatibility, or login-state regression. Do not add a silent compatibility fallback.

Workflow