SpaceXAI trained Grok 4.6 on something most AI labs throw away

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

SpaceXAI released Grok 4.6 on Wednesday, less than a month after Grok 4.5. The company says Grok 4.6 can research unfamiliar topics, work its way through large codebases and turn a product idea into a functioning app. SpaceXAI also found that it checked its work more often on longer tasks, although those results haven’t been independently verified.

But Grok 4.6’s training reflects a shift in the coding-model race. Producing the right code on the first try still matters, but so does catching mistakes, fixing them and continuing without losing sight of the original task.

Producing the right code on the first try still matters, but so does catching mistakes, fixing them and continuing without losing sight of the original task.

How agents learn failure

SpaceXAI subjected Grok 4.6 to a longer supplemental training run than its predecessor, combining model-generated reasoning and technical material with engineering data. The optimizer and training recipe used to update the model’s weights were also changed. It then used Grok 4.5 to regenerate supervised fine-tuning trajectories spanning different reasoning settings, agent harnesses and domains including STEM, software engineering and knowledge work. Problematic trajectories were removed using model-based checks.

Reinforcement learning extended that work into general coding, kernel optimization, web development and computer-aided design. The model was rewarded for completing the larger task rather than simply drafting a plausible block of code.

SpaceXAI says Grok 4.6 became more likely to pause during longer tasks and check …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/grok-4-6-agent-training/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.