Grok Build OSS 1.0.6 — optional pager status line, richer grok clone, Shift+arrow prompt selection, and a breaking change to how subagent tool access is configured.
Changelog
[changed]Subagent spawning no longer accepts capability_mode; tool access is controlled only by agent type.
[new]Optional status line at the bottom of the full-screen pager can show live session info (model, context, cost, cwd, and more) or the output of a configured script (user guide).
[new]grok clone can fetch a repo into a content store and mount a projected working tree.
[new]Shift+arrow keys extend text selections in the prompt like a standard text field.
[changed][ui] remember_tool_approvals now defaults to true, so per-command “Always allow” / “never allow” rows appear on permission prompts unless you turn them off.
[changed]Bash allow rules are conjunctive across chained segments: every segment must match an allow rule for the command to auto-approve; deny/ask still reject on any matching segment.
[fix] Session startup no longer hangs on large or unhealthy git repositories.
[fix] Queued messages during goals no longer starve; editing queued prompts works reliably.
[fix] First-launch consent notice shows clickable links and handles keyboard/mouse correctly; link handling is stricter across terminals.
[fix] Ctrl+C then edit a prompt correctly removes the original text from the conversation.
[fix] Double-clicking a terminal command result shows the complete output instead of a preview.
[fix] Video generation surfaces a clear ZDR error when output storage is required, instead of raw API responses.
[fix] Project hooks on Windows correctly expand $CLAUDE_PROJECT_DIR when invoking PowerShell scripts.
Agent & tools
Goal planner and verifier prompt templates treat objective-named external oracles (CI, remote pipelines, deployments) as gating bars: the remote system’s own verdict is required proof; a local re-run is supporting evidence only, and unreachable oracles should end unverifiable rather than silently substituting a local proxy.
Planner acceptance criteria must preserve the environment a result must hold in (CI, remote pipeline, deployment), not swap it for an easier local stand-in.
Status line support is wired through the pager and shell session path (built-in segments and command scripts with a stdin JSON contract).
Docs
New guide: Status Line (25-status-line.md) — built-in segments, command scripts, polling via refresh_interval, payload fields, and troubleshooting.
Configuration documents [ui.status_line] and the flipped default for remember_tool_approvals.
Permissions and Safety updates Bash rule matching (segment-level allow, normalization/wrappers) and per-command always-allow behavior.
User-guide index links the status line chapter.
Under the hood
New workspace crate xai-grok-status-line for status-line config and context.
Package versions advanced to 1.0.6 (xai-grok-pager, xai-grok-shell, xai-grok-version, and related bins).
New env knobs for connect UI timeout and workspace preview/dashboard behavior: GROK_CONNECT_UI_TIMEOUT_SECS, GROK_WORKSPACE_DASHBOARD, GROK_WORKSPACE_PREVIEW_DISCOVERY_REFRESH_MS, GROK_WORKSPACE_PREVIEW_STATE_WAIT_SECS.
Root Cargo.toml gains an admin-cli-dist size-optimized release profile (opt-level = "z", LTO, single codegen unit, strip).
Upgrade notes
If you spawn subagents with capability_mode, drop that parameter and rely on agent type for tool access.
Expect per-command “Always allow” rows on permission prompts unless you set remember_tool_approvals = false (or your org disables them in managed config).
Review Bash allow rules that assumed whole-string prefix matching on chains such as cmd1 && cmd2; each segment must now match an allow rule for rule-based auto-approval.
To enable the status line, set [ui.status_line] in ~/.grok/config.toml and restart; the row is full-pager only (not minimal mode).
