Grok 4.7 is xAI's new flagship. Same price, and the upgrade case is self-verification on long tasks.
xAI released Grok 4.7 on 21 September 2026 as the model it now recommends for coding and knowledge work, built on a new, larger base model with a longer reinforcement-learning run weighted toward problems that take hours to complete. Access, headline pricing and the context window match Grok 4.6, so the case for moving rests on whether the deeper reasoning and self-verification claims hold on your own long-running task.
What changed
xAI released Grok 4.7 on 21 September 2026 through the xAI API, Grok Build, Cursor, third-party coding harnesses, and model routers and cloud platforms, and its model catalogue now recommends 4.7 for coding and chat, calling it the most capable model it has built. It uses a new, larger base model and a longer reinforcement learning run on a harder mix of tasks weighted toward problems that take many hours to complete, and xAI says it is better at verifying its own work and managing longer context than Grok 4.6. Access, the headline input and output prices, cached-input pricing and the 500,000-token context window are unchanged from Grok 4.6; it carries a May 2026 knowledge cutoff, and a faster variant is available at double the price. Grok 4.6 remains listed and available with its original pricing and limits.
Why it matters
A newer model number invites an automatic upgrade, but the price per token and the tools it reaches are unchanged from 4.6. The case for moving is narrower and more testable than the launch suggests: it rests on whether the longer reasoning and self-verification gains actually show up on your own long-running task, since nothing about cost or access changed.

Bit’s takeaway
The human take
A person decides whether the longer reasoning and self-verification claims actually change the accepted result on a task that matters, and reads the real bill before migrating off a working 4.6 setup.

Turn this into a workflow
Do not just read the change. Try it safely.
Bit starts from this reviewed update and helps you build a safe way to use it on your own work: what AI can prepare, what you still check, and where the workflow should stop.
Turn this into a safe workflow with BitSources and method