Quick answer: Maccy works with both iTerm2 and Warp because it watches the macOS system clipboard, and both terminals read from and write to it. Install Maccy App, switch its search to Regex, keep password managers out of the history, and resolve the one real hotkey clash: Maccy Mac’s default Shift+Cmd+C collides with iTerm2’s Copy Mode shortcut. Once that’s handled, you get searchable, pinnable, local-only history for every command, path, and log line you copy.

You ran kubectl get pods -n staging forty minutes ago. You tweaked the flags twice since. Now you need the second version, but you copied three other things in between. The terminal’s shell history has the command, but not the output you copied, the stack trace you grabbed from the browser, or the path you pulled from Finder.

That gap, between shell history and clipboard history, is where a clipboard manager earns its place. This guide covers how to set up Maccy Clipboard alongside iTerm2 or Warp, which settings matter, where the two tools overlap, and where they behave differently.

Does Maccy work with iTerm2 and Warp?

Yes. Maccy is a menu-bar clipboard manager that polls the macOS pasteboard, so any app that copies to the system clipboard is captured, including terminals. There is no terminal-specific integration to install. The same is true for pbcopy: anything piped into it appears in Maccy’s history like any other copy.

Scenario Captured by Maccy? Notes
Select text in iTerm2, Cmd+C Yes Standard pasteboard write.
iTerm2 „Copy to pasteboard on selection“ Yes, but noisy Every selection becomes a history entry. See the tips below.
echo "text" | pbcopy Yes Handy for scripts and aliases.
Copying a block’s output in Warp Yes Warp writes to the system pasteboard.
Remote tmux/SSH clipboard via OSC 52 Depends Only if the terminal is allowed to accept OSC 52 clipboard writes. See below.
Text selected inside tmux with mouse mode on Depends tmux may keep the selection in its own buffer unless configured to hand it to the system clipboard.

Setup: the five-minute version

  1. Install. Download from the GitHub repository or run brew install maccy.
  2. Grant permissions. If you want Maccy to paste into the frontmost app for you, macOS requires Accessibility access (System Settings → Privacy & Security → Accessibility). Without it, Maccy copies the item and you paste manually with Cmd+V.
  3. Set search mode to Regex. In Maccy’s Settings → General, change the search mode from fuzzy to regular expressions . Terminal clips are structured, so regex pays off immediately.
  4. Review the Ignore tab. Add your password manager and anything else that touches secrets.
  5. Resolve the hotkey clash (next section).

The hotkey conflict nobody warns you about

Maccy’s default global shortcut is Shift+Cmd+C. In iTerm2, that same combination toggles Copy Mode, the keyboard-driven text selection feature. Global hotkeys are registered at the system level, so in practice Maccy tends to win and Copy Mode stops responding . Warp also assigns shortcuts around Cmd+Shift combinations, so check its Settings → Keyboard shortcuts for overlaps before assuming it’s clean.

You have two options:

  • Change Maccy’s shortcut (usually the simpler fix). Many people move it to something like Cmd+Shift+V or an Option-based combo that no terminal uses. Open Maccy’s settings and record a new shortcut.
  • Remap iTerm2’s Copy Mode under Settings → Keys → Key Bindings, if you actually use it daily.

Pick one and test it with the terminal focused. A shortcut that works in Finder can still behave differently in an app that captures keys aggressively.

A workflow, not a feature list

1. Rebuild a command from three sources

Say you copy a pod name from a dashboard, a namespace from Slack, and a flag from documentation. Open Maccy, pick them in sequence, and paste each into your prompt. Because Maccy lists items newest-first and numbers them, jumping back three or four entries is a keystroke or two instead of a trip back to each source app.

2. Search clips with regex

With regex mode on, you can narrow history precisely. Some examples:

You want Try
Any copied git command ^git
Anything that looks like an absolute path ^/[\w./-]+
IPv4 addresses \b\d{1,3}(\.\d{1,3}){3}\b
Stack-trace lines Exception|Traceback|at .+\(.+:\d+\)
Docker image references [\w.-]+/[\w.-]+:[\w.-]+

3. Pin the things you retype

