In validation · not publicly released

Sutie

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.

See validation status

Workflow illustration from copy source through Sutie to paste destination

SurfacesmacOS + Chrome + Obsidian

SystemmacOS 14+ · Apple Silicon

Current build0.4.0 · build 23

Status checked2026-07-28

Keep “where this came from” attached to the act of collecting it

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.

02 / Current capabilities

History, flow records, and source links stay separate

Knowing clipboard history does not give the product permission to rewrite every paste.

Capture after copy

Clipboard changes enter session history with their source app; dedicated Chrome capture can add the web origin.

App-level flow record

Record source and destination apps while keeping observed and verified evidence states distinct.

Paste from history

After copying A and then B, choose A from history and paste it back without overwriting a newer external clipboard change.

Obsidian inline link

The dedicated shortcut turns only the copied text into a web link, with no Sutie ID, footnote, app name, or timestamp by default.

03 / Local privacy boundary

Clipboard text stays in session memory; persistent records store metadata

These are current implementation boundaries, not a formal security audit or a final database architecture.

Stored locally

Source, destination, title, and safe URLs are encrypted in the ledger with AES-GCM
The master key is protected by macOS Keychain
Copied text remains in app session memory for at most 60 minutes, subject to count and size limits
Logs, exports, and the persistent ledger do not store clipboard body text

Permissions and exclusions

Input Monitoring observes copy and paste shortcuts without swallowing them
Accessibility identifies the frontmost app, sensitive controls, and dedicated paste targets
No Screen Recording permission; incognito sources and sensitive fields are excluded by policy
The current AES-GCM JSON ledger is a validation implementation, not the final long-term database

04 / Release boundary

The engineering candidate is testable; public download remains closed

Publishing this page makes the project visible; it does not make the software a public release.

Engineering evidence available

macOS 0.4.0 build 23: arm64, macOS 14+, ad-hoc signed
Swift normal, Thread Sanitizer, and Address Sanitizer runs each passed 115/115
Obsidian plugin 50/50; production plugin 0.4.1 does not intercept normal paste
Chrome 0.1.2, Native Host, and the local encrypted ledger have build and smoke-test evidence

Pending before public release

Complete build 23 physical-shortcut matrix, Office flow, and human accessibility acceptance
Developer ID signing, notarization, stable Keychain identity, and formal install/uninstall flow
Public license, download origin, support route, and upgrade/rollback instructions
Notion support has not started and is not a current capability

Current gate

Download, purchase, and source links remain closed

The current app is for local development acceptance only. This site contains no .app, DMG, plugin ZIP, Chrome extension package, or active checkout link.

05 / Versions and boundaries

Facts currently confirmed

macOS App: 0.4.0 · build 23 · arm64
Chrome Extension: 0.1.2 · Manifest V3 · Chrome 109+
Obsidian Plugin: 0.4.1 · Obsidian 1.12+ · Desktop only
Signing: Ad-hoc · not notarized
License: No public distribution license declared
Public source: No public repository linked

This page does not receive or upload clipboard content. Use the public support route for current status. View support