A new Sonnet model, a runtime boundary for agents, and a GitHub Actions cutoff land today.
- Anthropic releases Claude Sonnet 5.5.
- NVIDIA pairs OpenShell with a BlueField watchdog.
- GitHub Actions blocks old self-hosted runners today.
- New York City hears four AI firms on 5 October and subpoenas SpaceXAI.
- The MCP Python SDK can send OAuth secrets to a server-chosen login service.
AI
Anthropic releases Claude Sonnet 5.5
Anthropic announced Claude Sonnet 5.5 on 28 September. Anthropic says it generates output 30%+ faster than Sonnet 5, keeps list price at $2 per million input tokens and $10 per million output tokens, and in Anthropic’s testing costs up to 30% less per task. Anthropic says it is on Amazon Web Services, Google Cloud, and Microsoft Azure. The model page lists a 1-million-token context window and the id claude-sonnet-5-5. GitHub says the model is generally available in Copilot, with a gradual rollout, and that Business and Enterprise tenants receive it unless an admin has turned off the default or this model. Anthropic says a request that turns thinking off has to use between_tools before it can move to Sonnet 5.5.
This week. Where a Sonnet 5 request disables thinking, set that setting to between_tools, then rerun those prompts on claude-sonnet-5-5 before you change a production model id.
Architecture
NVIDIA pairs OpenShell with a BlueField watchdog
NVIDIA announced the Open Agent Safety Platform on 28 September. NVIDIA says OpenShell, now broadly available, is an open-source runtime boundary for agents on CPUs, including Arm and Intel hosts, and that NVIDIA Sentry is an out-of-band watchdog on BlueField-4 DPUs that can quarantine an agent in milliseconds. The developer post the same day describes OpenShell 0.1.0 as enforcing file, process, and network limits outside the agent, including inspected HTTP, GraphQL, and MCP calls.
This week. If an agent can call tools or the network, put OpenShell 0.1.0, or an equivalent boundary outside the model, in front of it. Treat Sentry as a BlueField-4 reference design, available only where that DPU already sits on the path.
Platforms
GitHub Actions blocks old self-hosted runners today
GitHub says full enforcement of the self-hosted runner minimums on GitHub Enterprise Cloud begins 29 September. That date is today. Runners below 2.329.0 cannot register or reregister. GitHub says a higher minimum, which this note does not number, stops already-registered runners from running jobs. GitHub Enterprise Server is outside this change. Enforcement for Enterprise Cloud with data residency began 31 July.
This week. Upgrade every Enterprise Cloud self-hosted runner to at least 2.329.0 now, and use the runner version deprecation API named in that changelog to find the higher build that may still register and still will not run jobs.
Policy
New York City hears four AI firms on 5 October and subpoenas SpaceXAI
The Council said on 28 September that Anthropic, OpenAI, Google, and Meta will testify under oath at a Committee of the Whole hearing on 5 October. Meta agreed without a subpoena. OpenAI, Google, and Anthropic agreed after the Council warned that subpoenas would go out on 28 September. Speaker Julie Menin issued a subpoena to SpaceXAI, which had not responded. The release names a whistleblower incentive, a private right of action for New Yorkers harmed by AI agents, and third-party validation requirements among the bills at that hearing.
This week. If you offer or run an AI system in New York City, read those three proposals before 5 October and mark which products would need a third-party validation or a human stop.
Security
MCP Python clients can send OAuth secrets to the wrong login service
Advisory GHSA-qx49-fqc8-xw99, published 28 September, says a malicious MCP server can choose the authorization server that receives a client’s client_secret, authorization code, and PKCE code_verifier. The maintainers score the unattended providers 7.5. Versions 1.9.1 through 1.29.1 and 2.0.0 through 2.1.1 are affected. The fixes are 1.30.0 and 2.2.0. Servers built with the SDK, stdio clients, and clients that attach their own tokens are outside the advisory.
This week. Upgrade the 1.x line to 1.30.0 or the 2.x line to 2.2.0. If you use ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider, pass issuer= as well. The advisory says the upgrade leaves those two providers unbound until you do. Clear stored OAuth client registrations once.
Link of the day
Anthropic on Claude Sonnet 5.5: Claude Sonnet 5.5.
Leave a Reply