SpaceXAI Releases Grok 4.6
SpaceXAI has announced the launch of the new Grok 4.6 model, showcasing significant performance improvements while maintaining the same pricing. Grok 4.7 is expected to follow soon with even greater capabilities.
SpaceXAI Releases Grok 4.6
SpaceXAI has announced the release of the new Grok 4.6 model, which demonstrates a significant performance increase while keeping the price at $2/$6 per million tokens.
The model has been fine-tuned on 1.5 trillion tokens used in Grok 4.5 and has received a notably improved post-training.
In celebration of the launch, Grok Build and Cursor have doubled the limits on this model for one week. It is expected that in a few weeks, Grok 4.7 will be introduced with 2 trillion parameters, promising even greater performance gains compared to 4.6.
Why it matters
AnalysisThis is important as new AI models like Grok 4.6 can significantly enhance data processing efficiency and reduce costs for users. The increase in parameters in new versions also opens up new possibilities for developers.
Discuss in community
Share your questions and insights with developers
Related in Ecosystem
Practical guides, core terminology, and agent skills
JSON — Structured Data for Programs, APIs, and AI Agents
A complete hands-on guide to JSON: syntax specifications, serialization via parse and stringify, REST API consumption, JSON Schema validation, and structured outputs for LLMs.
DOCX and XLSX Formats: When AI Needs to Deliver Production-Ready Documents
A comprehensive hands-on guide to generating and processing DOCX documents and XLSX workbooks with AI: comparing against Markdown and CSV, prompt engineering, formula design, and code automation.
Binance publishes investigation into $6.3 billion theft
Binance’s investigation links the theft to a modified Homebrew download, a fake interview and abuse of an internal AI tool.
Reddit user explains why Claude Code weekly limits are burning almost 4x faster
A Reddit user compared token usage across two weeks and found that each 1% of Claude Code's weekly limit now yields far fewer output tokens, pointing to subagents, reasoning time, and UI refresh requests as likely causes.