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

271–280 of 316 posts

Re: Google Workspace CLI

#271

Post by neuronexmachina »

sothatsit wrote: post #216
ksri wrote: post #196

I have been working on extrasuite ( https://github.com/think41/extrasuite ). This is like terraform, but for google drive files. It provides a git like pull/push workflow to edit sheets/docs/slides. `pull` converts the google file into a local folder with agent friendly files. For example, a google sheet becomes a folder with a .tsv, a formula.json and so on. The agent simply edits these files and `push`es the change…

We have been using something similar for editing Confluence pages. Download XML, edit, upload. It is very effective, much better than direct edit commands. It’s a great pattern.

I've found that usually works ok, but currently tends to timeout with the Atlassian MCP when trying to do updates on large Confluence pages: https://github.com/atlassian/atlassian-mcp-server/issues/59

Re: Google Workspace CLI

#272

Post by d4rkp4ttern »

chrisweekly wrote: post #270
d4rkp4ttern wrote: post #266

Earlier quoted context omitted.

Images wouldn't work though, right? I'd be amazed if that worked. My CLI tools handle those.

Obsidian has become almost an operating system for working with markdown. Its Live View / Edit mode is excellent (WYSIWYG) and its ability to accept pasted content and handle it appropriately is good and getting better. Its plugin/extension ecosystem is robust (and has a low barrier to entry), and now that it has a CLI I expect to see an acceleration of clever workflows and integrations. No affiliation, just a very h…

I’m intrigued by their recent CLI release as well. I’ll have to check out the markdown edit support too, thanks

Re: Google Workspace CLI

#273

Post by anthonypasq »

fergie wrote: post #175

> gws doesn't ship a static list of commands. It reads Google's own Discovery Service at runtime and builds its entire command surface dynamically. What is the practical difference between a "discovery service"+API and an MCP server? Surely humans and LLMs are better off using discovery service"+API in all cases? What would be the benefit of MCP?

theres a lot more to the MCP spec than tool calling

Re: Google Workspace CLI

#274

Post by anthonypasq »

fergie wrote: post #175

> gws doesn't ship a static list of commands. It reads Google's own Discovery Service at runtime and builds its entire command surface dynamically. What is the practical difference between a "discovery service"+API and an MCP server? Surely humans and LLMs are better off using discovery service"+API in all cases? What would be the benefit of MCP?

theres a lot more to the MCP spec than tool calling, and also people ignoring the fact that remote mcps exist

Re: Google Workspace CLI

#275

Post by oofbey »

Yet another way Google might decide you’ve violated their ToS and cut you off from your entire digital life without warning or recourse.

Sounds handy. But use at your own risk.

Re: Google Workspace CLI

#276

Post by chrisweekly »

a_t48 wrote: post #119
nikanj wrote: post #76

Earlier quoted context omitted.

This is about eight years old. The python situation has mostly gotten worse since https://xkcd.com/1987/

What? It’s much much better now, you can just use uv. Yeah, it’s yet another package manager, but it does it well.

Or go up a rung or two on the abstraction ladder, and use mise to manage all the things (node, npm, python, etc).
Post reply on HN