OpenAI launched its Daybreak security initiative this week. Anthropic's Project Glasswing reached Day 38 without the public artifact it promised within ninety days. Both share partners — Cisco, CrowdStrike, Palo Alto Networks. Both pitch themselves as the answer to exactly the type of incident Vercel disclosed in April. Neither has said whether Vercel was a customer of either lab. [4] [5]

The paper's Friday account argued that Vercel's breach is now an AI-OAuth supply-chain story — the Context.ai OAuth route into Google Workspace and onward into Vercel's build pipeline made the consent-screen economy a production-infrastructure problem. The same day's piece on Glasswing as Day 38 without the promised public artifact named the silence. Daybreak's launch this week supplies the missing comparison.

The Vercel facts have not changed since April. Vercel's own bulletin describes the April 2026 incident, a Context.ai OAuth path that reached non-sensitive environment variables, and a continuing investigation. [1] Trend Micro's analysis named the supply-chain mechanism. [2] Push Security's later write-up traced the OAuth grant pattern across the Workspace boundary. [3] None of those accounts have been retracted or revised by the public timeline; the change is around them, not in them.

The Daybreak launch is the change. The New Stack and AI Business both treat Daybreak as a Glasswing mirror — same kind of vendor-capture move, similar partner roster, similar promise of defender access. [4] [5] AI Business's headline framed Daybreak as OpenAI's challenge to Glasswing. Neither piece closed the loop with Vercel. Neither lab has said publicly whether the Vercel customer environment in April was running Daybreak preview tooling, Glasswing partner instrumentation, or neither.

That silence is the artifact this piece adds. A vendor that pitches an OAuth-supply-chain security initiative and cannot answer whether a major OAuth-supply-chain incident customer was a paid relationship is not yet a vendor; it is an announcement. The April incident was the canonical case both initiatives describe in their launch materials. The April customer was a recognizable enterprise platform. The April mechanism — third-party AI app, OAuth grant, Workspace bridge, build-pipeline read — is the exact pattern Daybreak and Glasswing both market themselves against.

X has been quicker than the trades to draw the line. Security accounts have spent the week noting that Daybreak's partner list and Glasswing's partner list overlap heavily and that the overlap is a vendor-capture story before it is a defender-access story. The narrower observation is that the two largest AI labs are now signing the same security firms to similar consortia and asking the public to wait for evidence that the consortia change incident outcomes. The Vercel breach is the cleanest available test case. Neither has used it.

The mainstream version of this story is the announcement version. Daybreak launched. Glasswing exists. Both have partners. Both have promises. Both have ninety-day or similar evidence windows. The institutional version is the one that asks whether the announcements have changed any incident's actual mechanism. Vercel is not a hypothetical. It is a published bulletin with a Context.ai OAuth path through Google Workspace into a build pipeline.

The honest reader service is to hold three sentences at once. First, the April Vercel facts are settled and the bulletin is public. [1] Second, Daybreak and Glasswing are sold as the institutional answer to exactly that class of incident. [4] [5] Third, neither lab has confirmed or denied a Vercel customer relationship, and neither has produced a public artifact tied to the April mechanism. The third sentence is the news.

The next legitimate milestone is a public artifact from either initiative that names a remediated OAuth-supply-chain incident with the customer's consent. CISA could publish an advisory. The Linux Foundation could publish the Glasswing report Anthropic promised by July. OpenAI could disclose a Daybreak case study. Until one of those arrives, the marketing exceeds the evidence by a margin the press is too polite to mention.

The Vercel breach is now the unanswered question on two product pages, not just one bulletin page. That is the May 16 frame the paper carries forward.

-- THEO KAPLAN, San Francisco