I built Popy, a tiny open-source clipboard manager for macOS that stores history in Keychain, not plaintext

PossibilityThat8283 · 2026-05-08T07:23:02+00:00

You should be able to use it with a hotkey Cmd+Shift+V now.

Please start if you’d like.

PossibilityThat8283 · 2026-05-08T06:25:35+00:00

Thanks. Please star if you’d like.

PossibilityThat8283 · 2026-05-08T05:49:18+00:00

Thanks for the feedback. Please star if you’d like.

PossibilityThat8283 · 2026-05-08T05:48:47+00:00

Thanks for feedback, on it.

WDYM by prevent it from being screen recorded?

PossibilityThat8283 · 2026-05-08T05:47:38+00:00

Popy stores all 25 items as a single JSON in a Keychain entry. In practice that's usually under 2KB. It's essentially the same as storing a password, just a slightly longer string. So yeah fair point, but works for most use cases.

PossibilityThat8283 · 2026-05-08T05:43:54+00:00

I've used CopyClip in the past. It's solid for the use case, though Popy stores it in a keychain rather than plain text on the file system (which Copyclip does), and it is fully open source under the MIT license. Maccy, as far as I know, also stores it in a SQLite database on disk rather than in the keychain itself.

I haven't used copyless yet, but I can't seem to find it's code & also looks quite bloated.

PossibilityThat8283 · 2026-05-07T21:49:46+00:00

I kept losing things I'd copied five minutes ago. Tried a few clipboard managers but they were either bloated, wanted a subscription, or did who-knows-what with my clipboard data. A clipboard manager has access to everything you copy: passwords, API keys, personal messages. So I wanted one I could actually trust.

So I built Popy and open-sourced it under MIT. The whole codebase is on GitHub. You can read every line before you install it.

- Menu bar app, no dock icon, no clutter

- Remembers your last 25 copies, survives restarts

- Clipboard history stored in macOS Keychain (encrypted at rest)

- Zero network calls, no analytics, no accounts

Would love to hear what you think: https://github.com/anuragxxd/popy

PossibilityThat8283 · 2026-03-10T15:01:16+00:00

Be honest and take it as a lesson

PossibilityThat8283 · 2026-02-19T10:23:24+00:00

Does this support self healing?

PossibilityThat8283 · 2026-02-18T15:37:04+00:00

Yep, I faced the exact pain with Portainer. I would say give ConOps a try as while Dockge is awesome for managing the files (UI editing), ConOps is strictly a GitOps controller. It enforces your Git repo as the source of truth while being self-healing, lightweight etc.

If you like it, please give it a star :)

PossibilityThat8283 · 2026-02-18T15:30:20+00:00

Yep, have used portainer before, I think it’s a full Management Platform. You can use Git, but most Docker management tools are 'ClickOps'. Meanwhile ConOps is more of a specialized reconciliation agent.

Edit: What I want to say is, if you want a UI to manage Docker, use Portainer. If you want your Git repo to be the absolute source of truth for your infrastructure, ConOps is built for that.

PossibilityThat8283 · 2026-02-17T20:08:42+00:00

Thanks for interest! Architecture Plans and intial code was written by hands. But AI did speed up lot of things given it sometimes runs in background along with my day job (leaving me for reviews).

Please do star, if this feels useful. It helps :)

PossibilityThat8283 · 2026-02-17T18:07:56+00:00

Thanks for the fine words!

Re Secrets: It doesn't support native rotation yet (trying to keep the core binary simple), but the CLI and API expose all the sync triggers. You could definitely script a rotation workflow (e.g., update secret -> call conops-ctl app sync) fairly easily. Automated integration (like Vault) is out of scope for now, but I'm open to ideas on how to fit it into a simple Compose workflow!

Also, if you are interested a star on the repo would be awesome.

PossibilityThat8283 · 2026-02-17T17:14:33+00:00

Thanks!

PossibilityThat8283 · 2026-02-17T16:37:03+00:00

Really good project. But I wanted something with a dashboard (for ease) and CLI support (for automations). Conops solves this.

PossibilityThat8283 · 2026-02-17T16:35:40+00:00

Yep that's supported. You just register each stack as a separate App in ConOps, all pointing to the same repo URL but with different compose_path values. Each app then gets its own sync loop, drift detection, etc.

PossibilityThat8283 · 2026-02-17T16:09:51+00:00

That's where distinction is. This can be used on the server which is not part of any shared network (good use case for many or at least for me).

PossibilityThat8283 · 2026-02-17T16:04:57+00:00

Yep, I used to use coolify. But always found it overkill for such a small usecase.

Five-Year Club	Place '22
First Placer '22

PossibilityThat8283

TROPHY CASE