AI Digest — April 22, 2026

---

🔖 Project Releases

Claude Code

Latest: v2.1.117 (April 22, 2026 — 00:04 UTC)

The Tuesday-evening quiet broke seven hours after yesterday’s digest hit with v2.1.117 landing overnight — the seventeenth April release in twenty-two days and the first release that meaningfully widens the agent programming model rather than just polishing existing surfaces. The headline addition is forked subagents as an external-build opt-in (CLAUDE_CODE_FORK_SUBAGENT=1), moving the forked-subagent architecture from internal-only to anyone shipping a custom Claude Code binary. Agent frontmatter mcpServers is now loaded for main-thread agent sessions via --agent, closing a long-running gap where custom agents had reduced tool access compared to inline work. /resume will now proactively offer to summarize stale, large sessions — the natural follow-on to v2.1.116’s 40MB+ resume performance work — and MCP startup moves to concurrent connection handling.

Two sets of changes matter for enterprise posture. First, managed-settings enforcement for blockedMarketplaces and strictKnownMarketplaces — the plugin/marketplace-governance equivalent of the sandbox.network.deniedDomains posture that shipped in v2.1.113. Second, native builds on macOS and Linux now replace the Glob and Grep tools with embedded bfs and ugrep — the same performance/quality posture shift as the April-17 jq→native migration, and the first sign Anthropic is systematically walking through the bundled-JS-dependency tree rather than hotfixing individual tools. OpenTelemetry gets three new event attributes (command_name, command_source, effort) and a fix for Opus 4.7 context-window calculations (was reporting 200K, actually 1M). The Advisor Tool experimental gets reduced error states — a quiet signal that the advisor track is progressing toward more stable gating. What v2.1.117 still does not ship is a response to the OX Security MCP disclosure: no STDIO input sanitization change, no protocol-level hardening, no sandbox.mcp.* settings.

Beads

Latest: v1.0.2 (April 15, 2026)

No new release this week. v1.0.2 remains current — the now-fourth consecutive quiet week since the v1.0 announcement. The repository continues to accumulate issues without cutting a release; the post-1.0 stabilization posture holds unchanged into the EmTech/Cloud Next week. Steve Yegge’s April 4 “distributed graph issue tracker powered by Dolt” framing (x.com/Steve_Yegge/status/1977645937225822664) remains the public-positioning artifact the project is operating behind.

OpenSpec

Latest: v1.3.1 (April 21, 2026)

A new release: v1.3.1 landed yesterday with path and telemetry fixes — canonical artifact path resolution through realpath, glob artifact output corrections, cleaner --json output (preventing spinner progress from contaminating stderr when agents parse combined output), and telemetry reliability in firewalled networks. The release confirms the “monthly cadence” assumption observed last week is wrong in the strict sense — OpenSpec is running a point-release pattern where minor fixes land within two weeks of feature drops. v1.3.1 is the second release this month after v1.3.0’s April 11 feature drop (Junie/Lingma/ForgeCode/IBM Bob tool integrations).

---

🧵 From the Community (r/LocalLLaMA & r/MachineLearning)

“DeepSeek V4 Has Missed Three Windows — The Community Is Now Watching the Pre-Training Noise”

An r/LocalLLaMA thread tracking the DeepSeek V4 release window has consolidated what is now three missed “next few weeks” forecasts (April 3 Reuters, April 10 BigGo, April 14 DeepSeek V4 blog) into what the subreddit is reframing as a feature of the release rather than a bug. The working read: DeepSeek’s V4-Lite has already been live-tested on API nodes, pre-training is confirmed done, and the CUDA-free Huawei Ascend 950PR production path is the single technical risk that still remains unresolved. The thread’s modal position is that the delay is a Huawei-silicon production-yield story, not a model-readiness story — and the late-April window is now understood as “before the end of April, or after Google Cloud Next if Google lands anything that reshuffles open-vs-closed positioning.” Paired with the Tencent Hunyuan 3.0 April-launch reporting (led by former OpenAI researcher Shunyu Yao, ~30B parameters, in-context-learning and agent-usability focus), the community’s read is that the next two weeks could see two Chinese frontier-class open models ship in succession, a cadence that would retire last year’s “Chinese labs are behind” framing decisively.

”Forked Subagents Just Went Public — The MCP-Safe Story Got Complicated”

