A fast day for defenders and developers: Anthropic’s cautious rollout of Project Glasswing is the clearest sign yet that AI is changing both how we find bugs and how we must patch them. At the same time, platform tooling and industrial supply chains are quietly reshaping who can actually productize those models.

Top Signal

Anthropic — Project Glasswing: An initial update

Why this matters now: Anthropic’s Project Glasswing shows Mythos-class models already scaling vulnerability discovery, meaning security teams and maintainers face an immediate operational shock: far more finds, far faster triage needs.

Anthropic published an initial update on Project Glasswing describing a pilot where the Mythos Preview model helped partners surface thousands of issues. Anthropic reports Mythos estimated over 6,000 high‑ or critical‑severity issues in a sampled set of open‑source projects, and a partner validation sample returned a ~90.6% true‑positive rate. Those are headline numbers, and Anthropic is careful to stress partners, controls and limited distribution.

"Finding them in the first place has become vastly more straightforward with Mythos Preview," Anthropic writes, adding that no company has built safeguards strong enough for broad release.

Operationally, the numbers force a rethink: triage, disclosure coordination, and patch capacity are the chokepoints now—not raw detection. Open‑source maintainers already complain about overflow from automated scanners; Mythos‑level throughput threatens to swamp those human processes unless teams invest in faster triage, improved exploit-priority filters, or coordinated vulnerability-handling networks.

For defenders, the immediate playbook is clear: adopt comparable tooling for prioritized scans, harden defaults in critical services, and budget for rapid-change windows. For policymakers and risk teams, Anthropic’s approach raises governance questions about who gets access, who audits findings, and how to avoid a dual‑use arms race between defensive and offensive discovery.

Source: Anthropic's Project Glasswing initial update.

AI & Agents

DeepSeek permanently cuts prices 75%

Why this matters now: DeepSeek’s announced permanent 75% price cut could materially reduce the compute cost of advanced models for small teams and startups, shifting economics for self‑hosted and cloud workflows.

DeepSeek has said a temporary promotion will be followed by a permanent three‑quarter price reduction, a move discussed on r/singularity and Chinese social channels. If the cut reflects sustainable unit economics, it can democratize access to high‑quality inference and accelerate adoption of more expensive agent patterns. But the critical follow-up is independent benchmarks and safety comparisons to incumbents: lower cost only upends the market if quality and guardrails are comparable.

(Reporting thread discussed at the original Reddit post image.)

Markets

Meta launches Forum; Reddit stock reacts

Why this matters now: Meta’s new Forum app repackages Facebook Groups into a Reddit‑like feed—investors feared it could drain casual engagement and ad dollars, prompting a near‑term hit to Reddit’s share price.

Meta quietly released Forum for iPhone, surfacing Groups in a single feed and adding an in‑product AI “Ask” feature. Traders and analysts flagged the move as a plausible competitive pressure against Reddit’s casual traffic, which can matter for ad monetization even if core communities remain loyal. The product’s success will hinge on trust, anonymity options, and whether advertisers follow the migration.

Sources: App Store listing and related coverage summarized in Reddit threads.

World

Consumer sentiment slides as Strait of Hormuz disruption hits prices

Why this matters now: U.S. consumer sentiment fell to fresh lows as energy disruptions tied to the Iran war pushed gasoline and inflation expectations higher—an immediate constraint on policymakers and markets.

The University of Michigan’s sentiment index slid further in May; year‑ahead inflation expectations are rising and long‑term expectations ticked up, increasing the risk that temporary supply shocks become embedded inflation. That complicates Fed policy and firms’ planning even if the geopolitical event itself resolves.

(See recent coverage and the University of Michigan survey brief.)

Dev & Open Source

Deno 2.8 — a major compatibility and tooling push

Why this matters now: Deno 2.8 significantly narrows the practical gap with Node.js—better npm compatibility, faster installs, and new dev ergonomics that make Deno a real candidate for teams seeking tighter security and TypeScript‑first workflows.

Deno’s v2.8 release is a developer‑grade upgrade: unprefixed package names now resolve to npm by default, Node test‑suite compatibility climbed from ~42% to 76.4%, cold npm installs are multiple‑times faster, and new commands (deno audit fix, deno ci, deno pack) land real ergonomics for reproducible builds and security work. For teams weighing a switch from Node or Bun, the release reduces migration friction while preserving Deno’s permission model and integrated tooling.

"deno ci" and "deno audit fix" are small features with outsized operational effects—fewer surprises in CI and a practical path to patch vulnerable dependencies.

If your stack depends on long-lived Node modules, Deno 2.8 removes many historical blockers. Expect more teams to trial Deno in staging, especially where TypeScript, reproducibility, and tighter permission boundaries matter.

