xAI has released the 1.0.14 update for Grok Build, which focuses on reliability. The initial release came on 31 August 2026, and rolled out to users over the following week.
The reliability changes focused on signed-in session refreshes, context hooking, and an updated sandbox mode where the CLI can be allowed to write to the disk. So far, this doesn’t bring any new breaking changes, such as the upcoming Grok 4.7, to Grok Build, but it does provide more reliability for developers working in the Build environment.
One of the most important changes is that an expired OIDC token used to kill the Grok Build session, terminating any task in progress. Now, token refresh is proactive for default, meaning that you’ll see less issues with login failures mid-task.
Hooks and Per-Turn Cost
PostToolUse hooks, including ones registered through the SDK, can now send feedback and context back to the model after a tool runs. That is how a team keeps the next turn informed by what the last tool actually did, instead of treating each call as a dead end.
grok usage <session-id> shows persisted per-turn token and cost data as well now, rather than just a session total. When the composer retries, the composer and the title show a short reason for the retry, so a stall is easier to read than a silent loop where it keeps retrying and failing, costing you tokens.
A few quieter reliability fixes sit in the same update as well. Subagent sessions no longer leak threads or file descriptors when the parent is busy. Compaction failures from context size degrade the input instead of retrying the same way. Failed task and todo tool calls stay in the transcript, and interjections during a turn are delivered atomically or not at all.
Strict Sandbox and Smaller Windows Builds
--sandbox strict now restricts writes to ~/.grok/sessions only. This helps to ensure anyone who wants the CLI working inside a session directory keeps it there, rather than letting it wander more widely on your machine.
In addition, thanks to some code optimizations, the Windows CLI is now about 70% smaller, using the same compressed sidecars as macOS and Linux. On a large repository, the first message no longer waits on a repository status scan, and startup fetches remote settings once per boot. Plus, a a signed-in warm start can use a local cache rather than having to fetch one again.
Models can declare a different identifier for each reasoning-effort level, and prompt suggestions follow remote configuration, defaulting to the current session model. grok inspect shows Claude bypass locks as advisory, not enforced.
Safe, Rollback Free Release
The 1.0.14 notes are in the Grok Build changelog and the matching JSON file, available online now. Every JSON item has breaking_change set to false, which means this specific update will not break a current install or cause any issues requiring a rollback.