An r/MachineLearning Monday thread is actively dissecting the CLAUDE_CODE_FORK_SUBAGENT=1 flag shipping in tonight’s v2.1.117, and the conversation has pivoted fast from “great, we can build our own agent architecture” to “wait, this is exactly the integration surface the MCP-Safe proposal was trying to harden.” The thread’s concern: forked subagents inherit the main-agent’s MCP tool graph, which means any STDIO-sanitization flaw in the main-thread server configuration is now replicated across every forked subagent in a session. The companion weekend proposal — an audited-server registry that displays sanitization posture at install time — is being re-evaluated in light of forked subagents as more urgent, not less, because the surface area has just multiplied. The modal comment: “v2.1.117 is the feature ship, but the MCP-Safe repo is the compensating control."

"MIT Technology Review’s ‘10 Things That Matter in AI’ Is Its Most Consequential Editorial Move Since ‘Breakthrough Technologies’”

An r/MachineLearning megathread on the unveiled 2026 list is dissecting the editorial frame MIT Technology Review announced yesterday at EmTech. The list — AI companions, mechanistic interpretability, generative coding, hyperscale data centers, humanoid robot training, large language models (still), AI for scammers/offensive cybersecurity, world models, military AI, AI agents in teams, Chinese open-frontier labs, and AI co-scientists — is being read as the first attempt by a major technology publication to treat “AI trends” as a genre distinct from the “10 Breakthrough Technologies” franchise. The thread’s consensus: the inclusion of “AI scammers / offensive cyber” alongside mechanistic interpretability is the signal that the editorial team has accepted the Mythos-era framing where cyber capability is now a first-order AI trend, not a subcategory of “AI safety.” The second most-discussed entry is Chinese open-frontier labs “earning global credibility with developers” — an explicit editorial endorsement of the framing the Stanford 2026 AI Index and the DeepSeek V4 reporting have both been converging on.

”Amazon–Anthropic 5 GW Is Bigger Than the Headline Number — Here’s the Chart”

A Monday-night r/LocalLLaMA thread made the rounds with a reconstruction of the full Amazon–Anthropic compute commitment: $5B immediate, up to $25B total, ~5 GW of combined Trainium2+Trainium3 capacity by end of 2026, and a $100B-over-ten-years AWS spend commitment on Anthropic’s side. The thread’s point is that $100B over ten years is roughly the run-rate equivalent of Anthropic’s 2026 compute spend indexed forward at current growth — i.e., this is not a premium-priced long-term commitment, it’s Amazon formalizing what Anthropic would have spent on AWS anyway at something close to preferred-customer pricing. The comparative framing is the ~3.5 GW Google/Broadcom TPU deal from April 9: Anthropic is now the only frontier lab with both hyperscale compute locked across two hyperscalers, and the Nvidia-independence story that DeepSeek V4 will narrate on the China side has now been mirrored on the US side through AWS Trainium + Google TPU.

---

📰 Technical News & Releases

Google Cloud Next 2026 Opens Today in Las Vegas — “The Agentic Cloud” Keynote at 9 AM PT

Source: Google Cloud Next 2026 event page | BizTech Magazine preview: Agentic AI as a major theme | Anthropic at Google Cloud Next 2026

Google Cloud Next 2026 opens today at the Mandalay Bay Convention Center in Las Vegas, running April 22–24, with Google Cloud CEO Thomas Kurian’s opening keynote titled “The Agentic Cloud” scheduled for Wednesday, April 22, 9:00–10:30 AM PT. The expected focus across the three-day agenda: scaling AI agents across enterprise workloads, new Vertex AI tooling for multi-agent orchestration, Gemini API enhancements, Google Kubernetes Engine for AI, and industry verticalizations (retail, finance, healthcare, government). The Thursday developer keynote — “Get real: Agents in the autonomous era” — reinforces the editorial frame that 2026 is the year Google is positioning agentic AI as its core enterprise-cloud story, not a side product.

