The new "daemon-fuzzy" mode uses a new fuzzy matcher powered by Nucleo and might be what you're looking for

it seems indeed better in some ways, but the scoring is still way off,

for example, for my second criteria:

> - works on partial matches (e.g. inputting "ma in" matches ("make install", "cd main")

typing "ma in" I would expect "make install" to come before "cd main" to come before (what's currently the very first hit) "cd Binaries/Multimedia".

I'm now reading about https://docs.atuin.sh/cli/configuration/config/?h=fuzzy+daem... while not managing to really get what would seem natural. Sigh.

I'd start with setting the combined frecency score to 0 and testing out how the raw fuzzy scoring does. Then if you find you're having trouble finding recent or frequent commands, you can adjust from there. If you can't find a configuration that feels good, please feel free let me know in an issue.

I really like this idea — might give an implementation a shot

The backend server, Atuin Hub (https://hub.atuin.sh), isn't currently open source, but the open source desktop app can still connect to it. We also support offline workspaces if you prefer using Git or another VCS to manage and collaborate on runbooks, rather than using Atuin Hub.

Following the Obsidian model, which I love and support. Give folks the best part of the product, offer a paid option to enhance it, but allow folks to use alternatives as first class options.

Thank you for the candid response. So team collab without the hub is still possible, but the desktop client becomes a viewer for a hit repo. Am I understanding that correctly? The advantage of the hub is that that is all handled under the hood?

A viewer and editor, but essentially yes — the Hub handles sharing and collaboration for you, as well as realtime collaborative editing and a few other features (and likely a few more to come). We want the Hub to feel like the most frictionless way to collaborate on runbooks, but we understand that some folks don't want host their runbooks with a third party, and sometimes fitting into an existing VCS workflow makes the most sense.

Candid responses like this are an excellent way to earn good will, thank you!

Thanks for this interesting (and very entertaining) talk! The phrase "it's hard to keep a mental model of a system while consuming these actions" really sums up what's nice about using flux. With the right developer tooling, visualizing past (and even potential future) state changes becomes much more trivial.