Today's digest · Friday, October 2

The 7 things in AI/dev today.

LiveNext issue at 7:00 CET
#1 / TODAY
Cloudflare Developer Platform·1 min·2d agoFREE

Agents, Workers - The best way to do MCP auth just got better: Workers OAuth Provider goes v1, with a new split API and full support for MCP 2026-07-28

Cloudflare's Workers OAuth Provider has reached v1, according to a changelog entry on the Cloudflare Developer Platform dated October 1, 2026. The release introduces a new split API and adds full support for MCP 2026-07-28. The changelog frames the update as an improvement to doing MCP authentication on Workers. The source describes the split API and MCP version support as the two headline changes accompanying the v1 milestone.

Developers using Workers OAuth Provider for MCP authentication can now rely on a v1 release with a split API and support for MCP 2026-07-28.

cloudflaremcpoauthworkers
developers.cloudflare.com
Agents, Workers - The best way to do MCP auth just got better: Workers OAuth Provider goes v1, with a new split API and full support for MCP 2026-07-28
Is sandboxing sufficient to contain rogue agents?
#2 / TOP STORY
LobstersFREE

Is sandboxing sufficient to contain rogue agents?

A post on the cryptography engineering blog, surfaced via Lobsters, asks whether sandboxing is sufficient to contain rogue agents. The item is framed as a question in its title and appears on the blog's index under the heading "A Few Thoughts on Cryptographic Engineering." The excerpt available to this digest consists of the page's title and embedded stylesheet markup, so no argument, evidence, or conclusion from the post itself is present in the source text.

AI coding agents leaked 13,000 screenshots, and nobody hacked them.
#3 / TOP STORY
The New StackFREE

AI coding agents leaked 13,000 screenshots, and nobody hacked them.

The New Stack reports that AI coding agents leaked 13,000 screenshots without any hacking taking place. According to the source, the exposure came from the agents themselves rather than from an attacker breaching a system. The story frames the incident around the volume of screenshots that escaped, not around an intrusion. The source-grounded consequence is that the leak is attributed to agent behavior, so the incident is described as an accidental exposure rather than a security breach.

aigest · daily

Get this every morning.

One email. The signal. Built for builders.

Free · Unsubscribe in one click · No trackers

// Worth knowing4 stories

The excerpt provides only page styling, so developers get no source-grounded detail on how the time-travel debugger records or replays agent execution.

agentsdebuggingdevcommunitycss
DEV Community24h ago2mFREE
// Yesterday11 stories