The significance for the next forty-eight hours is that Cloud Next lands into a news cycle already saturated with enterprise-agent narrative. EmTech AI opened yesterday with the “Agents at Work” session (9 AM ET today) and MIT Technology Review’s “10 Things That Matter” list headlined by AI agents in teams; Anthropic shipped Managed Agents to GA ten days ago and forked subagents to external builds overnight; Amazon just committed up to $25B more to Anthropic in part to lock enterprise-agent compute capacity. The competitive question Kurian’s keynote has to answer is whether Google’s agent-cloud story is differentiated from Anthropic-on-AWS — both are now selling enterprise agents on hyperscaler infrastructure, both have ~5 GW of dedicated compute capacity, and both are explicitly targeting the Fortune 500 AI-budget committees making Q2/Q3 procurement decisions. Anthropic has a scheduled partner session at Cloud Next — a reminder that the Google–Anthropic compute relationship (the ~3.5 GW Broadcom/TPU deal) sits alongside the Amazon deal, not in opposition to it.

Amazon Invests Additional $5B in Anthropic, With Up to $25B Total and a $100B 10-Year AWS Spend Commitment

Source: Bloomberg | TechCrunch | CNBC | Anthropic: Anthropic and Amazon expand collaboration for up to 5 gigawatts of new compute

Announced Monday and hardening into the week, Amazon is investing an additional $5 billion in Anthropic immediately with up to $20 billion more tied to commercial milestones — bringing Amazon’s total Anthropic investment to ~$33 billion on top of the $8 billion already in. The counter-commitment from Anthropic: $100+ billion over the next ten years on AWS technologies, including Trainium2 and Trainium3 hardware, plus Graviton. The deal secures up to 5 gigawatts of combined AWS Trainium2 and Trainium3 capacity for training and deploying Claude, with nearly 1 GW total of Trainium2+Trainium3 coming online by end of 2026. The valuation: $350 billion pre-money on the new funding, consistent with the $380B IPO-window target reported earlier in April. Starting this week, AWS customers can access the full Anthropic-native Claude console from within AWS using their existing AWS contract — no additional credentials, contracts, or billing relationships.

The structural read is that Anthropic has now locked two hyperscaler compute commitments of roughly matched magnitude — the April 9 ~3.5 GW Google/Broadcom TPU deal plus this ~5 GW AWS Trainium commitment — and the combined posture decouples Anthropic from single-vendor Nvidia risk in a way that mirrors what DeepSeek is attempting on the Huawei Ascend side. The commercial implications: Claude will be a first-class console inside AWS starting immediately (matching the Google Cloud Vertex AI / Microsoft Foundry posture); Anthropic’s run-rate revenue just crossed $30B annualized, up from ~$9B at end-2025; and the IPO window — which The Information and Axios both described earlier in April as late-2026 at a $380–500B valuation — now sits on a much stronger compute-commitment foundation than OpenAI’s, whose $20B+ Cerebras deal is a fraction of the scale Anthropic has now secured across AWS and Google combined.

Claude Code v2.1.117 Ships Forked Subagents, Main-Thread Agent MCP Servers, and Native bfs/ugrep

Source: Claude Code GitHub releases

Landing overnight (00:04 UTC April 22) and covered in more depth in the Project Releases section above, v2.1.117 is the release that closes a meaningful gap in the Claude Code agent model. Forked subagents are now enabled on external builds via CLAUDE_CODE_FORK_SUBAGENT=1, which lets anyone shipping a custom Claude Code binary opt into the fork-based subagent architecture Anthropic has been running internally. The agent-frontmatter mcpServers field is now loaded for main-thread agent sessions when invoked via --agent, fixing the long-running gap where custom agents had reduced tool access compared to inline work. On the quality-of-life side: /resume now proactively offers to summarize stale, large sessions, /model selection persists across restarts, MCP startup uses concurrent connection handling, and plugin dependency management is improved.

Two under-discussed pieces are the most consequential long-term. First, native builds on macOS/Linux replace Claude Code’s built-in Glob and Grep tools with embedded bfs and ugrep — the same “walk the dependency tree one tool at a time” posture that shipped for jq on April 17, and the signal that Anthropic is systematically replacing bundled-JS tools with native binaries (performance, sandbox, and supply-chain-posture all improving together). Second, managed-settings enforcement for blockedMarketplaces and strictKnownMarketplaces — the plugin-governance equivalent of v2.1.113’s sandbox.network.deniedDomains. Both changes reflect Anthropic rationalizing the tool-and-ecosystem surface that any enterprise deployment can lock down. What v2.1.117 does not ship, despite four days of MCP-security attention: no STDIO sanitization change, no protocol-level MCP hardening, no sandbox.mcp.* settings. The community-led MCP-Safe adapter track is now into its second week as the de-facto hardening path for the MCP supply-chain class the OX Security disclosure put on the board ten days ago.

