Tooling46d ago
Grok Build v1.0.35: Accurate MCP Handshake Status, Better /memory, Leaner Syntax Highlighting
Grok Build shipped v1.0.35 focused on MCP reliability, the /memory experience, and large-file performance: headless MCP status and connecting reminders now match real handshake state; tool searches/calls on the daemon path show query, results, arguments, and output; /memory gains content search, copy confirmations, narrow-terminal support, and faster deletes; syntax highlighting uses far less memory and runs faster on large TypeScript and other files.
Tooling47d ago
Grok Build v1.0.33: Structured MCP JSON, /memory Deletes, Long-Session Checkpoints Kept
Grok Build shipped v1.0.33 with stronger MCP, memory, and long-session reliability: MCP tool results can include structured JSON, cancel/timeout notifies the server to stop work, /memory supports two-press delete for real notes, and compaction checkpoints survive the 30-day cleanup so long agent workflows keep context. Elon Musk amplified the update.
Tooling1d ago
xAI will add an invisible watermark to Grok API text by default from Nov 7, covering grok-4.7 and six other models, with per-model admin opt-out
On Oct 31, xAI (signed as SpaceXSI in its docs) added an "Output Watermarking" page to its API docs: starting November 7, 2026, text generated by grok-4.7, grok-4.6, grok-4.5, grok-4.3, and the reasoning, non-reasoning, and multi-agent versions of grok-4.20 will carry an invisible watermark by default, to comply with the EU AI Act. It covers ordinary text, structured outputs, and tool call arguments on both the Responses and Chat Completions APIs, and works by slightly shaping token choice without adding any characters. Developers can read the x-watermark response header to check; team admins can opt out per model in the Console, but must confirm a legal exception applies, and some models may be locked on.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.