Not for human use

gm legends, happy Wednesday.

Today: Google shipped a command line tool that isn't for you, a Mac app for everyone with nine Gmail accounts and one near-miss, and a synth you play with friends. Plus the forum on getting burned by platform APIs.

agents-cli is Google's new open-source CLI that takes an AI agent from demo to production, scaffolding, evals, deploy, and it's built to be driven by your coding agent rather than by you. It comes out of Elia Secchi's (@elia_secchi) day job helping teams ship agents on Google Cloud, where the demo takes an afternoon and the plumbing takes weeks.

🔥 Our Take: Google shipped a developer tool and the developer it's built for is Claude Code. Everything the CLI prints is structured for a model to parse, and the version a human can read is the fallback for when you're driving it yourself. Dipankar Sarkar explained in the comments why that matters: he once let an agent run a deploy CLI unattended, and it read the human-formatted errors, missed that the deploy half-failed, and cheerfully reported success. Every dev tool is about to grow an agent mode like this, and Google getting there first means your coding agent might pick your cloud provider before you do.

Orbit for Mac gives each of your Google accounts its own sealed room in one native 12MB Mac window, full Gmail, Calendar, and Drive, switchable with ⌘1 through ⌘9. It's built by Andrew Kwak, a man who runs nine Gmail accounts and finally snapped.

🔥 Our Take: You know that pause where you hover over your avatar to double-check which Gmail you're in before hitting send, because one time you didn't. Orbit makes that whole accident impossible, every account gets its own sealed room and ⌘2 is always work, ⌘3 is always the side project, so switching becomes muscle memory instead of squinting at tiny profile photos. It doesn't try to do anything Gmail in a tab can't, no unified inbox, no AI layer, just walls, which after nine accounts is apparently all Andrew ever wanted. Shift will sell you a subscription to a much heavier version of this idea, and it's hard to see why you'd keep paying it once a 12MB native app does the job.

Jamboree is a synthesizer that lives in your browser and lets your friends in too: everyone twists knobs on the same patch in real time, with live cursors and a chat box. Kartik Nair (@kartiknair) built it over a weekend because he wanted to make weird noises with his friends.

🔥 Our Take: Open this with your group chat and within a minute someone has found the worst sound imaginable and everyone is fighting over the filter knob, and that's the product, it's great. The old way of jamming remotely was one person screen-sharing Ableton while everyone else said "make it more spacey" from the couch, here everyone's cursors are on the same knobs at once, and when the noise accidentally turns into something good it exports as a SoundFont you can actually keep. Companies have tried to sell this exact feeling, Endlesss was the big one and it's gone, because jamming with friends refuses to become a subscription. A weekend project with no pricing page might just be the right shape for it.

Luke (@lukem121) is building an API that pulls data from 13 social platforms, and says the scraping was never the hard part. It's how differently every platform breaks: rate limits that change without notice, auth that expires silently, "structured data one week and a wall of JS the next." So he asked which platform has burned everyone else the most.

Everyone had a story. Reddit's API changes meant rebuilding from scratch, Facebook auth failed for one commenter without a single line of code changing, and Narek Keshishyan (@narek_keshishyan), who runs one app across three platforms, laid out the spread: Bluesky's API just works, Threads hides every useful read behind another OAuth consent screen, and Instagram gives you "a human in a browser or nothing."

The best reply came from Akbar B (@akbar_b), on the failure nobody monitors for: not the clean 403, but the endpoint that keeps returning 200 with quietly stale data, so your dataset rots for days before anyone notices. His rule: "Status lies; the payload doesn't."