Markdown becomes a document, not a wall of asterisks
Headings, nested lists, tables, blockquotes, and fenced code with syntax highlighting and a copy button.
Most clipboard managers hoard.
This one asks.
Pastery offers each copy instead of recording it. Keep the few worth keeping; everything else expires and never touches your disk.
Keep this copy?
Fixes are done and verified. PR is blocked.
Withdrawing either statement erased the other.
feat/exercise-drawer
0001_rls.sql
1,757 chars
Dismiss
Keep ⌘⇧K
A history you never asked for is not a library.
Record everything and you get a drawer of half-copied passwords, stray URLs and one thing you actually wanted. Finding it means reading past all the rest.
Pastery inverts that. A copy is offered, not taken. Ignore the panel and the copy is dropped from memory — it is never written down, so there is nothing to prune later and nothing to leak.
It reads what it keeps.
Each entry is classified on your machine — Markdown, code, terminal output, a diff, JSON — and rendered as the thing it is.
Identifiers get their own colour
Git branches, commit hashes, file paths, shell commands and test summaries are recognised and tinted — a key, not a highlighter.
Built for /copy
A Claude Code response goes straight into the library, and is completed from the response file when the terminal truncated it mid-answer.
Provenance, stated plainly.
Nothing you copy leaves your Mac. No telemetry, no account, no sync.
The one exception, said out loud rather than hidden behind a blanket claim: Pastery checks for updates. That request carries nothing about you or your clipboard, and you can switch it off.
Notarized by Apple. Signed with a Developer ID, so it opens with no Gatekeeper warning.
Password managers are skipped. And any copy an app marks concealed is never stored, or even offered.
Updates are signed. Each release is EdDSA-signed and delivered over HTTPS.