I see justinwp is commenting here… Justin, people are asking questions that you’re not replying to. Sorry, but it’s pretty disingenuous to tweet your story and post it here, but then refuse to answer requests for more info.

> I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace.

Seems to me your management chain was thinking “Why the hell is someone on our team releasing a vibe-coded CLI that’s branded to look like an official API, when we’re 2 weeks from announcing the actual CLI??” If you didn’t know there was an official CLI in the works, that’s one thing, but if you did know then that’s pretty shitty to your teammates in Workspace and bad for users who would adopt one CLI (thinking it’s official) just to then see another one 2 weeks later.

Still, I would expect a talking-to and not an actual firing… but who knows what actually happened since you’re not responding to anyone. :shrug:

▲

cute_boi 4 hours ago | parent [-]

The read me clearly says "This is not an officially supported Google product.". I am not getting what you want to imply here and what you expect him to reply here.

▲

khazhoux 3 hours ago | parent [-]

It's other people on this thread that had questions, more than me.

I'm not really implying -- I'm stating that I don't think his management chain was "afraid of being disrupted", but that they were pissed that one of their own team members released a product with Google branding that was the same thing they were about to announce in 2 weeks. It was poor judgement. Not worth a firing, though, in my opinion.

	▲	justinwp 29 minutes ago \| parent [-]
		> they were about to announce in 2 weeks Market validation can change roadmaps. As I stated on Twitter/X, CLIs for agents was not a very interesting thing outside a small group earlier in 2026.