Guide

The prompt editor (Ctrl-G)

Long prompts deserve better than a terminal input line. Ctrl-G opens them in a real editor, right on top of the pane.

What it does

Claude Code and Codex both have an "open this prompt in your editor" key:Ctrl-G. In a terminal that normally drops you into vim. In a Gallager pane it opens a resizable editor overlay on top of the terminal — type comfortably, then ⌘Return to submit the edited prompt back to the agent, or Escape to cancel and leave it untouched.

There's nothing to set up: Gallager points $VISUAL at its own tiny editor shim in every session it manages, so Ctrl-G just works. It never touches your shell configuration.

If you already set $VISUAL

If your shell profile exports its own $VISUAL, it wins inside login shells — so Gallager probes for that conflict and asks what you prefer the first time you create a session. Your choices, changeable later underSettings → Editors → Prompt editor (Ctrl-G):

  • Use Gallager's editor in Gallager sessions — your editor stays the default everywhere else. The recommended route is a one-line guard in your profile so your export skips Gallager-managed shells.
  • Keep your editor — Ctrl-G opens your GUI editor on the Mac instead of the overlay.

From a remote viewer

Viewing your Mac from another Mac? The same overlay appears on the viewer, and either machine can finish the edit — first submit wins. On the iPhone the overlay isn't available; prompt editing stays a desktop feature.

Beyond agents

The shim is an ordinary command — gallager edit <file> — so any tool that shells out to $VISUAL inside a Gallager pane gets the same treatment, and you can use it directly from scripts: it blocks until you submit or cancel, just like an editor should.

← All docs