The question is whether what makes it useful is actually being in the terminal (limited, glitchy, awkward interaction) or whether it's being able to run next to files on a remote system. I suspect the latter.
Eh, I can't see how your comment is relevant ti the parent thread. Creating a CLI in Go is barely more complicated than JS. Rust, probably, but people aren't asking for that.
They wrote the CLI "GUI" in React using ink, which is all JS-only. I don't know what the Golang way of doing this would be, but maybe it's harder if you want the same result.
There are many GUI building libraries in Go. Sure, you wouldn't be writing JSX (and I agree it's an interesting idea), but it doesn't mean it's more any work to get things rendered in a terminal with other approaches, especially with these AI assistants to help you finish the boring parts.