I was already turned off by their decision to remove support for fzf, which I use everywhere else. I'm done.

I’m not sure what you mean here - we never supported fzf, other than a super early prototype in like 2021

This release actually adds support for nucleo, which matches with the same algorithm as fzf and was a common request

	▲	evandrofisico 3 hours ago \| parent \| next [-]
		About the "ai", the announcement is very vague. Is this incorporating a local model on device, something running on your infrastructure or a third party model like Claude? Because to me nowadays adding AI on anything usually means higher running costs equals sooner or latter enshittification.
	▲	mpalmer 3 hours ago \| parent \| prev [-]
		Hey, thanks for responding. I guess I used the prototype then. Definitely don't remember anyone saying "this is a prototype" at the time, so I took the product at face value, and part of the reason I chose it was the fzf support. I'm sure I recall some unhappy GitHub issues about the shift away... And the algorithm isn't the value prop for me, not by a long shot. fzf's customizability takes the cake. And now the overall product is way too big and feature-ful for me. I want simple, unix-y software that clicks together like Lego. You should be proud of the project's success for sure, it's just not for me!