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

301–310 of 316 posts

Re: Google Workspace CLI

#301

Post by grantcarthew »

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.

Yes, Atlassian's CLI support is shocking.

This is for Confluence. Markdown all the way:

https://github.com/grantcarthew/acon

Jira, same, markdown all the way:

https://github.com/grantcarthew/ajira

Other agent tools:

https://github.com/grantcarthew/homebrew-tap

Re: Google Workspace CLI

#302

Post by rendaw »

greymalik wrote: post #239
d4rkp4ttern wrote: post #236

Related, I often work with markdown docs (usually created via CLI agents like Claude Code) and need to collaborate with others in google docs, which is extremely markdown-unfriendly[1], so I built small quality-of-life CLI tools to convert Gdocs -> md and vice versa, called gdoc2md and md2gdoc: https://pchalasani.github.io/claude-code-tools/integrations/... They handle embedded images in both directions. There are si…

Paste from markdown (Chrome only) works _really_ well for me. What are the extra steps you’re running into?

After reading a comment here about how google docs had awesome markdown handling (I didn't know it supported it at all) I tried it out and it was bad to the extent that I don't think I'll use it again. I can't remember everything, but for instance it kept the syntactic newlines that should be swallowed during rich text conversion and IIRC it had issues with code too.

And then you have to edit it thereafter with their WYSIWYG editor. I was hoping there was an actual "markdown mode" where I could avoid getting into wars about whether this bullet point is in a new list or part of the previous list, etc.

IIRC there's no way to get markdown back out either, once you've realized you made the wrong choice.

Re: Google Workspace CLI

#303

Post by rendaw »

csomar wrote: post #112
mountainriver wrote: post #53

Earlier quoted context omitted.

Doesn’t this seem excessive over just using rust’s cross platform builds?

There's no such thing as a truly "cross-platform" build. Depending on what you use, you might have to target specific combinations of OS and processor architecture. That's actually why WASM (though they went with WASI) is a better choice; especially for libraries, since anyone can drop it into their environment without worrying about compatibility.

I think GP's point is that instead of having 3 target-specific rust-built binaries, they have 3 target-specific node binaries running rust-built wasm plus wrapper code.

Re: Google Workspace CLI

#305

Post by tianzhou »

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…

Good stuff. I added to the latest star-history.com issue https://www.star-history.com/blog/ai-ui-irrelevant

Re: Google Workspace CLI

#306

Post by ksri »

lewisjoe wrote: post #293
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…

Excellent project! I see that the agent modifies the google docs using an interesting technique: convert doc to html, AI operates over the HTML and then diff the original html with ai-modified html, send the diff as batchUpdate to gdocs. IMO, this is a better approach than the one used by Anthropic docx editing skill. 1. Did you compare this one with other document editing agents? Did you have any other ideas on how…

re. comparing with other editing agents - actually, I didn't find any that could work with google docs. Many workflows were basically "replace the whole document" - and that was a non-starter.

re. what happens if its a big book - each "tab" in the google doc is a folder with its own document.xml. A top-level index.xml captures the table of contents across tabs. The agent reads index.xml and then decides what else to read. I am now improving this by giving it xpath expressions so it can directly pick the specific sections of interest.

Philosophically, we wanted "declarative" instead of "imperative". Our key design - the agent needs to "think" in terms of the business, and not worry about how to edit the document. We move all the reconcilliation logic in the library, and free the agent from worrying about the google doc. Same approach in other libraries as well.

Re: Google Workspace CLI

#307

Post by eudiwjfie »

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…

[dead]

Re: Google Workspace CLI

#309

Post by eudiwjfie »

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…

[dead]

Re: Google Workspace CLI

#310

Post by mogili1 »

heinrichhartman wrote: post #180
mogili1 wrote: post #157

I was excited to see this but all of that went away when I realized you need to create an app in GCP to use it. Can't really expect non technical users to set this up across the company.

Can someone explain to me, why Google can't (or does not want to) implement the same auth flow that any other SaaS company uses: # API Keys in Settings 1. Go to Settings -> API Keys Page 2. Create Token (set scope and expiration date) # OAuth flow 1. `gws login` shows url to visit 2. Login with Google profile & select data you want to share 3. Redirect to localhost page confirms authentication I get that I need to co…

They definitely can, even gcloud cli can authenticate without needing to create a oauth app.
Post reply on HN