Maccy lets you pin items so they stay at the top and survive history cleanup. Good candidates for terminal work: your SSH jump host string, a long docker run with volume mounts, a staging API base URL, or a multi-flag rsync invocation. Pins are a lightweight alternative to shell aliases when the snippet changes often or includes values you’d rather not commit to dotfiles. The pin shortcut is Option+P in recent versions .

4. Paste without dragging rich text along

Text copied from a web page can carry formatting. Terminals ignore most of it, but Warp’s input editor and some TUI tools can behave oddly with unexpected characters such as smart quotes, which silently break shell commands. Maccy has a paste-without-formatting action (Option+Shift+Return ) that strips formatting and keeps plain text. If a command copied from a blog „looks right“ but fails, curly quotes are the usual culprit.

iTerm2 vs Warp: what changes for clipboard use

iTerm2 Warp
Built-in clipboard history Yes. Paste History window, with optional saving to disk No full system-wide equivalent, but its input editor and command history cover some needs
Copy on selection Optional setting; floods Maccy if enabled Optional setting
Multi-line paste safety Configurable warnings; Advanced Paste for tweaking text before sending Input editor lets you review and edit multi-line text before running
OSC 52 (remote clipboard) Supported; must be enabled in settings Check current docs
Best Maccy pairing Cross-app history; iTerm2’s own paste history stays terminal-only Warp’s editor makes pasted multi-line snippets easy to inspect first

One honest note: iTerm2’s built-in Paste History overlaps with Maccy for terminal-only copying. If you live entirely inside iTerm2, you might not need a separate tool. Maccy wins when your clips come from everywhere (browser, Slack, Finder, Xcode) and you want a single, consistent shortcut.

Security: don’t let your clipboard history become a secrets log

Terminal work puts sensitive strings on the clipboard: API tokens, .env values, SSH keys, database URLs. Maccy keeps history locally, with no cloud sync, which is a real privacy advantage. But „local“ still means „on disk,“ so be deliberate.

  • Ignore your password manager. Add it under Maccy’s Ignore settings. Many password managers also mark their clipboard writes as concealed using the community nspasteboard.org convention, which clipboard managers can honor .
  • Use Maccy’s regex ignore for token patterns. If the Ignore tab supports ignoring by pattern , add something like ^(ghp_|sk-|AKIA)[A-Za-z0-9]+ to avoid storing common token formats.
  • Clear history after sensitive sessions. Maccy has a clear-history action (menu and keyboard shortcut) for exactly this.
  • Don’t ignore your terminal entirely. That would defeat the purpose. Be selective instead.

Common problems and fixes

Problem Likely cause Fix
History fills with fragments „Copy on selection“ is on Turn it off in the terminal’s settings, or accept the noise and rely on search
Maccy opens but won’t auto-paste Accessibility permission missing Grant it in System Settings → Privacy & Security
iTerm2 Copy Mode stopped working Hotkey clash Rebind Maccy’s shortcut
Pasted command fails with strange characters Smart quotes or hidden formatting from the source Paste without formatting
Remote tmux copy never reaches Maccy tmux or SSH isn’t forwarding to the system clipboard Enable OSC 52 in tmux and in the terminal
Large paste hangs the shell Not Maccy: the terminal or shell is the bottleneck Use iTerm2’s paste-slowly option or save to a file and source it

Where Maccy isn’t the right tool

Maccy stores what you copy. It doesn’t understand commands, run snippets with variables, or sync across machines. If you need parameterized command templates, a snippet manager or shell functions do that better. If you need your clipboard on two Macs, Maccy’s local-first design is a deliberate trade-off, not a bug. And for command recall specifically, Ctrl+R reverse search (or a tool like fzf or atuin) beats any clipboard manager. The two are complementary: shell history remembers what you ran, Maccy remembers what you copied.

The short version

Install Maccy, move its hotkey off Shift+Cmd+C, switch to regex search, ignore your password manager, and pin the handful of snippets you retype. That’s about five minutes of setup for a clipboard you can actually search. Which snippet is the first one you’d pin: that jump-host string, or the docker run you’ve typed fifty times?