OpenAI Ships ChatGPT Images 2.0 — Charts, Diagrams, Multi-Language Text Rendering

Source: Bloomberg: OpenAI Unveils Image Model That’s Better at Charts and Diagrams | 9to5Mac preview coverage

OpenAI rolled out ChatGPT Images 2.0 on Tuesday, shipping through both ChatGPT and the Codex AI coding assistant. The headline capability is accurate complex charts and scientific diagrams — the specific quality gap that has held OpenAI’s image models back for professional use — along with better instruction-following, more faithful style rendering, and multi-language text rendering in generated images. The positioning read is that this is OpenAI’s answer to the Claude Design / Canva-handoff story Anthropic opened April 17: Anthropic is selling natural-language design generation with a collaborative-surface handoff to Canva; OpenAI is selling natural-language visual generation embedded directly inside its own products.

The competitive frame is that ChatGPT Images 2.0 ships alongside Codex’s expansion into computer use, web workflows, image generation, memory, and deeper developer tools (announced earlier in April) — OpenAI is rationalizing its product surface so that a single ChatGPT Plus/Pro subscription plus Codex covers the full “generate any output” workflow, compared to Anthropic’s partner-first architecture (Claude Design → Canva, Claude Code → VS Code/Cursor, Managed Agents → enterprise-managed infrastructure). The open question through the rest of Q2 is whether the OpenAI single-product thesis or the Anthropic partner thesis earns better enterprise pricing once the Fortune 500 budget committees settle their 2026-H2 procurement. Cloud Next’s “Agentic Cloud” agenda is the first test.

Trump Signals DoD–Anthropic Deal Is “Possible” After White House Meeting

Source: CNBC

In a significant softening of the administration’s posture toward Anthropic, President Trump told CNBC on Tuesday that a Department of Defense deal with Anthropic is “possible”, citing “some very good talks” with the company during a White House meeting last week. The framing — that Anthropic is “shaping up” — is a material reversal from the March 29 “phased out for refusing domestic surveillance and autonomous weapons deployment” posture that triggered the still-pending DOJ appeal of Judge Rita Lin’s April 7 ruling blocking the ban (2026-04-07-AI-Digest). The April 20 OMB memo wiring federal agencies for Mythos around the Pentagon blacklist now reads, in hindsight, as the pre-positioning for exactly this reversal — with the UK AISI evaluation of Claude Mythos Preview landing the same weekend as the technical foundation that made the reversal politically defensible.

The broader signal is that the White House has now publicly re-entered negotiation with Anthropic at the DoD level inside the same week that Amazon committed up to $25B more (partly underwriting Anthropic’s federal-capacity trajectory) and the UK AISI’s Mythos evaluation supplied the empirical asymmetry framing. The open question for the rest of the week is whether the DOJ appeal is withdrawn — which would be the strongest signal that the blacklist is collapsing entirely — or whether Trump’s “possible” stops at a scoped DoD contract without reversing the “supply-chain risk” designation in full.

MIT Technology Review Unveils “10 Things That Matter in AI Right Now” at EmTech — New Annual List Format Debuts

Source: MIT Technology Review | Roundtables: Unveiling the 10 Things That Matter in AI Right Now | The Download coverage

MIT Technology Review unveiled its first-ever annual “10 Things That Matter in AI Right Now” list at EmTech AI on Tuesday afternoon — a format split from the magazine’s long-running “10 Breakthrough Technologies” franchise because the AI candidate set was too dense to fit inside a general-technology frame. The ten entries: AI companions, mechanistic interpretability, generative coding, hyperscale data centers, humanoid robot training, large language models (still), AI for scammers and offensive cybersecurity, world models, AI’s military applications, AI agents cooperating in teams, Chinese AI labs giving away frontier models, and AI co-scientists. (The published list has twelve items rather than ten — a distinction the Monday roundtable explicitly flagged as “so many worthy candidates we couldn’t fit them all.”)

The editorial significance is that MIT Technology Review has explicitly promoted AI for offensive cybersecurity and Chinese open-frontier labs earning global developer credibility into its annual “things that matter” canon — both have been implicit in the Mythos-era and Stanford-AI-Index coverage of the last two weeks but have not yet appeared in a single-page editorial endorsement. The inclusion of AI agents in teams and AI co-scientists on the same list as LLMs (still) is the clearest public signal to date that MIT Technology Review is treating 2026 as the year where the model-capability story and the agent-deployment story become the same story. The list is now the reference artifact that the Wednesday enterprise-agent panel at EmTech and the Thursday closing public-perception session will be read against.

