Grok · 5 min read

The @ file picker now reaches outside your workspace, and chips are editable

Typing an @ path that starts with /, ~/ or ../ now lists files from that folder, and picked files can be edited in place. The week also brings Shift+Enter in more terminals, full Vim editing in the prompt and clearer Auto-review cards.

Key takeaways 5
  • An @ path starting with /, ~/ or ../ lists files from that folder; set [ui] at_picker_outside_workspace = false to turn it off.
  • Picked @ files are editable in place, and @ mentions accept :N line suffixes and @!hidden files.
  • Shift+Enter inserts a newline in VS Code and other xterm.js terminals, and the new [ui] kitty_keyboard = 'query' setting covers terminals Grok can't identify.
  • /vim-mode all turns on full Vim editing in the agent prompt.
  • Copy buttons on /btw answers and quotes, Ctrl+L quoting from the scrollback and Auto-review explanations on shell approval cards (Ctrl+F) round out the TUI changes.

Anyone who works across several folders knows the friction: the file you want to mention sits one directory up, or in your home folder, and the prompt only sees the workspace. Once you pick a file, a typo in its path means deleting the whole mention and starting over. This week addresses both with an @ picker that reaches outside the workspace and file chips you can edit in place. Alongside it come Shift+Enter in more terminals, full Vim editing in the prompt, easier copying and quoting from the transcript, and shell approval cards that explain what Auto-review decided.

This update covers Week 45 (November 2-8, 2026): versions 1.0.74 to 1.0.79, six releases and 118 changelog entries. Most of the weight sits in the TUI, with a smaller permissions change at the end.


The @ picker now leaves the workspace, and chips can be edited

Folders outside the workspace are listed. An @ path that starts with /, ~/ or ../ now lists files from that folder (1.0.74). Type @~/ and you browse your home folder. Type @../ and you see the parent directory. Typed @~/ paths resolve to the home folder (1.0.78).

One setting switches it off. If you want the picker to stay inside the workspace, set [ui] at_picker_outside_workspace = false. The entry describes the new behavior as the default, so the setting is the place to look if you want the old one back. The settings reference lists it.

Picked files are editable in place. Once you pick a file, it no longer has to be deleted and retyped when the path is slightly off. In 1.0.74, Backspace at the end of a picked file reopens the picker on its path. Left or Right puts the cursor inside the chip so you can change the path directly. Version 1.0.78 repeats the in-place editing for @ file chips, so expect it to work consistently from that release on.

More precise mentions. @ mentions now accept :N line suffixes and @!hidden files (1.0.78). That lets you point at a specific line and reach hidden files from the picker.

Conditions.

  • Outside-workspace listing arrived in 1.0.74 and is on by default; [ui] at_picker_outside_workspace = false disables it.
  • In-place chip editing arrived in 1.0.74 and was extended in 1.0.78; :N suffixes and @!hidden files need 1.0.78.
  • The changelog entries do not list plan restrictions or usage limits for any of this.

Changes for everyday work

Shift+Enter works in more terminals. In 1.0.74, Shift+Enter inserts a newline in VS Code and other xterm.js-based terminals that use the Kitty keyboard protocol. For terminals Grok can’t identify, 1.0.77 adds [ui] kitty_keyboard = 'query', which makes Shift+Enter insert newlines there as well. If Shift+Enter submitted your half-written prompt before, try that setting first. More details are on the terminal support page.

Full Vim editing in the prompt. /vim-mode all enables full Vim editing inside the agent prompt (1.0.79). It is listed with the other slash commands in modes and commands.

Copying and quoting from the transcript got easier. The changes, with versions:

  • A finished /btw panel and its folded transcript row have a [Copy] button that copies the whole answer, even when only part of it is visible (1.0.74).
  • Quotes in replies get a [Copy] button that copies the quote as Markdown without its > markers (1.0.74).
  • Ctrl+L in the scrollback adds the selected message or highlighted text to your prompt as a quote (1.0.75). Open Extensions with /plugins instead.
  • Dragging in the transcript now selects and copies colored text across message blocks instead of whole blocks (1.0.78).

