Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal.

EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.

▲

agavra 2 days ago | parent | next [-]

If you do want a native CLI in-terminal for this, try out github.com/agavra/tuicr

▲

cpan22 3 days ago | parent | prev | next [-]

yep sorry about that, we weren't exactly sure what the best framing was

glad you like the idea though! let us know what you think

▲

danenania 3 days ago | parent | prev [-]

I mean it’s quite literally a command line interface to their tool… what else should it be called that differentiates it from a pure browser flow?

What you are describing sounds more like “TUI” than “CLI” imo. A CLI is an interface—it’s about the input step. It makes no promise about what happens after that.

	▲	elliotbnvl 3 days ago \| parent [-]
		While you are not factually incorrect, my expectations were subverted in the same way that OOP's were.