Apparently you use it with iterm2 or whatever terminal you want...on a mac.

And I think it's an interesting idea to move the autocomplete out of band where it doesn't write to the same window where my work is (if I were on a mac), especially if it's still keyboard driven as they say.

But I still wouldn't touch this for other reasons.

I don't see any justification for this being proprietary.

There are already decades old autocoplete in most shells and the enhacement concept that this brings is just not that special that it deserves putting up with having to install proprietary binaries, being limited to their mac-only platform support, tolerating their data collection, and of course whatever their licensing arrangement is or will be.

It's not a bad enhancement idea, it just seems like it's barely a little spiff-up over ordinary bash completions.

Ordinary completions are already a flexible system that you can customize to do quite fancy things if you wanted. They already execute commands to generate output. It's a trivial addition, conceptually, to feed that output into any of the many xdialog-alikes instead of directly to stderr. This is a little slicker that literally just that, but not by much.

And the existing shells are already on all platforms not just mac, and fully open source, and don't have any telemetry or client/server architecture, and so are the xdialog-alikes, and so are the autocomplete definitions.