211–220 of 316 posts
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 have always said that if we had done for developers what we are doing for agents the whole world would have been a much better place.
But saying "it's for AI" is a corporate life hack for you to get permission to build said better tooling... =)
Also, what I find fascinating is that the repo was initialized 3 days ago so it seems it's still a work in progress.
> Disclaimer
> Caution
> This is not an officially supported Google product.
Feel like this should be at the top of the README - not the bottom > Disclaimer > Caution > This is not an officially supported Google product.
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…
Interesting post from the main contributor about this (at least I assume it’s what he’s referencing) https://justin.poehnelt.com/posts/rewrite-your-cli-for-ai-ag...
Earlier quoted context omitted.
Most people aren't going to have npm installed though. Nobody outside of web devs uses it.
If you had to pick one package manager that was most likely installed across all the different user machines in the world, I'd say npm is a pretty good bet.
I'm curious why `npm` is used to install a `rust` binary?
I found that strange as well. My guess is that `npm` is just the package manager people are most likely to already have installed and doing it this way makes it easy. They might think asking people to install Cargo is too much effort. Wonder if the pattern of using npm to install non-node tools will keep gaining traction.
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.