Skip to main content
Clypy for developers

Your clipboard is a dev tool. Treat it like one.

Commands, stack traces, env values and the odd token. Clypy keeps every clip, finds it by what it was, pastes it where your cursor is, and keeps the secrets out of it.

The strip is live. Tap a card to paste it into the note.

incident-4821.md
## Incident 4821: sync stalls after sleep
Severity: SEV-2 · Owner: @dana
### Timeline
- 09:40 staging alert: peers stuck in `syncing`
- 09:52 reproduced on a MacBook after sleep
### Evidence
repeat ⌘⌥V or click to search
tab navigate↩ paste⌥+1–9 paste by number⌥Space preview? more
0Synced · 240+ recent · ⌘⌥V

macOS · Windows · Linux · iPhone · Android · no Clypy profile · no card for Free

A day on your clipboard

Six copies you'd normally lose, and where they went instead

None of this needs a new habit. You copy the way you already do; Clypy works out what each clip is and handles it.
  1. 09:12

    You copy the kubectl command from the runbook.

    History

    It's in your history for good. Type “logs” in the strip at 5pm and it's the first card.

  2. 10:40

    A teammate drops a screenshot of a stack trace in Slack.

    Text in images

    Clypy reads the text in the image on your machine. Search the error message, paste it into the issue as text.

  3. 13:05

    You copy a Stripe key out of the dashboard.

    Secrets

    Concealed on sight and left out of search and agents. Mark it local-only if it should stay on this machine.

  4. 15:30

    The new service wants five values in its .env.

    Paste stack

    Queue them in order, arm the stack, and every ⌘V pastes the next one. No tabbing back.

  5. 17:50

    You tell Claude Code why you picked Redis Streams over Kafka.

    Agent memory

    It saves the decision to Clypy. Tomorrow, Codex in another repo can recall it.

  6. 21:15

    A bug report lands. You're on the laptop, on the couch.

    Sync

    This morning's command is already in the strip, synced end to end encrypted.

Secret hygiene

The token you copied shouldn't be on show

Clypy recognises sensitive clips the moment you copy them. The card shows a lock, the clip stays out of search and agents, and revealing it takes Touch ID or Windows Hello.
  • Recognised
    API and auth tokens, sign-in links, credentials, licence keys
  • Never captured
    Anything copied from a password manager, or an app you exclude
  • Invisible to agents
    Left out of search, exports and every MCP tool
  • Your call where it goes
    Mark a secret local-only, or set it to expire
Secret · auth tokenExpires in 59:12
••••••••••••
Concealed on every deviceReveal
Paste stack

Fill a .env without tabbing back once

Copy the five values from the dashboard, queue them in the order the file wants, then paste them one after another. If you switch apps halfway, Clypy stops rather than paste into the wrong window.
  1. ⌥S on each clip
  2. ⌘⌥S to arm
  3. ⌘V ⇥ ⌘V

Queue the clips a form needs with ⌥S, arm the stack with ⌘⌥S, and every ⌘V pastes the next one. A whole shipping form, filled with ⌘V and Tab.

Agent memory over MCP

One memory for Claude Code, Codex and Cursor

Clypy serves MCP itself, with nothing else to install. Tell one agent to remember a decision and a different agent in a different repo can find it tomorrow, in its own collection or one you share.
  • Off until you turn it on. You choose whether agents read full text and save or change clips.
  • Secrets are never returned to an agent, whatever it asks for.
  • One click for Claude, Codex, Cursor and more, a prompt for any other agent. Remove one any time.
Claude Code · ~/northwind/api · Monday
› Remember: we chose Redis Streams over Kafka for the job queue. Ops can run it and we don't need replay past 7 days.
✓ Saved to Clypy · Team Decisions
Codex · ~/northwind/worker · Tuesday
› Why aren't we on Kafka?
Found in Team Decisions: Redis Streams was chosen because ops can run it and replay past 7 days isn't needed.

Tell Claude Code to remember a decision and it saves it to Clypy. Later, Codex in another project recalls it, and secrets never show up in what agents find.

The CLI

Your history, scriptable

The clypy command talks to the running desktop app, so scripts read and write the same encrypted library the strip shows. Stable exit codes, JSON output and shell completion included.
curl -fsSL https://updates.clypy.app/install.sh | sh

Windows, ARM builds and checksums are on the download page.

$ command | clypy add
Save any command's output as a clip
$ clypy pick deploy
Fuzzy-pick a clip in the terminal
$ clypy --json search invoice
Search history from a script, as JSON
$ clypy transform json < package.json
Format JSON, YAML, XML or SQL, decode a JWT, hash, sort
$ clypy pause --minutes 30
Stop capturing while you screen-share
$ clypy export backup.json
Export clips and collections
Keyboard first

Your hands never leave the keys

Everything in the strip has a shortcut. Shown here for macOS; Windows and Linux use their own modifiers.
Ctrl/Command + Alt/Option + V
Summon the strip over any app
⌥1 … ⌥9
Paste the first nine cards without looking
⌥↩
Paste as plain text from the strip
⌘⇧V
Paste as plain text from anywhere
⌥Space
Quick Preview a clip full size
⌥S
Add a clip to the paste stack
⌘⌥N
Write a new clip without switching apps
P
Pin the selected clip
FAQ

What developers ask us

Anything else? The help centre has the rest.

Does Clypy capture what I copy from my password manager?

No. Copies from password managers, and anything your system marks as concealed, are never stored at all. You can add any other app you'd rather Clypy ignored.

What happens to an API key I copy by accident?

Clypy recognises tokens, credentials and sign-in links when they're copied. The clip is concealed and left out of search, exports and agents, and revealing it requires system authentication. It syncs to your other devices encrypted and concealed; mark it local-only to keep it on one machine.

Does it run on Linux?

Yes. The Paste Strip runs on macOS, Windows and Linux, and the iPhone and Android apps paste from the same history. One Pro licence covers every device.

Can AI agents read my clipboard?

Only agents you connect in Clypy's Settings, and only while you have MCP switched on. You choose whether they can read full text or save and change clips, and secrets are never returned.

Does my clipboard go through your servers?

On the same network, your devices sync directly. Elsewhere, an encrypted relay passes ciphertext it can't read. Search, text recognition and classification all run on your machine, and Clypy works fully offline.

Can I send a build or a log file to another device?

Yes, with Pro. Send files moves files of any size between your paired devices over your local network, end-to-end encrypted: a debug .apk to the test phone, a crash dump from the laptop. They're saved as files in Downloads, never as clips, and never pass through our servers.

Can I paste code without the formatting it was copied with?

Yes. ⌥↩ in the strip, or ⌘⇧V from anywhere, pastes as plain text. Code clips keep their line breaks and show highlighted in the strip.