
Every-Turn HTTP 400 on ANTHROPIC_BASE_URL Is Not a Dead Gateway
A wall of HTTP 400s on a named Claude Code base URL is a schema reject, not a status outage. Print the 400 body, the named URL, and the named CLI pin before you page the gateway.
16 posts tagged with #Change-Control

A wall of HTTP 400s on a named Claude Code base URL is a schema reject, not a status outage. Print the 400 body, the named URL, and the named CLI pin before you page the gateway.

A remote or headless row that says waiting for your input is not done. Open the agent list, split Needs input from Working, and name who owns the CLI pin.

When import.meta.url fails on a Worker, Node.js APIs are already on. Name who owns the compat-flag list before the coding agent flips the wrong switch.

When a managed allow-list cannot be read, Claude Code now admits nothing. Classify the block, name who owns the file, then resume the coding agent.

A failed Cloudflare CLI login is a requested-scope list, not a status page. Copy the unknown scope, name who owns the CLI pin, then resume the coding agent.

An Organization policy line on /status can explain a miss. It does not prove the fleet policy loaded. Read claude doctor, name the proxy owner, then resume coding.

GitHub Issues are off on most Laravel packages. The ticket is a pull request that documents the bug, with a named owner. laravel/framework Issues stay on.

GitHub CLI’s Linux signing key expires Saturday 5 September 2026. Last night’s green apt update is not a trusted keyring. Name the owner of the image before the next CI layer runs apt.

A Copilot content exclusion is a policy row. App and CLI now honor it. Agent chat in the editor still can. Name the owner of the list and of the surface before you call a secret recovered.

GitHub now prints a ready-to-approve assessment on every Copilot review. That line is a note. The admin switch that turns it into a required approval is off by default. Keep it off.

A ranked cheat-sheet of five desk rules from this week: who pins the model, what .gitignore does not lock, who merges, who retries, and who still reads the diff.

A green chart lockfile is not permission to add ECharts beside ApexCharts. Name a rollback owner and one failing chart fixture before anyone ships a second visualization stack.

Chat said done is not recovered. I wait for a file on disk, a job log that names why the run stopped, and one fail-once restart from the last good commit.

TanStack Table 9.0.0-beta.64 honors explicit global-filter opt-in. That is pilot hygiene, not permission to unpin stable 8.21.3. Here is the gate list before a Vue admin table leaves the spike branch.

shadcn-vue 2.8.1 looks like a quiet patch until registry entries, icon maps, message-scroller gutters, and number-field styles hit a real admin surface. Treat the lockfile bump as a release decision with an owner, smoke list, and rollback.

Treat repository instructions for coding agents as a governed change-control system: owned, reviewed, scoped, evidenced, and reversible.
Also see: #Coding-Agents #Change-Control #Laravel #Vue #Code-Review
Type at least 2 characters to search.