I’m honestly surprised something like this doesn’t already exist.

That makes me wonder if there’s a pitfall I haven’t discovered yet.

Is there a fundamental reason this hasn’t been built before?

They didn't even reviewed their own PR in the demo video :\

Thanks for sharing! I think your approach makes sense. Who are your clients if you don't mind?

I’m working on a product to tackle the same problem - keeping user-facing docs up-to-date as products evolve. I’m still early, currently building a proof of concept.

Would love to connect and exchange ideas. Feel free to reach out on LinkedIn: https://www.linkedin.com/in/bpetryshyn/

I have happily used the free Stats app for a couple of years now.

Hey iStat users, what makes the paid tool worth it for you?

Looks better, support weather, supports more sensors, more configuration options… But Stats is sufficient, I just use iStats for ages and it ask for little money ~two times in a decade.

I not only enjoyed it as a satire on the overstimulation problem but also learned that my compulsive-obsessive syndrome has a high correlation with overstimulation.

I'm currently hacking together a prototype of such a tool. The problem I noticed is that in CLI, commands are way less predictable than lines in code files, so such a tool will probably have a pretty low correct completion rate. However, there are clearly cases where it could be very helpful.

Thank you for the first comment and sorry for the broken formatting. I just improved it.

The existing solutions are tailored for website analytics and built around concepts like page views, clicks, sessions, etc. Some of them allow sending arbitrary events, but users still need to solve CLI-specific problems like reliable and non-blocking event delivery, user uniqueness, consent collection, and others.

I'd be happy to hear about people's experiences with using these platforms for CLI analytics.

In addition to what pancomplex mentioned, Posthog is not fully open-source. Their free self-hosted version has limited functionality and the paid self-hosted version is no longer supported [1] which makes me feel like I'm pushed to use their cloud offering.

[1]: https://posthog.com/docs/self-host

I'm maintaining Basti, an open-source AWS Bastion Host management CLI that lets you connect to RDS and other resources at almost no cost. Check it out: https://github.com/basti-app/basti

This project also inspired me to explore a commercial analytics solution for CLI applications — currently assessing if there's demand for it.

It looks interesting. Is the Basti EC2 instance deployed in a private subnet? Do you have a high-level diagram?

The diagram is available in the basti-cdk package. Probably, I have to make it more visible in the main README: https://github.com/basti-app/basti/tree/main/packages/basti-...

By default, the instance is deployed to a public subnet but any ingress traffic is not allowed by the instance's security group. This is needed for the instance's ability to connect to AWS SSM service (egress only).

The user can also deploy the instance to a private subnet but this would require them to manually ensure connectivity to the AWS SSM via NAT gateway, VPC endpoint or other means.