Grok✓ ReviewedAnnounced 5 August 2026Reviewed 17 October 2026Grok's voice default is changing under your integrations.
Reviewed editorial Update
Grok's voice default is changing under your integrations.
xAI moved Grok’s latest voice alias to Voice 3.0 on 14 October 2026. Integrations using that alias change models without a code change.
What changed
The official API release notes record Voice 3.0 on 14 October 2026 and deprecate Voice 2.0. The grok-voice-latest alias now routes to grok-voice-3.0. Check a pinned model separately rather than assuming it follows the alias.
Why it matters
The interesting part is not the voice model, it is the alias: 'latest' means your product's behaviour changes on the provider's schedule, not yours. Voice tone, pacing and interpretation quietly shifting under a customer-facing product is a change nobody reviewed.
Bit’s takeaway
The human take
A person chooses when the product underneath their product is allowed to change, and tests the change on their own schedule.
Turn this into a workflow
Bring your task to Bit.
Bit reevaluates the recorded facts when you ask. Historical recommendations do not approve a current action.
Ask Bit about my taskSource-backed facts
- The xAI developer release notes state that grok-voice-latest routes to grok-voice-3.0 from 14 October 2026. Voice 2.0 is deprecated; this is a developer API change, not evidence of a particular consumer app voice model.Reviewed
Technical record
[grok-voice-2-fact; official_fact; product_fact; reviewed 2026-10-17; sources: xAI developer release notes (https://docs.x.ai/developers/release-notes); xAI developer documentation (https://docs.x.ai/developers/models)] The xAI developer release notes state that grok-voice-latest routes to grok-voice-3.0 from 14 October 2026. Voice 2.0 is deprecated; this is a developer API change, not evidence of a particular consumer app voice model.
Sources and method