clipaste CLI
A screenshot from the clipboard reaches Claude Code, Codex and Cursor on macOS, Windows, over SSH and in WSL2, with no config
- 65 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The daemon reads the clipboard and serves its images over HTTP on a local port, and a remote server gets them through an SSH tunnel
- On macOS and Windows it changes clipboard contents by adding a file path beside the image
Install
- Works in
Manual install
brew install hqhq1025/clipaste/clipasteThen `brew services start clipaste`. Windows: the `install.ps1` one-liner; any platform: `cargo install --git https://github.com/hqhq1025/clipaste --tag v2.6.0 --locked`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The daemon reads the clipboard and serves its images over HTTP on a local port, and a remote server gets them through an SSH tunnel
- On macOS and Windows it changes clipboard contents by adding a file path beside the image
This is third-party code. Review the repository files before installing.
What it does
clipaste is a small Rust background daemon that fixes screenshot paste in terminal AI tools such as Claude Code, Codex CLI and Cursor. On macOS a screenshot puts only raw TIFF or PNG data on the clipboard, and terminals like Ghostty and Alacritty can paste only text or file URLs with Cmd+V. clipaste saves the screenshot as a PNG, adds a path beside the image and enables Cmd+V, and for Ctrl+V it adds the legacy PNGf type. Over SSH the daemon runs an HTTP server on `localhost:18340`. `clipaste ssh-setup user@your-server` configures the remote machine: it detects the OS, installs an xclip or wl-paste shim in `~/.local/bin/` and an SSH tunnel, so Ctrl+V in remote Claude Code fetches the image from your local clipboard. The server needs only `curl`. For WSL2 the same shim points straight at `clipaste.exe` on Windows, with no tunnel. The local daemon runs on macOS and Windows, while a graphical Linux session only serves clipboard PNG over SSH without changing the clipboard. Server-only mode leaves the macOS and Windows clipboard untouched if you only paste into remote agents.
Who it is for. People who use Claude Code or Codex in a terminal on macOS, over SSH on a server or in WSL2 and cannot paste a screenshot into it.
Good fit when
- After a screenshot, Cmd+V or Ctrl+V in Claude Code pastes nothing in a Ghostty terminal
- The agent runs on a remote server over SSH and the picture sits in your local clipboard
- Claude Code lives in WSL2 while the screenshot is taken in Windows
- The clipboard must stay unchanged while images go only to remote agents, which is what server-only mode is for
Not a fit when
- You want a clipboard manager or cross-device sync: clipaste passes only images to agents
- Linux has no graphical session with a working clipboard: hosting needs one
- The agent cannot reach `localhost:18340` and cannot use the xclip shim
Example request
I took a screenshot of an error. Paste it from the clipboard and tell me what it saysLimitations
- Clipboard hosting works on macOS, Windows and graphical Linux with a usable clipboard; on Linux it is read-only and serves `image/png`, and desktop compatibility has to be verified on your setup.
- The remote server needs `curl`, and a Linux host needs `wl-clipboard` and `xclip`; the install creates no Linux autostart service.
- On macOS and Windows the daemon changes the local clipboard by adding a path beside the image; server-only mode avoids that.
- The HTTP server on `localhost:18340` serves clipboard images, so keep the tunnel to trusted servers.
How to disable. Stop the daemon with `brew services stop clipaste` on macOS and remove the package with `brew uninstall clipaste`; delete the shim from `~/.local/bin/` on the server.
FAQ
How do I install clipaste on macOS?
Run `brew install hqhq1025/clipaste/clipaste` and start the daemon with `brew services start clipaste`. Windows has an `install.ps1` one-liner, and any platform can build with `cargo install --git https://github.com/hqhq1025/clipaste --tag v2.6.0 --locked`.
How do I enable paste over SSH?
Run the daemon locally and execute `clipaste ssh-setup user@your-server`. For a custom port add `-p 22222`. The command detects the server OS and installs the shim itself.
Does clipaste work in WSL2?
Yes, as long as `clipaste.exe` runs on the Windows side: the xclip shim in WSL2 connects to it directly with no SSH tunnel.
Why does Ctrl+V not paste a screenshot in the terminal?
A macOS screenshot puts raw TIFF or PNG data on the clipboard, and terminals paste only text or file URLs. clipaste adds a PNG path beside it and the paste starts working.
How much does the daemon use?
The author cites about 9 MB of RAM and roughly 0 percent CPU at idle, with no configuration.
Discussion
No questions or reviews yet.
Related
CLI toolsThe Clippy MCP server for macOS: an agent puts text, files and email drafts on the clipboard to paste into Slack, Gmail or Teams.
Claude Code plugin for pasted images: thumbnails above the prompt and a markup editor before sending.
Cross-device clipboard sync with a built-in MCP server: the agent reads your copy history, and data never leaves for the cloud
Named clipboards retain terminal text and files so results move between commands and sessions without a graphical file manager.
A macOS app that remembers your screen and opens the history to agents over MCP: search, days, work threads, screenshots.
A skill and MCP for voiced screen recordings: the agent turns a spoken bug walkthrough into tasks with screenshots and code
README in short
The README explains the screenshot paste problem in terminal AI tools, its cause and the fix, and lists platforms, install routes, SSH and WSL2 setup and the server-only mode.