Google Workspace

Justin Poehnelt, a senior devrel engineer, published an open-source Google Workspace CLI under the company's own GitHub org, wearing Google's logo and brand colors. It hit 20k+ stars and #1 on HN. He says legal grilled him over the branding, and the deeper fear was what agents meant for Workspace.

A former Google Chrome engineer in the thread complicated the cheering: publishing under official Google orgs was routine, but shipping something that looks like an official product without sign-off is the kind of lapse that gets you walked out.

Open admin.google.com in Firefox and a security banner appears: secure your device, download Chrome, sign in with your work account. No technical reason was visible for the demand.

The blog's author turned up in the thread to confirm he is the admin, has never enabled Identity-Aware Proxy, and is on Workspace Business Plus, where Google's Context-Aware Access browser lock isn't even available. So what is triggering it?