opencode-models-providers

To validate provider and model configurations, prompt an AI to verify your current settings against OpenCode and provider documentation, adjusting defaults and compatibility constraints to align with the authoritative docs.

Configuration drift occurs when provider settings misalign with upstream documentation. Validating compatibility during provider changes or model migrations prevents this drift and ensures correct integration behavior.

Update OpenCode defaults and validation rules when adding or changing providers and models, or modifying authentication and environment variables, ensuring current settings reflect upstream provider guidance.

Yes, you can check model compatibility constraints during a model migration by validating configurations against authoritative provider docs to enforce compatibility checks and update defaults where necessary.

The best way to align authentication and environment variables is to validate provider configurations against upstream docs during updates, enforcing compatibility constraints and documenting findings for ongoing governance.