← AI PulseAug 20, 2026

Wire · news · Single-source brief

Grok Build TUI Introduces Modes and Slash Commands

The Grok Build Terminal User Interface (TUI) now incorporates various modes and slash commands to manage session behavior and tool permissions.

By Illumora Editorial

Source · Aug 20, 2026, 3:13 PM · On Illumora · Aug 20, 2026, 3:48 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — Modes and Commands | SpaceXAI Docs
Save

The Grok Build Terminal User Interface (TUI) has introduced new modes and slash commands. These features aim to provide users with more control over session management, tool execution, and planning within the environment.

Key Points

  • The Grok Build TUI includes pager-local slash commands and commands from xai-grok-shell.
  • User-invocable skills are accessible as slash commands, such as /<skill-name>.
  • Plan mode allows editing only the session plan file until approved, entered via /plan [description] or Shift+Tab.
  • Auto mode uses a classifier to auto-approve safe tools, toggled with /auto or Shift+Tab.
  • Always-approve mode bypasses permission prompts for tool calls, activated with /always-approve, Shift+Tab, or grok --always-approve.
  • The command palette organizes session, context, model, and tool actions.
  • The /context command checks current context usage.

Context

According to xAI Docs, the Grok Build TUI's modes and commands are designed to streamline interactions and provide granular control over the development workflow. These functionalities are part of a broader set of features detailed in the documentation, including various API integrations, new voice capabilities, and advanced API usage options.

Why It Matters

These new modes and commands offer builders more direct control over how Grok executes tasks and interacts with tools. This could lead to more predictable and efficient development cycles, particularly when managing complex projects or sensitive operations.

What To Do

  • Review the Grok Build documentation for a full key reference on keyboard shortcuts.
  • Experiment with Plan mode using /plan [description] to manage session planning.
  • Test Auto mode and Always-approve mode to understand their impact on tool permissions.
  • Use /context to monitor resource usage during development.

Keep Exploring

/techniques/direct-blocks-**grok**