Removed gradient agent is the Important line in doctl 1.175.0

So doctl put v1.175.0 on the feed, dated September 25, 2026. We flagged it Important as a breaking change. Recency wants the tidy rename: knowledge bases move to doctl knowledge-base, and doctl gradient hides from public help. Fine. Those are the lines people screenshot when they skim a CLI note.

The line that matters, to the best of my understanding, is the Breaking changes block. This release removes the doctl gradient agent command tree (create, get, list, update, delete, update-visibility, list-versions, plus apikeys, route, and functionroute). Scripts using those paths will fail. Your AE forwards 1.175.0. A customer whose deploy job still shells out to doctl gradient agent list starts asking why CI went red. That is the product change you track when you sell next to DigitalOcean Gradient AI tooling, not the knowledge-base alias.

There is a migration table in the same note. doctl gradient knowledge-base becomes doctl knowledge-base (still works as a hidden deprecated alias with a warning for now). Inference paths under doctl inference stay as they were since v1.171.0. Kind of easy to paste the rename into a status update and sound thorough. Kind of useless when the partner ticket is the agent tree that is gone, not warned.

I keep almost filing doctl under "cloud CLI bump, ignore." Kind of the wrong habit when you sell into teams that automate Gradient agents from shell scripts. Tracking product change here means reading past the help-text cleanup and asking which line changes a partner ticket. Let's say the talking point is not "1.175 shipped a rename." It is doctl gradient agent is removed and scripts fail, then yes mention knowledge-base is top-level now and the old path warns until a later cut. We pull it into a uniform entry shape at /sources/doctl.updates. Same JSON as everything else. Recency still wants the tidy rename. Recency is not the removed agent tree.