v0.2.113

stable

Published Jul 28, 2026

NEW11FIX6BREAKING3SECURITY2PERF1

Trailer

MCP servers can now be enabled or disabled directly from the CLI with grok mcp enable <name> and grok mcp disable <name>.
Full plan markdown can now be copied to the clipboard with y during plan approval or preview.
Added support for the new SuperGrok Plus subscription tier in authentication and feature gating.
Enabled automatic recovery from repetitive loops in model output by default.

Terminal command output is no longer lost or duplicated when the gateway is unreachable.
Invalid MCP server entries in config.toml no longer prevent Grok from starting; problems are shown in grok inspect.
SessionEnd hooks now run on exit in non-leader TUI and headless sessions.
Paste chips now display with the correct background in inline prompts and question inputs.
Pasted content chips now behave consistently when editing answers in the question view.
Background task status now shows only elapsed duration instead of absolute timestamps.
Session lists no longer drop real sessions when the remote registry reports an outdated turn count of zero.
/loop now stores prompts that include stop conditions so recurring tasks can terminate themselves when done.
Reduced spurious warning messages for common auth and config scenarios.
Fixed conda activation (and other sourced scripts that read $@) when using persistent or login-capture shells.
Fixed stuck background-task tray rows after long foreground shell commands complete.
Agent subprocesses and idle inhibitors are now cleaned up when the parent CLI process dies unexpectedly.
Fixed truncated plans in minimal mode and improved visual separation between reasoning and output (including NO_COLOR).
Fixed credential loss across multiple grok processes sharing the same auth file.
Fixed doubled Enter and other keys on older Alacritty terminals.
Fixed false paywall messages for free-tier and unmatched users.

Cold start shows the UI instantly while models and settings load in the background.
Large session forks and resumes now use far less memory and avoid spikes.
Prevented thread exhaustion on high-core shared machines by limiting the workspace daemon's worker threads.