Capture after copy
Clipboard changes enter session history with their source app; dedicated Chrome capture can add the web origin.
In validation · ad-hoc experimental download
Track where text was copied from and pasted to, with a direct path back to web sources.
macOS users who move material into Obsidian and want source links, clipboard history, and app-level flow records.
Concept illustration · sample data
Sutie records clipboard history and app-level paste flows locally. For Chrome web sources, its companion extension can also retain a sanitized page origin.
Standard ⌘C and ⌘V remain native to macOS and the destination app. A source link is created only when the user deliberately uses ⌥⇧C in Chrome and ⌥⇧V in Obsidian.
Knowing clipboard history does not give the product permission to rewrite every paste.
Clipboard changes enter session history with their source app; dedicated Chrome capture can add the web origin.
Record source and destination apps while keeping observed and verified evidence states distinct.
After copying A and then B, choose A from history and paste it back without overwriting a newer external clipboard change.
The dedicated shortcut turns only the copied text into a web link, with no Sutie ID, footnote, app name, or timestamp by default.
These are current implementation boundaries, not a formal security audit or a final database architecture.
Stored locally
Permissions and exclusions
This is an unnotarized experimental package on a personal site, not an Apple-verified public release.
Engineering evidence available
Pending before public release
Current download
The ZIP is 1,204,335 bytes; SHA-256 starts c8b7f007 and ends 00b369. This build applies six fixes from a three-perspective cross code review. If the first launch says Apple cannot verify the app and only offers Done/Move to Trash, choose Done, then allow this app under System Settings → Privacy & Security → Open Anyway.
The experiment download is open; the following are candidate goals for a normal public beta release.
Gate the first public beta on Developer ID, Hardened Runtime, a notarized DMG, stable Keychain identity, upgrades, and uninstall.
When WeChat or another capture tool places an image on the system clipboard, the candidate design records a thumbnail, source app, time, and dimensions, then pastes the original back. The first version would not use OCR, upload images, or request Screen Recording.
Use at least five real users to validate clean installation, permission explanations, Chrome/Obsidian pairing, Word flows, and accessibility before deciding whether to invest in Developer ID.
This page does not receive or upload clipboard content. Use the public support route for current status. View support