Configure free-form Always-allow patterns and enforce MCP kill switch in Grok CLI
Grok Build 780d138 enforces the vendor-compat MCP kill switch, auto-approves read-only git queries, normalizes permission path globs, and adds a free-form Always-allow pattern editor. Update MCP policy and allowlists to match.
Why this loop
The release makes the vendor-compat MCP kill switch actually enforced when reported on, auto-approves read-only git queries while deferring writes to the classifier, and lexically normalizes permission path patterns before glob matching. The new free-form pattern editor on Always-allow lets you encode precise command allow rules instead of coarse approvals. Pager/plan UX also improves (Mermaid affordances in plan preview, clickable ▲ jump-to-top, Tab through ask_user_question). Teams should realign MCP kill-switch policy, rewrite Always-allow rules with normalized paths and free-form patterns, and use the plan/pager fixes in review workflows.
Proposed actions
- In Grok CLI, open the Always-allow command prompt and use the new free-form pattern editor to add explicit allow patterns for safe commands (e.g. git status*, git diff*, git log*, git show*)
- Enable the vendor-compat MCP kill switch in your Grok/MCP config, fully restart the CLI, and confirm blocked vendor-compat MCP servers no longer load when the switch is reported on
- Rewrite workspace permission path allow rules with lexically normalized paths (no .. segments or redundant separators) so they match the new normalize-before-glob behavior
- Start a plan-mode task that emits Mermaid, confirm Mermaid affordances appear in the plan preview, and use clickable ▲ to jump to the top of long responses while reviewing
- If using external providers, trigger sign-in once after an expired credential so you hit the sign-in flow (not a 401 loop); note auth refresh is now a single 7s attempt
Agent prompt
Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI costPaste into Claude Code / CLAUDE.md task
# DevAgentRadar → Claude Code You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features. ## Context Assistant: xAI Grok CLI (Grok Build) Proposal: Configure free-form Always-allow patterns and enforce MCP kill switch in Grok CLI Summary: Grok Build 780d138 enforces the vendor-compat MCP kill switch, auto-approves read-only git queries, normalizes permission path globs, and adds a free-form Always-allow pattern editor. Update MCP policy and allowlists to match. Primary source: https://github.com/xai-org/grok-build/commit/780d1388fff103ff0db0d8c14de65af6225b4860 ## Why it matters The release makes the vendor-compat MCP kill switch actually enforced when reported on, auto-approves read-only git queries while deferring writes to the classifier, and lexically normalizes permission path patterns before glob matching. The new free-form pattern editor on Always-allow lets you encode precise command allow rules instead of coarse approvals. Pager/plan UX also improves (Mermaid affordances in plan preview, clickable ▲ jump-to-top, Tab through ask_user_question). Teams should realign MCP kill-switch policy, rewrite Always-allow rules with normalized paths and free-form patterns, and use the plan/pager fixes in review workflows. ## Suggested actions 1. In Grok CLI, open the Always-allow command prompt and use the new free-form pattern editor to add explicit allow patterns for safe commands (e.g. git status*, git diff*, git log*, git show*) 2. Enable the vendor-compat MCP kill switch in your Grok/MCP config, fully restart the CLI, and confirm blocked vendor-compat MCP servers no longer load when the switch is reported on 3. Rewrite workspace permission path allow rules with lexically normalized paths (no .. segments or redundant separators) so they match the new normalize-before-glob behavior 4. Start a plan-mode task that emits Mermaid, confirm Mermaid affordances appear in the plan preview, and use clickable ▲ to jump to the top of long responses while reviewing 5. If using external providers, trigger sign-in once after an expired credential so you hit the sign-in flow (not a 401 loop); note auth refresh is now a single 7s attempt ## Your job 1. Restate the change in one sentence. 2. Propose a minimal plan for my repo (or a throwaway pilot). 3. Implement only what I approve; prefer small diffs and tests. 4. Call out risks (permissions, breaking APIs, cost). Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”Community signal · 0 approved · 0 deferred · 0 ignored
Anonymous public tally (one vote per visitor; changing choice updates your vote). Not moderated product truth.