Source: Deno’s v2.8 release notes.

Antigravity 2.0 tops the OpenSCAD architectural LLM benchmark

Why this matters now: Google’s Antigravity 2.0 (Gemini 3.5 Flash) produced the best autonomous OpenSCAD recreation of the Pantheon—an encouraging sign that spatial code generation is moving from toy demos to practical CAD assistance.

ModelRift’s OpenSCAD benchmark used photographic prompts and asked agents to generate renderable parametric code. Antigravity stood out by searching for real architectural parameters and producing a coffered dome rather than ad hoc geometry. The work still needs a human in the loop for verification and precise tolerances, but it shows LLMs can now reason about repeated structures, radii and parametric patterns in a way that’s useful for hobbyists and engineers.

For engineering teams shipping physical parts, the takeaway is hybrid workflows: use an LLM to scaffold parametric models, then validate tolerances and run a final human review before prototype prints.

Source: ModelRift’s OpenSCAD LLM benchmark.

Microsoft pulls back Claude Code inside the firm

Why this matters now: Microsoft is moving engineers off Claude Code and toward GitHub Copilot CLI—an internal consolidation that highlights how token billing and vendor control shape which AI tools survive in large shops.

Internal memos report Microsoft winding down many Claude Code licenses and centralizing on Copilot CLI to better align with security, cost and integration goals. The shift underscores a recurring enterprise tension: teams will often pick the most productive tool, but corporate procurement and cost controls can override grassroots choices—especially where vendor control, telemetry and budget are involved.

Source: Coverage of Microsoft’s internal change summarized by The Verge.

In Brief

  • Deno 2.8 ships major Node compatibility and performance wins; teams migrating from Node or evaluating Bun should re‑test now. (Source: Deno blog)
  • Anthropic’s Project Glasswing reports thousands of finds in early pilots—triage capacity, not detection, is the bottleneck. (Source: Anthropic)
  • Antigravity 2.0 (Gemini 3.5 Flash) beat peers on a parametric OpenSCAD benchmark, pointing to practical gains for CAD workflows. (Source: ModelRift)
  • A small, human logistics story: shipping a laptop to a refugee in Uganda revealed how customs, courier rules and battery rules can turn a donation into a 42‑day ordeal. (Source: Notes by Lex)

Deep Dive

Why Japanese conglomerates still matter to modern supply chains

Why this matters now: Japan’s corporate model—cohesive, diversified firms with deep manufacturing know‑how—explains why niche, high‑precision parts for semiconductors still come from Japan, and why supply‑chain resilience can’t be replicated overnight.

David Oks’s long read on why Japanese companies do so many different things uses Toto (yes, the toilet maker) as a gateway to a structural explanation: cross‑training, lifetime employment norms, keiretsu‑style capital ties and long investment horizons let firms sustain loss‑making but strategically vital divisions (for example, advanced ceramics e‑chucks used in wafer handling). That organizational bundle produces tacit skills and production depth that Western, capital‑market-driven firms often can’t match quickly.

For tech leaders, the practical implication is straightforward: when you rely on esoteric suppliers for precision parts—e‑chucks, ceramic substrates, optical mounts—short-term sourcing switches are hard. Build relationships, fund dual sources where possible, and design products tolerant of supply hiccups. Policy-makers weighing industrial policy should also note: plant-level capability depends on corporate practices and hiring systems, not only subsidies.

Source: David Oks, “Why Japanese companies do so many different things” (longform).

Deno’s 2.8 release: what to do this quarter

Why this matters now: Deno 2.8 turns experimental curiosity into a plausible production option—teams should evaluate migration risk, CI reproducibility and dev tooling savings this quarter.

Conservative engineering teams can safely trial Deno 2.8 in a staging context: run a representative microservice, use deno ci to lock installs, and run existing Node tests under Deno’s improved compatibility. Measure cold‑start install times and audit/patch workflows; if your CI and security posture improves with minimal rewrite cost, Deno can reduce runtime complexity and tighten supply‑chain risk (fewer external build steps, a single integrated runtime).

Source: Deno’s v2.8 release notes.

Closing Thought

Anthropic’s Glasswing update is the clearest signal yet that AI isn’t just adding capability—it’s changing operational load. Defenders must treat detection as table stakes and invest in the human systems that turn findings into fixed software. At the same time, platform moves (Deno) and industrial deep‑tech (Japanese suppliers) remind us the economics of productization are still decided in toolchains, factories, and governance—where small changes cascade into big outcomes.

Sources

If you want, I can produce a short, shareable TL;DR thread or a checklist for engineering leaders to act on the Glasswing findings this week.