A running turn in Grok Build leaves you two awkward options: queue a correction behind it and wait, or cancel and lose the work in flight. This week adds a middle path, a steer mode where your prompt is picked up at the next step. Around it sit changes to session search, hook trust, worktree approvals and permission checks that are worth a look before you update a shared setup.
Week 43 (October 19-23, 2026) brought seven releases, 1.0.64 to 1.0.70, with 54 changelog entries. The follow-up controls are the headline. The rest is mostly search, trust and permissions.
Steer a running turn instead of queuing behind it
The default stays queue. Enter still queues your prompt until the turn finishes. The new follow_up_behavior setting changes that. Set it to steer under [ui] in config.toml, or change Follow-up behavior in /settings, and Enter makes the running turn pick up your queued prompt at its next tool or model step.
Send now cancels and sends. Ctrl+Enter or Ctrl+I cancels the running turn and sends the prompt right away. Use it when the turn is heading the wrong way and waiting for the next step is too slow. Two further cases follow from this:
- While the turn waits on a subagent or a background command and nothing else is queued, Enter acts as send now.
- With an empty prompt and a queued follow-up, Enter or send now cancels the turn and sends the top queued follow-up, unless that follow-up cannot be sent right now.
Slash commands behave differently. Sent with send now or Enter, a built-in slash command does not cancel the turn. Most run immediately, and those the agent runs, such as /compact, are queued. Prompt-like commands are different: send now on /goal, /deep-research, a skill such as /create-workflow, or a saved workflow run as /<name> cancels the turn like any other prompt. During /goal itself, a prompt or follow-up steers the goal instead of cancelling the turn.
Esc no longer cancels. It never cancels the turn and only shows a hint to press Ctrl+C. A stray Esc is now harmless.
Stash a half-written prompt. Ctrl+S or Alt+S stashes the prompt, and pressing it again on an empty prompt restores the stash. That helps when you start typing a follow-up and then need to send something else first.
Terminal conditions. Some terminals cannot send Ctrl+Enter or Ctrl+I as distinct keys. There, send now is Ctrl+O in the prompt and the prompt queue. In other contexts Ctrl+O toggles always-approve, so check the Terminal differences section of the keyboard shortcuts page for your terminal. The docs for Apple Terminal no longer list Ctrl+O as the interject chord and point to that same section for the send-now chord.
Changes for everyday work
/resume finds far more. Search now reaches sessions from other folders, tolerates typos, and matches the commands, file paths and replies inside a session, not just titles. Older sessions load when you reach the last row, with a count of how many are loaded. On the dashboard, /resume lists sessions from every folder, with the current folder and its checkouts first. Details are in the sessions documentation.
Untrusted folders run only managed hooks (breaking). In an untrusted folder, only your organization’s managed hooks run. User, project, plugin and agent hooks wait until you trust the folder. Headless sessions treat user hooks as trusted. If a hook of yours suddenly stops firing in a fresh checkout, trust is the first thing to check. See hooks.
Worktrees inherit ‘always allow’. A worktree now also uses the main checkout’s saved ‘always allow’ answers, so you are not asked again for a tool you already allowed there. To turn this off, set [features] worktree_inherits_main_approvals = false. The main checkout’s ‘never allow’ answers apply either way. Worktree create and fork also list files that could not be copied and any mode changes that were lost. More in the worktrees documentation.
Auto mode is stricter about shell commands. It runs a shell command without review only when every command in it matches an allowlist entry. Anything else asks first. Permission rules now read each word the way bash passes it to the program. The permissions documentation has the rules.
Subagents are on by default. The GROK_SUBAGENTS default changed from 0 to 1, so subagents and the task tool are enabled out of the box. The enabled master switch under [subagents] in the config file also defaults to on. To keep them off, set it explicitly. The settings reference lists both.
Technical notes
Keys and vim mode. Vim navigation is now one setting, [keys] vim with the values off or nav, also set with /vim-mode. The older [ui] vim_mode still works. Prompt suggestions follow vim mode: Tab moves focus to the scrollback, → or Ctrl+→ accepts, and Esc dismisses. Up arrow on an empty prompt focuses the prompt queue if it has entries, otherwise it browses history, and /history searches it. New shortcuts: Shift+J and Shift+K step turns from the top of the view, Ctrl+R toggles mouse capture when mouse_reporting_toggle is on, and Ctrl+4 toggles the prompt queue on a local Mac.
Dashboard. Directory grouping now shows a header with the folder path and agent count above each folder’s agents.
Speed. @ file completion shows results about 5 ms after you type instead of about 40 ms. Quitting is faster too: Grok no longer waits out fixed intervals, and the session-end Stop hook runs alongside SessionEnd hooks with a 1.5 second cap. Hooks that need longer than that at exit are worth a second look.
Config and flags. GROK_DISABLE_EXPERIMENTS turns off every [[experiments]] entry, and [experiments] enabled = false in any config file does the same. --permission-mode plan now starts the session in plan mode, as documented. A new enterprise release channel joins stable and alpha under [cli] channel.
Telemetry gotcha. DISABLE_TELEMETRY and DISABLE_ERROR_REPORTING turn things off for any non-empty value, including 0 and false. Setting DISABLE_TELEMETRY=0 therefore disables telemetry (a counterintuitive reading, but that is how it works).
Retired setting. [ui] simple_mode is retired and has no effect. grok doctor and /doctor flag it, along with any leftover [ui] vim_mode key.
What to take away
If you work in the terminal:
- Try
follow_up_behavior = "steer"for a few sessions and see whether Enter picking up your prompt at the next step suits you better than queuing. - Learn send now (
Ctrl+EnterorCtrl+I) and the stash (Ctrl+SorAlt+S). - If your terminal cannot send those keys distinctly, look up its chord under Terminal differences.
- Move vim settings to
[keys] vim, and run/doctorto catch the retired[ui] simple_modeand leftover[ui] vim_modekeys.
If you run parallel sessions:
- Use
/resumesearch with a half-remembered file path or command, and check the dashboard listing across folders. - Check whether worktrees now skip prompts you previously answered in the main checkout. If you would rather keep them separate, set
worktree_inherits_main_approvals = false. - Expect subagents and the task tool to be available by default.
If you administer integrations and company deployments:
- Audit which hooks are managed and which are user, project, plugin or agent hooks, because only managed ones run in untrusted folders now.
- Review your allowlists, since auto mode runs a shell command unreviewed only when every command in it matches an entry.
- Decide whether subagents should stay on, and set
GROK_SUBAGENTSor[subagents] enabledexplicitly if not. - Check any telemetry opt-out that sets
DISABLE_TELEMETRYorDISABLE_ERROR_REPORTINGto0orfalse, because those now disable. - Note the new
enterprisechannel under[cli] channel.
Sources: the Grok Build changelog, versions 1.0.64 to 1.0.70 (October 19-23, 2026), and the Grok Build documentation. The follow-up controls, subagent defaults and some shortcuts are described in the documentation without a version number, and availability of newer features may change.
