M
MesmerTools
Back to tools

Terminal Paste Cleaner

Paste mangled text copied from Claude Code, a CLI, or any TUI — get clean, readable output with soft-wraps unwrapped and trailing whitespace gone.

Input — paste here
0 lines
Output — clean
0 lines
Clean output will appear here…
Cleanup rules

How it works

Three steps. No sign-up, no server round trip — the cleanup happens entirely in your browser.

Step 1

Paste the mangled text

Drop in anything copied from Claude Code CLI, a TUI, or a terminal session. Trailing whitespace and soft wraps are fine — that's what the tool fixes.

Step 2
scanning

Detect terminal artifacts

Identifies trailing spaces, soft-wrap breaks, ANSI codes, box-drawing chars, NBSP and zero-width chars — and counts every one.

Step 3
clean

Copy the clean version

One click to copy. Paste into Obsidian, Notion, Slack, a PR description, or anywhere else — readable formatting restored.

Why use this

Most online text cleaners only strip trailing whitespace. This one knows what terminal output actually looks like.

Smart reflow

Detects lines that were soft-wrapped by the terminal and merges them back — while preserving list items, code blocks, and real paragraph breaks.

8+ artifact types handled

Trailing whitespace, ANSI escape codes, box-drawing chars, NBSP, zero-width chars, unicode spaces, smart quotes, and blank-line padding — all in one pass.

100% in your browser

Nothing gets uploaded. The cleanup runs as a pure function in your tab — paste secrets, commit diffs, or client data without worrying about where it goes.

Every rule is a toggle

Turn off reflow for ASCII diagrams, turn on dedent for quoted replies, enable smart-quote normalization for plain-text exports. Your call.

Common use cases

Whenever you copy from one of these and paste into a rich-text editor that doesn't understand terminal padding.

Claude Code CLI → docs & notes

Copy a Claude Code response, plan, or summary. Paste into Obsidian, Notion, Linear, or a GitHub issue without the vertical bar artifacts and trailing whitespace.

Used by developers working with Claude Code daily.

Logs → bug reports & PRs

Paste a stack trace or log tail from your terminal into a GitHub issue or PR description. Strip the color codes and trim the clutter so the important line is actually readable.

Used by engineers writing incident reports and reproductions.

TUI output → team chat

Output from k9s, lazygit, btop, htop, or any other TUI becomes a mess when pasted into Slack or Teams. Clean it first so your teammates can actually read what you're sharing.

Used by DevOps, SREs, and platform engineers.

Perfect for

If you live half your day in a terminal, this one is for you.

Claude Code users

Anyone who ships most of their work through the Claude Code CLI and copies results into docs, tickets, or chat.

Developers, founders, technical PMs.

Incident responders

Pasting terminal output into post-mortems, Statuspage updates, customer emails, or runbooks.

On-call engineers, SREs, support escalation.

Technical writers

Writing CLI documentation, tutorials, blog posts — where terminal transcripts need to be legible, not pixel-perfect to the terminal.

Docs teams, DevRel, technical bloggers.

Support engineers

Pasting customer terminal output into tickets — making sure the trace is actually readable to whoever picks up next.

Customer-facing engineers, T2/T3 support.