Vercel × Context AI Breach Enters Phase Two — $2M Sale on BreachForums, February Infection Date Revealed

Source: The Register | Security Boulevard: $2M data heist | Dark Reading | OX Security analysis

The Vercel × Context AI breach that broke Monday has now hardened with two new details that shift the severity assessment. First, the attacker is selling the stolen data for $2M on BreachForums — Vercel has declined to confirm dollar amounts but has not disputed the figure. Second, the Lumma Stealer infection on the Context AI employee’s laptop occurred in February 2026, meaning the attacker had more than two months of persistent OAuth access before the pivot into Vercel infrastructure was detected. Context AI’s Monday security advisory also confirmed that the attacker “likely compromised OAuth tokens for some of our consumer users” — which moves the blast radius from Vercel-only to the entire Context AI consumer OAuth-token set.

The strategic read aligning with Trend Micro’s Monday framing is that this is now unambiguously the template attack for the AI-productivity-tool supply-chain class. A single Lumma Stealer infection in February; two months of persistent OAuth token harvesting; a pivot from a third-party AI tool’s Google Workspace into Vercel’s internal systems through an OAuth scope with read access to platform environment variables; customer API keys, source code, and database data exfiltrated; stolen data now on BreachForums at $2M. The Dark Reading coverage frames this explicitly as “AI tools being onboarded at machine speed while access governance frameworks run at human speed” — a sentence that will show up in Q2 procurement decks the way “MCP supply chain” did in March–April. The practical consequence for the next quarter is that every developer-installed AI tool is now in scope for the same OAuth-scope audit, session-lifecycle review, and sensitive-variable encryption posture that enterprises have been applying to traditional SaaS for the last decade — with the wrinkle that AI tools proliferate faster than IT can onboard them.

EmTech AI 2026 Day 2 — “Agents at Work,” “Talent, Team, Transformation,” and the 10-Things List in Circulation

Source: Detailed agenda | CSAIL Alliances event page

Day 2 of EmTech AI opened at 9 AM ET with two parallel sessions that together define the conference’s editorial thesis: “Agents at Work” on deploying agentic systems at scale (“what worked, what didn’t, how value was measured, and the surprising lessons only experience reveals”) and “Talent, Team, Transformation” on reskilling teams and rethinking talent pipelines in a world where human and machine intelligence are “inextricably linked.” The session design pairs the technical-deployment case with the organizational-change case, explicitly aligning with the “Great Integration” framing announced at Monday’s opening keynote.

The session most watched by Fortune 500 budget committees is the Wednesday afternoon enterprise-agent panel, where EY’s 130,000-professional Claude rollout is expected to surface in public for the first time alongside Microsoft and JPMorgan Chase participation. The 10-Things List circulating among attendees is now the frame the panel will be read against — the inclusion of “AI agents cooperating in teams” on the list provides the editorial mandate for EY/Microsoft/JPMC to articulate exactly what “at scale” means in 2026 terms. Thursday’s closing session absorbing the Q1 tech-layoff tape, the Bloomberg backlash reporting, and the CNBC AI-demand skepticism pieces will, in combination with the Cloud Next keynote twelve hours earlier, set the Q2 enterprise-AI narrative for the remainder of the quarter.

---

🧭 Key Takeaways

• Google Cloud Next opens today with “The Agentic Cloud” as its defining frame — and its editorial distinctiveness depends entirely on what Kurian can say that Anthropic hasn’t already shipped. Managed Agents went GA ten days ago; forked subagents just landed in external Claude Code builds overnight; EmTech’s “Agents at Work” session is running the same morning; MIT Technology Review’s 10-Things list put AI agents in teams in its first-ever canon. The Cloud Next keynote is landing into a saturated enterprise-agent news cycle, and the differentiation question is sharp: Google is selling agents on Google infrastructure with Gemini, Anthropic is selling agents on AWS and Google infrastructure with Claude, and the Fortune 500 buyers making Q2 decisions now have concrete comparison points between the two across every cloud surface. What gets said between 9 AM and 10:30 AM PT today will anchor the enterprise-agent narrative through EmTech’s closing session Thursday.

