Daily · · Claude Code · 🌶️Nice to knowMild: nice to know Why: Fewer surprises in scheduled tasks
Claude Code flags extra connectors in /schedule
A scheduled task that quietly picks up connectors now gets called out.
Claude Code’s latest release warns in /schedule when a new cloud scheduled task gets connectors you didn’t ask for, and shows how to remove them.
What changed
Claude Code now asks before your account email leaves the machine. The same release adds a check before a web or shell tool call sends your account email address to the network, alongside the new /schedule warning about connectors you didn’t request.
Also in this release
- Agent SDK hook callbacks accept
onFailure: "block", so a callback that fails blocks the action instead of letting it run. - Admins on the Claude apps gateway get a cost report at
GET /, showing past spend over a date range in total, per developer, per day or per IdP group.v1/ organizations/ analytics/ cost - The Read tool no longer returns a “file unchanged since your last Read” stub, so reading an unchanged file again returns its content.
claude -pnow exits 1 with an error when a full disk or quota loses its transcript or~/.writes, instead of exiting 0.claude. json