Your clipboard is a dev tool. Treat it like one.
A developer's clipboard churns harder than anyone's: snippets, tokens, stack traces and one-off shell commands. Clypy keeps every clip, pastes it clean, and never leaks a secret.
The clipboard was never built for how you work
- Lost snippet
You copied a value, copied three more, and the first is gone just when the migration needs it.
- Smart quotes
A copy-paste from a doc drops curly quotes into your YAML and the deploy fails at 5pm.
- Leaked token
That API key you pasted once is now sitting in your clipboard history forever.
Refactor without round-trips
Copy five values from a config, switch files, and paste them one after another in the order you grabbed them. It is a queue for your clipboard, with no tabbing back and forth or losing your place.
Tokens can't end up in history
Anything that looks like a key, including content from a password manager, is concealed on sight, excluded from sync, and auto-expires in minutes. Paste it, forget it, safely.
A normal Tuesday, minus the friction
Editors always get plain text
Set a rule once: anything pasted into VS Code, a terminal, or vim arrives stripped of formatting. No more smart quotes breaking your YAML.
Error screenshots become text
A teammate sends a screenshot of a stack trace. Copy the text straight out of the image and paste it into your search. No retyping line numbers.
A snippet stays a snippet
Clypy tags every clip as code, link, secret or file, so a fenced block keeps its formatting and a token gets flagged the moment it lands.
Three machines, one history
Laptop, desktop, remote box. Everything is end-to-end encrypted, so what you copy never sits in plaintext on someone else's server.
“I stopped keeping a scratch file of env values. Clypy is the scratch file now, and it follows me to the laptop without me thinking about it.”