Command Models And Versioning

Production /v2/chat calls omit the model field and rely on an account default, so behavior shifts when the default Command model changes.

Always pass an explicit model id (e.g., a Command-R / Command-R+ / Command-A family id) so behavior is reproducible. Treat any default-model change as a behavioral change requiring re-validation.

Code written for a tool-use-capable Command model is pointed at a smaller model that handles the feature differently, and tool calls silently degrade.

Verify the selected model supports the features the workflow relies on (tool use, long context, multilingual) before swapping; capabilities differ across the Command family. Re-test the feature path on any model change rather than assuming parity.

An integrator pins only the family alias (e.g., 'command-r') and is surprised when an updated snapshot changes outputs for the same prompts.

Pin to a specific dated/versioned model snapshot where available so outputs are stable across the model's update cadence; migrate deliberately after regression testing. The family alias tracks the latest snapshot and will drift.