Copy from the terminal.
Paste it clean.
Undoes what the terminal did to your text. Code passes through untouched.
npm install --global cleancopy-cli The deploy failed because the staging
config was missing a required key, and
the same key is absent in production,
so the fix needs to land in both
places before Friday. Don't take our word for it
Edit the left pane.
The deploy failed because the staging config was missing a required key, and the same key turns out to be absent in production too, so the fix needs to land in both places before Friday. $ kubectl get pods NAME READY STATUS api-7d9c4b 1/1 Running worker-5f8d2a 0/1 CrashLoopBackOff Next steps: - roll the config change out to staging and verify the worker restarts cleanly - backport the key to the production chart
Three kinds of terminal dirt.
····The deploy failed ····because the staging ····config was missing
The fix needs to land ↵ in both places ↵ before Friday.
Deploy⟨ZWSP⟩ when ready⟨NBSP⟩ restart the worker⟨ESC[0m⟩ then verify⟨BOM⟩
Code, tables, JSON, logs — never touched. When unsure, it does nothing. full list →
Nothing leaves your machine. Ever.
No disk writes. No password-manager items. No network. Everything runs locally.
learn more in the docs →Fair questions
Will it mangle my code?+
No — that's the whole design. The cost of mistakes is asymmetric, so the classifier is biased hard toward caution: code, tables, traces, and data pass through verbatim, and anything uncertain is left exactly as it was.
Which terminals are supported?+
Terminal, iTerm2, Alacritty, kitty, WezTerm, Warp, Hyper, Ghostty, Termius, and common
variants. Add your own by bundle identifier:
export CLEANCOPY_TERMINALS=com.example.my-terminal.
Does it work on Linux or Windows?+
No. The clipboard watcher relies on a native macOS helper, so the package refuses installation elsewhere rather than installing a command that cannot work. macOS 12+, Node.js 22+.
Can I clean text without running the watcher?+
Yes: pbpaste | cleancopy clean | pbcopy cleans the clipboard once. Add
--explain to see how each block was classified.
How do I start it automatically at login?+
cleancopy autostart on registers a launch agent;
cleancopy autostart off stops it and removes the agent. Bare
cleancopy autostart shows the state.
Something was cleaned that shouldn't have been. What now?+
Press cmd+ctrl+z — the revert hotkey — and the original copy is back.
Then file an issue with a fixture: drop input.txt and
expected.txt under test/fixtures/ and run
npm test. Real-world terminal output makes the engine safer.