• The Amazon–Anthropic $25B / 5 GW / $100B-over-10-years deal is the compute-commitment story that formalizes Anthropic’s dual-hyperscaler posture and closes the IPO-runway question. Anthropic now has ~5 GW of AWS Trainium2/Trainium3 capacity coming online by end-2026 plus ~3.5 GW of Google/Broadcom TPU capacity from 2027, Claude as a first-class console inside AWS starting this week, and a $350B-pre-money valuation on the new funding. The $100B 10-year AWS spend commitment is roughly the forward-indexed run-rate of Anthropic’s 2026 compute draw — structurally closer to preferred-customer pricing than to a premium. The OpenAI-Cerebras $20B three-year commitment that felt large last Friday now looks small next to two ~5 GW hyperscaler commitments.

• Claude Code v2.1.117 is the first April release to widen the agent model rather than polish existing surfaces — forked subagents, main-thread agent MCP servers, and native bfs/ugrep all matter. The CLAUDE_CODE_FORK_SUBAGENT=1 opt-in brings internal fork-based subagent architecture to custom external builds. Agent-frontmatter mcpServers now loading for --agent-invoked main-thread sessions closes the long-running gap between custom agents and inline work. Native bfs/ugrep replacing bundled Glob/Grep is the second “walk the dependency tree and replace JS with native” milestone after jq, setting a pattern for the rest of Q2. Managed-settings enforcement for blockedMarketplaces / strictKnownMarketplaces matches the v2.1.113 sandbox.network.deniedDomains enterprise-governance posture. What still hasn’t shipped: any response to the OX Security MCP disclosure — so the community-led MCP-Safe adapter track remains the default hardening path for Anthropic’s largest unresolved security-posture question.

• The White House’s DoD-Anthropic “possible” signal is the clearest public unwind of the March-29 blacklist to date, and the timing suggests coordination with the UK AISI evaluation and the Amazon commitment. Trump telling CNBC that “very good talks” happened at the White House last week, combined with the April 20 OMB memo wiring federal agencies for Mythos around the Pentagon blacklist, the UK AISI evaluation supplying the empirical-asymmetry foundation, and the Amazon $25B commitment underwriting federal compute capacity — all point to a coordinated reversal pathway. The open question is whether the DOJ appeal of Judge Lin’s ruling is withdrawn; if yes, the blacklist is effectively dead; if no, the DoD deal is a scoped carve-out that leaves the “supply-chain risk” designation technically in place. Either outcome materially changes Anthropic’s federal-revenue trajectory.

• MIT Technology Review’s “10 Things That Matter in AI Right Now” is the first major publication’s editorial canonization of the 2026-specific AI narrative — and its inclusions matter as much as its omissions. Offensive cybersecurity AI (implicit endorsement of the Mythos-class capability framing); Chinese open-frontier labs earning global credibility (explicit endorsement of the Stanford AI Index / DeepSeek trajectory); AI agents cooperating in teams and AI co-scientists (the “agents are the 2026 story” thesis); world models, humanoid robot training, and hyperscale data centers (the physical-and-infrastructural thesis); AI companions and mechanistic interpretability (the human-centered thesis). The list is now the reference artifact EmTech’s remaining sessions and the Cloud Next keynote will be read against — and its frame is unusually kind to the Anthropic-adjacent narrative (Mythos cyber capability, Claude Code generative coding, Managed Agents for agent teams) relative to OpenAI’s or Google’s positioning.

• The Vercel × Context AI breach has hardened into the template attack for the AI-productivity-tool supply-chain class, and the $2M BreachForums sale means the full exfiltrated-data class will now be broadly available. A February 2026 Lumma Stealer infection, two months of persistent OAuth access, a pivot into Vercel internal systems, customer API keys / source code / database data — and the resulting dataset now trading at a $2M price point. Context AI’s acknowledgment that consumer OAuth tokens were “likely compromised” extends the blast radius well beyond Vercel. The “AI tools onboarded at machine speed, access governance at human speed” framing is now in broad circulation, and will anchor the Q2 procurement conversation around every AI-productivity tool the same way MCP supply-chain did in March–April. Every AI tool installed on a developer’s laptop is now, by default, a supply-chain dependency of every production system that developer has access to.

---

Generated on April 22, 2026 by Claude