Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Workspace CLI

github.com

Post reply on HN
Print view View original

91–100 of 316 posts

Re: Google Workspace CLI

#91

Post by gjs278 »

nozzlegear wrote: post #88
laalshaitaan wrote: post #60

[flagged]

Is this comment AI generated? I don't like to accuse people of generating comments, but looking at your comment history, almost all of them fit this pattern of a single paragraph with "LLM-isms", this one included (i.e. "the X angle here is real -").

[dead]

Re: Google Workspace CLI

#92

Post by jitl »

mmaunder wrote: post #57

Google really know how to screw up a product experience. npm install -g @googleworkspace/cli gws auth setup { "error": { "code": 400, "message": "gcloud CLI not found. Install it from https://cloud.google.com/sdk/docs/install ", "reason": "validationError" } } Which takes you to... https://docs.cloud.google.com/sdk/docs/install-sdk Where you have to download a tarball, extract it and run a shell script. I mean how ha…

gcloud cli will probably also require you to make a Google Cloud project and stuff by clicking around their godforsaken webui. hopefully they streamlined that, it took me a long time to figure out when i wanted to write some JS in my spreadsheet

Re: Google Workspace CLI

#94

Post by 22c »

tedk-42 wrote: post #5

Haha in the world of AI/MCPs, all of a sudden we have a push for companies to properly build out APIs/CLI tools.

I noted something similar a few weeks ago. Companies are finally putting APIs in front of things that should have had APIs for years!

Re: Google Workspace CLI

#95

Post by virgildotcodes »

God, getting this set up is frustrating. I've spent 45 minutes trying to get this to work, just following their defaults the whole way through.

Multiple errors and issues along the way, now I'm on `gws auth login`, and trying to pick the oAuth scopes. I go ahead and trust their defaults and select `recommended`, only to get a warning that this is too many scopes and may error out (then why is this the recommended setting??), and then yeah, it errors out when trying to authenticate in the browser.

The error tells me I need to verify my app, so I go to the app settings in my cloud console and try to verify and there's no streamlined way to do this. It seems the intended approach is for me to manually add, one by one, each of the 85 scopes that are on the "recommended" list, and then go through the actual verification.

Have the people that built and released this actually tried to install and run this, just a single time, purely following their own happy path?

Re: Google Workspace CLI

#97

Post by candiddevmike »

jitl wrote: post #93
hoppp wrote: post #90

Earlier quoted context omitted.

Google will slowly win at the AI game. They got everything going, lots of free usage and they are keeping it real, unlike openAI that rides a hype train

yeah just like they’ve slowly won at cloud over AWS and Azure. oh wait

I mean, they are? GCP usage/revenue is growing faster than AWS and Azure. Mostly driven by Gemini pushing folks onto the platform and them deciding "why not move everything else too".

Re: Google Workspace CLI

#98

Post by mindwok »

wonderfuly wrote: post #62

Why cli instead of just HTTP API doc? The agent can use curl or write code to send requests.

They already have a HTTP API, but the real reason is that CLIs are emerging as the most ergonomic way for the current wave of AI agents to do stuff. There's a few benefits over APIs:

- No need to worry about transport layer stuff at all, including auth or headers. This is baked in, so saves context.

- They are self describing with --help and then nested --help commands, way better than trying to decipher an OpenAPI spec. You usually don't even need an agent skill, just call the --help and the LLM figures it out.

Re: Google Workspace CLI

#99

Post by jitl »

virgildotcodes wrote: post #95

God, getting this set up is frustrating. I've spent 45 minutes trying to get this to work, just following their defaults the whole way through. Multiple errors and issues along the way, now I'm on `gws auth login`, and trying to pick the oAuth scopes. I go ahead and trust their defaults and select `recommended`, only to get a warning that this is too many scopes and may error out (then why is this the recommended set…

i had to do all that the last time i wanted to do a little js in my google sheets. when i saw their quick start required gcloud already set up, i decided not to bother trying this out. idk why google makes something that should take 15s (clicking “ok” in an oauth popup) take tens of minutes to hours of head scratching.
Post reply on HN