Try building a CLI with a complex JSON as flags approach. :)

I just did the opposite and am seeing better results.

Claude was struggling to use the ‘gh’ command to reliably read and respond to code review line level comments because it had to use the api. I had it write a few simple command line tools and a skill for invoking it, instantly better results.

YMMV

You don't need to install all of them.

You don't need to use gcloud if you already have:

1. A GCP project (needed for OAuth) 2. Enabled APIs in said project

You can skip that setup if you already have the OAuth credentials.

There are many gotchas in this process and unfortunately there is no easy way to deal with the OAuth setup.

Yeah, still no way around this unfortunately.

Title is a little clickbait, but not really! :)

---

Human DX optimizes for discoverability and forgiveness. Agent DX optimizes for predictability and defense-in-depth. These are different enough that retrofitting a human-first CLI for agents is a losing bet.

Drive, Gmail, Calendar, and every Workspace API. Structured JSON output. 40+ agent skills included.

I recently formalized a `.agent/workflows/knowledge-extraction.md` to extract high-signal engineering patterns from Antigravity’s persistence layer to make them explicit and portable.

Use a rules file to change the Git identity for agents in your repository.