@stacks

All good clipboard managers enable this workflow. With so many great options already available, why create another one?

Stacks is an experimental "tool for thought"

I think of my clipboard as "picking things up" to move them around or redirect them. In this sense, your system's clipboard acts as a strong proxy for your "locus of attention" when you're using a computer.

A clipboard manager, then, is a tool to capture and work with your "locus of attention." It ambiently captures your current tasks and work context.

Stacks is an experimental tool for tracking and manipulating your current context using pipes and filters. But that’s a lot to explain, so I usually just describe it as a clipboard manager.

UX disclaimer

A quick note on the user experience (UX): it’s fair to say it’s still a bit rough around the edges. If Stacks reaches a UX level similar to (neo)vim, I'd consider that a success. It’s pretty spartan and utilitarian, so being comfortable with the command line, or feeling adventurous, definitely helps.

Stacks is my personal "tool for thought" that I use as my daily driver. Eventually, I’d like Stacks to reach the polish of tools like Obsidian, but for now, the focus is on its experimental nature and the underlying event-sourcing store.

Give it a try!

If you're into experimental tools and are okay with a minimalist, utilitarian design, give Stacks a try-- I'd love to hear your thoughts!