---
title: "Verified Cut and Paste"
date: "2026-07-23"
canonical: "https://raytally.com/en/ideas/2026-07-23-ghost-cut-or-why-cut-and-paste-is-broken-everywhere/"
generator: "RayTally · dev-prompt-v4"
signal:
  query: "Ghost Cut – or why Cut and Paste is broken everywhere"
  observed_at: "2026-07-23T00:33:12.762Z"
sources:
  - url: "https://news.ycombinator.com/item?id=49007626"
    boundary: "Published at 2026-07-22T00:00:00.000Z. Observed at 2026-07-23T00:33:12.762Z."
  - url: "https://ishmael.textualize.io/blog/ghost-cut/"
    boundary: "Published at 2026-07-22T00:00:00.000Z. Observed at 2026-07-23T00:33:12.762Z."
  - url: "https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard"
    boundary: "Published at 2026-01-28T00:00:00.000Z."
  - url: "https://pasteapp.io/"
    boundary: "No publication timestamp is present in the source record."
notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief."
---

[Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-23-ghost-cut-or-why-cut-and-paste-is-broken-everywhere/)

Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting.

You are a senior product engineer. Turn the product idea below into a locally runnable MVP.

## Idea

Verified Cut and Paste
A safer cross-app Cut keeps the source intact until the pasted text and formatting have been verified, with one-click in-place recovery if the transfer fails.

## Product concept

When a writer presses Cut in an editor, the content enters a visible pending-transfer state instead of disappearing immediately. The app generates a verification marker for the text or rich text and leaves a temporary move receipt at the edge, making clear that the source has not yet been formally deleted. After the user pastes into another app, the extension checks whether the destination received an identical, fully formatted copy. Only after successful confirmation is the source deleted. If the destination app crashes, the clipboard is overwritten, or table formatting is lost in transit, a one-click restore control remains available in the original location. Users can also open a recent moves list to see where content was cut from, where it was pasted, and whether the transfer has been confirmed. For quotes, paragraphs, and tables moved between apps, this short-lived record reduces the panic of wondering where the content just cut went. The initial version starts with text and rich text in browsers and common document editors, without promising support for every system-level file move. It turns Cut from an irreversible deletion into a two-stage handoff that deletes the source only after the destination is verified.

## Why now (backed by facts)

The Ghost Cut article published on July 22 brought non-atomic cuts, fragmented undo, and clipboard overwrites into discussion that day. As of the July 23 snapshot, the post had 118 points and 83 comments, ranking 13th on the front page. This set of failure cases is being seriously discussed by a group of technical users.

## Direction (model inference, not independently verified)

Target user: Writers and editors who frequently move content between documents, web forms, and chat tools. The highest-risk moment is the few seconds after cutting a long paragraph, quote, or table and switching apps to paste it: the source has disappeared, while the destination may crash, reject the formatting, or lose the content to a newer clipboard item. For someone restructuring a draft, restoring text to its exact original position matters more than recovering a stray copy.

Minimal entry point: Start as a Chromium extension supporting text fields and standard contenteditable elements in the browser. Content scripts take over cut and paste events on supported pages and retain plain text and HTML. Use the Web Crypto API to generate content digests, with separate tag and table fingerprints for structure. Store pending-transfer records in IndexedDB, linked to the source tab, element, and surrounding text. When a paste occurs at a destination, read the inserted result and compare normalized versions. The first release makes no promise to support desktop apps, images, or arbitrary proprietary editors; it provides adapters only for a small set of web editors.

The strongest case against: The largest risk is that browsers cannot reliably verify paste results in arbitrary destination apps. Clipboard-read permissions, page focus, and browser differences can break the confirmation chain. Rich text is rewritten across editors, so identical content may produce different structural fingerprints. If the source page refreshes or is edited collaboratively, delayed deletion could overwrite someone else’s newer changes. The extension would also encounter emails, contracts, and keys; any ambiguity in its permission explanation would erode trust. If it supports only a few web editors, users may not want to relearn Cut behavior with exceptions.

These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty.

## Punching above weight (model inference)

Launch with an interactive demo that reproduces the failure: cut a table, overwrite the clipboard, then restore it in place. Publish short tutorials around concrete queries such as “cut paste lost text” and “clipboard overwritten” to capture existing search intent. Recruit frequent cutters from writer, editor-plugin, and productivity-tool communities. Maintain a public compatibility matrix and failure log so early users can directly request the next editor adapter.

## Competitors & gaps (model inference)

- Ishmael Ghost Cut: Ishmael’s Ghost Cut already turns an in-editor cut into a ghost state: after Cut, the original fades and becomes temporarily uneditable; Escape restores it, and it is removed only after paste. The whole move can be undone as one operation and does not use the system clipboard. That proves a pending-move state can fit existing shortcuts without asking writers to change their habits. Its limit is that it operates within one editor and cannot confirm delivery across apps. Users do not see a movement receipt linking source and destination, and it does not check formatting integrity. The opening is to extend the same principle across supported web editors, using content fingerprints, cross-tab confirmation, and in-place restoration to handle failures.
- Paste: Paste offers searchable clipboard history, cross-device access, and pinned favorites. It saves text, links, images, and files, and lets users retain original formatting or convert content to plain text. Users can exclude sensitive apps such as password managers, with data stored on-device or in private iCloud. These features reduce loss when the clipboard is overwritten and work well for frequently reused snippets. But Paste still treats cutting as deleting the source first and storing the content afterward. Even if the old content can be recovered, it cannot automatically return it to its exact place in the original text. It does not bind source and destination into a single move or inspect the pasted table structure. The opportunity is not another history panel, but delaying deletion until the destination has been verified.

## How it makes money (model inference)

Annual subscription for individuals. The free tier includes plain-text protection and a limited set of recent receipts; the paid tier adds rich-text verification, longer history, multi-device sync, and app adapters. Sensitive content stays local by default, and cloud sync is not required to access paid features.

## Source context

Theme: Ghost Cut and broken cut-and-paste
Trigger Hacker News post (original English): Ghost Cut – or why Cut and Paste is broken everywhere
Heat at capture: ~118 points, 83 comments (point-in-time values)

Points and comments are a historical snapshot from the moment of capture and drift over time. They only explain “why now”; do not present them as precise market numbers.

## Sources

- Ghost Cut – or why Cut and Paste is broken everywhere (https://news.ycombinator.com/item?id=49007626)
- Introducing Ghost Cut - or why Cut & Paste is broken everywhere (https://ishmael.textualize.io/blog/ghost-cut/)
- Interact with the clipboard (https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard)
- Paste — Clipboard Manager for Mac, iPhone & iPad (https://pasteapp.io/)

## Deliverables

- Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery.
- Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary.
- Do not show unverified market numbers in the UI or API.
- Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge.
- If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code.
- If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype.
- When done, explain what changed, how to run it, and how to verify it.
- Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.