The Ctrl+L change affects muscle memory, so it’s worth remembering /plugins. The keyboard shortcuts page has the full list.

Shell approval cards explain Auto-review. A card now says when Auto-review blocked a command or couldn’t review it, and Ctrl+F shows the reviewer’s explanation (1.0.74). Separately, permission rules that fail to load now produce a warning when a session opens instead of being skipped silently (1.0.75). Examples are a rule that doesn’t parse and a .claude/settings.json that isn’t valid JSON. A rule that was quietly ignored is a bad surprise, so the warning is the more useful change of the two. See permissions.


Technical notes

Prompt and keyboard.

  • Cmd+Up/Cmd+Down and Ctrl+Home/Ctrl+End move the cursor to the start or end of the whole prompt. With Shift they select to there (1.0.75).
  • Left on an empty prompt opens the dashboard from any session or the welcome screen (1.0.75).
  • Esc on a /btw side question that hasn’t been answered yet cancels it (1.0.75).
  • Long pastes, including long single-line text such as logs, JSON or base64, no longer freeze the prompt for seconds (1.0.74).
  • Editing a queued prompt now shows an ‘editing’ label and dims the row (1.0.79).

Shell and background work.

  • ! mode Tab completion offers commands installed as symlinks, such as Homebrew, npm and rustup binaries (1.0.74).
  • The end-of-turn marker shows how many background commands are still running (1.0.79).
  • Link cards now appear by default for links that cannot be opened (1.0.79).

Sessions.

  • grok --resume <id> opens much faster on large session stores and opens the session in the folder it was recorded in (1.0.74, 1.0.75).
  • /rewind now works in place for paged sessions without reloading every turn (1.0.79).

Integrations and headless runs.

  • /mcps shows an MCP server’s sign-in URL in a copyable panel (c or [copy the url]) when the browser can’t open it (1.0.74).
  • Headless runs stopped by Ctrl-C or SIGTERM end their JSON output with a closing record that keeps the run’s outcome (1.0.74).

What to take away

If you work in the terminal. Try @~/ and @../ in a real prompt and see whether the outside-workspace listing suits you. If it doesn’t, [ui] at_picker_outside_workspace = false turns it off. Edit a picked chip with Backspace at its end or with Left/Right. If Shift+Enter misbehaves, set [ui] kitty_keyboard = 'query'. Try /vim-mode all if you live in Vim bindings, and note that Ctrl+L now quotes from the scrollback while /plugins opens Extensions.

If you run parallel sessions. grok --resume <id> is faster on large session stores and returns you to the folder the session was recorded in. /rewind no longer reloads every turn in paged sessions. The end-of-turn marker now counts background commands still running, so you can see what is pending. Left on an empty prompt opens the dashboard from any session, which helps when you switch between them.

If you administer integrations and company deployments. Open a session after changing permission rules and look for the new load warnings, especially for .claude/settings.json. Check how Auto-review messages read on shell approval cards, and use Ctrl+F for the reviewer’s explanation. For MCP servers that need a browser sign-in, /mcps now offers a copyable URL when the browser can’t open it. If you script headless runs, the closing JSON record after Ctrl-C or SIGTERM keeps the run’s outcome, so check that your parsers accept it. Decide whether the @ picker should reach outside the workspace for your users and set at_picker_outside_workspace accordingly.


Sources: the Grok Build changelog, versions 1.0.74 to 1.0.79 (November 2-8, 2026), and the Grok Build documentation pages linked above. Settings and shortcuts are described as of those versions, so check the documentation if availability differs in your build.

Patrick Zandl trains teams in Claude Code and agentic software development in Prague and writes about what actually works in real-world AI-assisted projects. Follow on LinkedIn

Read next

Get the next one by email

Every Tuesday: what changed in Claude Code, Codex and other coding agents, plus new articles. No spam.