Skip to main content

Tips

None of this is required to use Saggar. All of it saves a step, and most of it is the sort of thing you only find by accident. Keyboard shortcuts have their own page — see Keyboard and the palette.

Rest the pointer on a file path in any terminal output and a preview card appears. What is in it depends on what the path is:

  • a text file shows its first few lines;
  • a folder shows what is in it, and how many entries;
  • an image shows the image, whole rather than cropped.

The card reads the file once, when the hover lands, and caps how much it reads. Hovering a path in a huge log never drags the whole file through memory.

The card's Open button opens the file in the project's IDE, at the line number if the path named one, and Reveal shows it in the Finder. You can skip the card: hold ⌘ and the link underlines and the pointer becomes a hand, and ⌘-click opens it.

URLs get the same treatment, with the page's title and description fetched for public addresses. Anything local — localhost, .local, a private address — is never fetched.

Hover an agent's image attachment​

When you paste or drop an image into Claude Code or Codex, the TUI replaces it with a placeholder like [Image #1]. Saggar keeps the bytes, so hovering that placeholder shows you the image you actually sent. Useful several prompts later, when you no longer remember which screenshot was #2.

Right-click a terminal​

The context menu is not just copy and paste. Saggar's shell integration knows where the last command started and ended, so the menu offers:

  • Copy last command output, without selecting it (⌘⇧C does the same);
  • Send last output to scratchpad, straight into the project's notes;
  • Save transcript… for the whole session;
  • New terminal here, in the directory this shell is actually in;
  • Open in your IDE, Reveal in Finder, and Copy path for that directory.

Rest on a terminal in the project menu​

Rest — don't sweep — on a terminal row you are not currently looking at, and a card shows the last dozen lines of its output. It is for answering "what is that one doing" without leaving the terminal you are in, so it never appears for the terminal already on screen.

Click the amber mark instead of switching​

A terminal that needs you wears an amber ! in the project menu. Put the pointer on the row and that ! turns into a tick you can click:

  • a filled tick answers the prompt with its default;
  • a hollow tick marks the bell as seen.

Either way you resolve the claim without leaving the terminal you were working in.

Hold ⌘ to see where everything is​

Holding ⌘ for a moment labels the interface: each terminal in the project menu gets its number for ⌘1–⌘9, the controls in the window chrome get their chords, and dashed ghosts appear in the corners where the monitor and quick-run panels will open. Let go and it all goes away.

Drag things in​

Saggar accepts drops in four places, and each does something different:

  • A folder from the Finder onto the project menu adds it as a project. The menu draws an amber border when it will take the drop. Loose files are ignored — a project is a directory.
  • A file or folder from the Finder onto a terminal types its path, quoted and escaped as one argument, with a trailing space. Drag several at once and you get several arguments. This is what Terminal.app does, and Saggar does it the same way.
  • An image onto an agent's terminal does that, and also keeps the image, so the placeholder the agent writes back previews on hover.
  • A project row onto a terminal types that project's path. Handy for cd, for opening an editor, or for telling an agent where to look.

Drag things around​

  • Drag a terminal row from the project menu onto the left or right half of the terminal area to open it there. Dropping on the right gives you a split with the terminal you were in.
  • Drag a terminal's header strip out of the window to tear it off into a window of its own.
  • Drag the seam between the project menu and the terminal to resize it, and double-click the seam to snap it back to the default width.

The Git chip is a set of buttons​

The chip in a project's header is clickable in two places. The branch name opens a branch switcher; the change count lists the changed files, and each row there will show a diff, open the file in your IDE, reveal it in the Finder, or copy its path. It also stops updating while the pointer is over it, so nothing moves out from under a click.

Quieter details​

  • ⌘Q is hold-to-quit. Tapping it does nothing, and holding tells you what is still running before it goes.
  • ⌘⇧P lists what is listening on which port, including processes that outlived the terminal that started them.
  • ⌘/ shows the project's scratchpad, which is where Send last output to scratchpad puts things.
  • ⌘L puts the cursor in the project menu's filter. It is fuzzy and live, and Escape clears it.
  • ⌘=, ⌘-, and ⌘0 change terminal text size for every terminal, not just the focused one.
  • Typing into a terminal you have scrolled up in returns you to the bottom, so a command entered a row or two above the prompt still lands.
  • Right-click a project for Rename project… — a local display name, so the folder on disk keeps its own — and for an emoji, which you can pick from the grid or type.
  • ⌘K on an empty query offers the terminal you last jumped to as ↵ again, so bouncing between two terminals is one key.
  • ⌘⇧/ shows every shortcut, whenever the list stops being memorable.