惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
I
InfoQ
H
Help Net Security
GbyAI
GbyAI
博客园 - 叶小钗
Recent Announcements
Recent Announcements
Engineering at Meta
Engineering at Meta
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
爱范儿
爱范儿
Y
Y Combinator Blog
L
LangChain Blog
腾讯CDC
酷 壳 – CoolShell
酷 壳 – CoolShell
WordPress大学
WordPress大学
Stack Overflow Blog
Stack Overflow Blog
F
Fortinet All Blogs
G
Google Developers Blog
Apple Machine Learning Research
Apple Machine Learning Research
The GitHub Blog
The GitHub Blog
T
The Blog of Author Tim Ferriss
博客园 - Franky
D
Docker
Jina AI
Jina AI
罗磊的独立博客

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Building a local-first clipboard workspace for macOS
刘芷维 · 2026-05-27 · via DEV Community

刘芷维

I am the developer of Adhibit, a macOS clipboard workspace mentioned in this article.

Most clipboard managers start with one useful question: what did I copy recently?

That is a good starting point, but it is not the whole workflow. A lot of copied content stops being temporary after a few minutes. A command copied from a terminal session, a support reply, a link, a prompt, a screenshot, a file path, an error message, a color value, or a reusable snippet often becomes part of a small personal knowledge base.

I built Adhibit because I wanted a Mac clipboard tool that treated those copied pieces as reusable context, not just a chronological list.

The product direction became a local-first clipboard workspace:

  • keep text, links, files, images, colors, OCR text, and templates searchable;
  • make recent clips quickly available from the menu bar or Shift-Command-V;
  • let users organize reusable material into Pinboards;
  • avoid requiring an account for normal use;
  • keep clipboard contents off developer servers;
  • make multi-Mac sync optional through iCloud rather than mandatory through a product account.

The privacy boundary matters because clipboard content is unusually sensitive. It can include one-time links, code, personal notes, fragments of customer conversations, credentials users copied temporarily, invoices, screenshots, or private URLs. Even when an app does not intend to collect sensitive data, a clipboard tool sits close to it.

That pushed a few product decisions:

  1. Local-first storage is the default.
  2. No product account is required for the App Store version.
  3. Clipboard contents are not uploaded to Adhibit developer servers.
  4. iCloud sync is opt-in and uses Apple's iCloud.
  5. Retention and privacy controls are part of the core product rather than advanced settings.

The harder design problem is deciding what clipboard history should become. A plain timeline is fast, but it gets noisy. A notes app is flexible, but it adds too much manual organization. Adhibit sits in between: recent history is still there, but users can search it, pin important items, and move reusable material into Pinboards when it stops being temporary.

OCR is useful for the same reason. Screenshots often contain the exact thing a user needs later: an error, a receipt line, a message, a small UI label, or a reference number. Indexing image text makes those screenshots retrievable without forcing the user to name or file them first.

Templates are another piece of the same workflow. Many people keep repeated replies, prompts, snippets, and small operating procedures scattered across notes, documents, and chat history. A clipboard workspace is a natural place for those fragments because the final action is usually copying them into another app.

Adhibit is still early. The current public Mac version is 1.0.2, requires macOS 15 or later, and supports English and Chinese. It is free to download with a 14-day Pro trial. The App Store version uses Apple in-app purchase, and the direct-web version uses Paddle licensing.

The main lesson so far is that clipboard tools need more privacy clarity than ordinary productivity apps. Users do not only ask "can I find my clips?" They ask "where did this content go, who can read it, and how long will it stay there?" For this category, those questions should be part of the product surface, not hidden in a policy page.

Links: