Credential loss across processes fixed; MCP servers toggleable from CLI
v0.2.113
2 features5 enhancements12 fixesThis release2 featuresNew capabilities5 enhancementsImprovements to existing features12 fixesBug fixesAI-tallied from the release notes
From the original release noteView original ↗
- MCP servers can be enabled or disabled from the CLI with
grok mcp enable <name>andgrok mcp disable <name> - Full plan markdown can be copied to the clipboard with
yduring plan approval or preview - Automatic recovery from repetitive loops in model output is enabled by default
- Terminal command output is no longer lost or duplicated when the gateway is unreachable
- Invalid MCP server entries in
config.tomlno longer prevent Grok from starting; problems are shown ingrok inspect - SessionEnd hooks run on exit in non-leader TUI and headless sessions
- Paste chips display with the correct background in inline prompts and question inputs
- Background task status 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
/loopstores 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 - Background task status rows clear correctly after long foreground shell commands complete
- Agent subprocesses and idle inhibitors are 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 Delete 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 use far less memory and avoid spikes
- Limited the workspace daemon's worker threads to prevent thread exhaustion on high-core shared machines
Fetched August 1, 2026


