AI Digest — April 23, 2026

---

🔖 Project Releases

Claude Code

Latest: v2.1.118 (April 23, 2026 — 00:42 UTC)

The April release cadence holds — v2.1.118 landed roughly twenty-four hours after v2.1.117, making it the eighteenth April release in twenty-three days and the first release of the Cloud Next / EmTech week to address the TUI and editor-ergonomics surface rather than the agent architecture. The headline addition is vim visual modes: v (visual) and V (visual-line) now work inside the Claude Code prompt input with selection, operators, and visual feedback — closing a long-standing gap in the vim-mode editor surface that’s been building toward parity with external editors since the March /config → Editor-mode flag. Alongside visual modes, custom named themes now ship via /theme, including hand-edited JSON theme files under ~/.claude/themes/ — a feature that moves Claude Code’s TUI configurability from “pick from the bundled set” to “check a theme file into your team dotfiles.” /cost and /stats are consolidated into /usage (both older names remain as typing shortcuts), cleaning up a split-UI surface that has been confusing new users.

Two enterprise-governance changes meaningfully extend the posture Anthropic has been accreting across v2.1.113 → v2.1.117. First, DISABLE_UPDATES env var now blocks all update paths — stricter than the existing DISABLE_AUTOUPDATER which only disabled background autoupdates. For enterprises running pinned Claude Code in regulated environments, this is the variable that actually closes the update surface in one setting. Second, WSL on Windows can now inherit Windows-side managed settings via the new wslInheritsWindowsSettings policy — which closes a practical gap where Windows IT departments were managing two parallel policy trees for the same user. The most consequential developer-facing addition is MCP tool hooks: hooks can now invoke MCP tools directly via type: "mcp_tool", which lets hook authors chain MCP servers into the pre/post/PreCompact hook pipeline without building custom shell plumbing. Auto mode defaults gain "$defaults" composition (add custom rules alongside bundled ones rather than replace them). Plugin tagging adds claude plugin tag for creating release git tags with version validation — a small but telling sign that Anthropic is treating plugins as versioned release artifacts, not scripts. What v2.1.118 still does not ship: any STDIO sanitization change or sandbox.mcp.* setting in response to OX Security’s MCP disclosure. The MCP-Safe community track continues to be the de-facto hardening path into week three.

Beads

Latest: v1.0.2 (April 15, 2026)

No new release this week. v1.0.2 remains current — the fifth consecutive quiet week since the v1.0 announcement. The post-1.0 stabilization posture holds unchanged through Cloud Next / EmTech week. The repository continues to accumulate issues and commit activity without cutting a point release; observers have now moved from “next release imminent” to “Beads is operating on a batch-release cadence deferred until the next meaningful feature cluster lands.” Steve Yegge’s April 4 “distributed graph issue tracker powered by Dolt” framing (x.com/Steve_Yegge/status/1977645937225822664) remains the canonical public positioning.

OpenSpec

Latest: v1.3.1 (April 21, 2026)

No new release today. v1.3.1 — the April 21 path and telemetry fixes release — remains current, confirming the two-days-after-feature-drop hotfix pattern observed earlier this week. The next signal to watch is whether a v1.3.2 lands before the end of the week with OpenSpec-side integration response to the Gemini Enterprise Agent Platform announcement; v1.3.0 added tooling for four new AI coding assistants (Junie, Lingma, ForgeCode, IBM Bob), and Google’s “Agent Designer” surface at Cloud Next is exactly the class of integration target OpenSpec has been tracking.

---

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

“Gemini Enterprise Agent Platform Is Google Admitting Vertex Was the Wrong Brand”

An r/MachineLearning Wednesday evening megathread on the Gemini Enterprise Agent Platform rebrand is reading the Vertex AI → Gemini Enterprise Agent Platform rename as a tacit admission that the Vertex brand was never going to carry a $100B enterprise-agents narrative. The subreddit’s modal position: the platform was always the competitive asset against AWS Bedrock and Microsoft Foundry, but “Vertex AI” positioned it as a data-science ML-ops surface rather than an agent-deployment control plane. The Gemini Enterprise Agent Platform rename, with Agentspace absorbed and Agent Studio / Agent-to-Agent Orchestration / Agent Registry / Agent Identity / Agent Gateway / Agent Observability as first-class surfaces, is the explicit control-plane positioning Google needed if it wanted to credibly compete with Anthropic-on-AWS (Bedrock) and Anthropic-on-Azure (Foundry). The second-most-discussed observation: Claude is still listed as a first-class model on the platform, even though the rebrand is framed around Gemini 3.1 Pro, 3.1 Flash Image (Nano Banana 2), and Lyria 3. The community’s read: Google is keeping the Anthropic partnership on the platform not out of generosity but because enterprise buyers would not adopt a single-model agent platform in 2026, and the Gemini Enterprise Agent Platform has to win on the orchestration surface to compete.

”TPU 8t / 8i Is the Split Nvidia Didn’t Do — And Might Be the First Silicon to Price Below Hopper on Inference”

An r/LocalLLaMA thread on the TPU 8t / TPU 8i dual chip split argues the architectural choice — separate chips for training (8t) and inference (8i) — is the first hyperscaler silicon that explicitly optimizes around the 2026-specific inference-economics problem rather than training-FLOPs leadership. The thread cites Google’s claimed 3x training-performance uplift over the previous generation and the 80% better performance per dollar framing as the headline numbers, but the bigger argument is that the 8i’s 3x more on-chip SRAM and 1,152-TPU pod sizing tune directly for agent-serving workloads — “millions of agents concurrently” is the stated design goal. The comparative implication: Nvidia has resisted splitting Hopper/Blackwell into a dedicated inference SKU because the GB200 is still selling out, but if Gemini 3.1 Flash and Opus 4.7 inference on TPU 8i starts coming in below Hopper pricing, the economic pressure to split accelerates across the rest of 2026. The MoE-serving community is reading this as the silicon validation of the architectural pattern that has dominated open-frontier models (Qwen 3.5, DeepSeek V4, GLM-5.1).

”SpaceX Options Cursor for $60B — What Does xAI’s Grok Code Look Like Now?”

An r/MachineLearning thread on SpaceX’s $60B option to acquire Cursor is dissecting the competitive implications for the rest of the agentic-coding cohort. The thread’s read: the $10B “collaboration fee” paid immediately to interrupt Cursor’s pending $2B / $50B round is the single largest front-running payment in AI-tooling history, and the structure (SpaceX holds the $60B option against Cursor, exercisable after SpaceX’s summer IPO) suggests SpaceX is treating Cursor as strategically essential to xAI’s developer-tools roadmap, not as a financial investment. The comparative analysis framing: xAI now has the option on the #1 IDE-native agentic coding tool the same quarter Anthropic compounds on Claude Code at $2.5B+ ARR and OpenAI reorganizes Codex under a gated domain-specialized posture. The thread’s consensus: if the SpaceX acquisition closes after SpaceX’s IPO, Grok Code becomes a first-class IDE-embedded product overnight; if Cursor chooses the $10B collaboration path instead, the deal still gives xAI the deepest partnership-as-acquisition ramp in the industry. The single most-linked comment: “the $10B collaboration fee just set the floor price for every other acqui-hire in the coding-agent space."

"OpenAI’s DeployCo Is the Structure That Would Not Have Happened if GPT-6 Shipped on Time”

An r/MachineLearning Wednesday thread on OpenAI’s $1.5B DeployCo commitment is reading the private-equity-backed enterprise-AI vehicle as the direct consequence of GPT-6’s missed window. The structure — OpenAI contributes $500M equity with an option to add $1B, private-equity partners (TPG, Bain Capital, Advent International, Brookfield, Goanna Capital) add ~$4B over five years at a guaranteed 17.5% annual return, and OpenAI retains super-voting shares — is being read as OpenAI buying enterprise-deployment surface area with someone else’s balance sheet because the GPT-6 capability uplift that was supposed to close the enterprise gap isn’t here yet. The comparative frame: Anthropic’s dual-hyperscaler posture (AWS 5 GW + Google 3.5 GW) and $350B valuation are funded by operating revenue at a $30B run rate; OpenAI’s $1.5B enterprise vehicle is funded by structured PE with a 17.5% guarantee, which is the tell that OpenAI’s financing cost-of-enterprise-growth is now structurally above Anthropic’s. The thread’s consensus: “if GPT-6 had shipped in March, DeployCo wouldn’t exist.”

---

📰 Technical News & Releases

Google Cloud Next 2026 Day 2 — Gemini Enterprise Agent Platform, 8th-Generation TPU 8t / 8i, Agentic Data Cloud

Source: Google Cloud: Introducing Gemini Enterprise Agent Platform | Google Cloud: Our eighth generation TPUs | Axios: Google unifies Gemini Enterprise, debuts new chips | TechCrunch: Google Cloud launches two new AI chips | SiliconANGLE: The agent control plane hits overdrive at Next 2026

Thomas Kurian’s “The Agentic Cloud” keynote resolved into three substantive announcements that together define Google’s 2026 enterprise posture. First, Vertex AI is rebranded and consolidated as the Gemini Enterprise Agent Platform, absorbing Agentspace and surfacing Agent Studio, Agent-to-Agent Orchestration, Agent Registry, Agent Identity, Agent Gateway, and Agent Observability as first-class primitives. The platform ships with Gemini 3.1 Pro positioned as “the most advanced model optimized for complex workflow orchestration,” Gemini 3.1 Flash Image (Nano Banana 2) for high-fidelity UI and visual assets, Lyria 3 Pro for audio and music, Veo 3.1 Lite for cost-optimized video, and — notably — Anthropic’s Claude as a first-class foundation-model option on the platform alongside Gemini. Second, the Agentic Data Cloud — a cross-cloud Lakehouse and Knowledge Catalog designed to let organizations put agentic AI on their existing data without re-platforming — lands as Google’s answer to the Fortune 500 budget question about what data-readiness for agents actually requires.

Third and most consequential long-term: Google’s 8th-generation TPU is split into two purpose-built chips. TPU 8t (training) networks up to 9,600 TPUs with 2 PB of shared high-bandwidth memory via a new inter-chip interconnect (ICI), delivering a claimed 3x compute uplift and 80% better performance-per-dollar over the previous generation. TPU 8i (inference) connects 1,152 TPUs in a single pod with 3x more on-chip SRAM, explicitly tuned for serving “millions of agents concurrently” with ultra-low latency for MoE workloads. Pichai’s framing — “our commitment to differentiated silicon” — is the clearest public signal yet that Google intends to compete on inference economics against Nvidia’s GB200 / Rubin trajectory. The read for Anthropic is specific: the ~3.5 GW of Google TPU capacity committed through the April 9 Broadcom / Google deal (starting 2027) is now concrete enough that Anthropic’s TPU spend is a named line item in the Gemini Enterprise Agent Platform’s marketing material — The Motley Fool’s Wednesday coverage frames Anthropic’s commitment to next-generation TPUs as “huge news for Alphabet and Broadcom.” Cloud Next Day 2 also unveiled an Agentic Defense posture combining Google Threat Intelligence, Security Operations, and Wiz’s Cloud and AI Security Platform — the first visible productization of the Wiz acquisition in the agent-security vertical. The Kurian framing that will be quoted through the rest of the week: other vendors are “handing you the pieces, not the platform, leaving teams to integrate components themselves.”

SpaceX Secures Option to Acquire Cursor for $60B — Pays $10B “Collaboration Fee” to Halt $2B Round

Source: Bloomberg: SpaceX Has Deal for Right to Acquire Cursor for $60 Billion | TechCrunch: SpaceX is working with Cursor and has an option to buy the startup for $60 billion | TechCrunch: How SpaceX preempted a $2B fundraise with a $60B buyout offer | CNBC: SpaceX can buy Cursor later this year for $60 billion | Fortune: SpaceX strikes a $60 billion deal for Cursor

SpaceX — which owns Elon Musk’s AI lab xAI — disclosed Tuesday and hardened into Wednesday a deal structure that halts Cursor’s pending $2B Series funding round at $50B valuation and puts a $60B acquisition option on the table, exercisable after SpaceX’s expected summer IPO. The terms: SpaceX pays $10B immediately as a “collaboration fee” for existing partnership work with Cursor, and takes the option to acquire Cursor for $60B later in 2026 — likely financed by post-IPO SpaceX stock to avoid the need to update SpaceX’s confidential pre-IPO financial filings. The practical consequence is that Cursor’s $2B round — which would have closed this week — is paused indefinitely, and the company has chosen the acquisition-path posture over independent fundraising.

The strategic read is that xAI’s Grok Code agentic-coding surface has been materially behind Claude Code, Codex, and Cursor Composer 2 through all of Q1, and SpaceX has concluded that organic catch-up is slower and more expensive than preemptive acquisition. The $10B collaboration fee alone is larger than Cursor’s entire pre-deal valuation reset a year ago — which makes the $60B acquisition-window option look inexpensive relative to the strategic value of owning the #1 IDE-native agentic coding surface heading into Q3/Q4 enterprise-agent procurement. The comparative framing: Anthropic has built Claude Code organically to $2.5B+ ARR over twelve months; OpenAI has reorganized Codex under a gated domain-specialization posture; SpaceX just bought the option on Cursor for the equivalent of a year-and-a-half of Claude Code’s annualized revenue. Cursor CEO Michael Truell’s positioning — that SpaceX’s partnership work “is too important to defer while we close a fundraise” — is the public framing that the acquisition-path is a mutually chosen posture, not a hostile lock-in.

OpenAI Commits Up to $1.5B to “DeployCo” — Private-Equity-Backed Enterprise AI JV with 17.5% Guaranteed Return

Source: PYMNTS: OpenAI Pledges $1.5 Billion to PE Enterprise AI Project | Investing.com: OpenAI in talks to commit up to $1.5 billion to private equity JV, FT reports | GuruFocus: OpenAI Plans $1.5 Billion Investment in New Joint Venture

OpenAI is preparing to commit up to $1.5 billion to a new joint venture called DeployCo — a Delaware-listed LLC valued at $10 billion in a funding round expected to close early next month. The structure: OpenAI contributes $500M in equity initially with an option to add $1B later; private-equity partners TPG, Bain Capital, Advent International, Brookfield, and Goanna Capital commit a combined ~$4B over five years at a reported 17.5% guaranteed annual return. OpenAI retains super-voting shares to preserve strategic control. DeployCo is aimed explicitly at accelerating adoption of OpenAI’s enterprise workplace tools — the segment where Anthropic’s $30B+ run rate and Fortune 500 account penetration have opened a visible gap over the last two quarters.

The structural read is that DeployCo is the first publicly disclosed instance of a frontier-lab financing enterprise-deployment growth through external private equity with guaranteed returns — a structure more common to real-estate and infrastructure funds than to AI-company growth capital. The 17.5% guaranteed annual return is the specific detail that differentiates this from ordinary equity investment: OpenAI is effectively paying a premium cost of capital to lock in PE distribution and deployment support, rather than extending operating revenue or equity to do the same work. The comparative frame sharpens against Anthropic’s dual-hyperscaler posture from Tuesday: Anthropic’s ~5 GW AWS + 3.5 GW Google compute and $100B / 10-year AWS counter-commitment are financed at approximately the forward-indexed run-rate of 2026 compute draw (preferred-customer pricing), while OpenAI’s enterprise-growth vehicle is financed at 17.5% guaranteed. The cost-of-capital gap between the two labs has now quantifiably widened — and it did so in the same week Anthropic outspent OpenAI on lobbying for the first time.

Claude Code v2.1.118 Ships Vim Visual Modes, Custom Themes, MCP Tool Hooks, DISABLE_UPDATES

Source: Claude Code GitHub releases

v2.1.118 landed at 00:42 UTC April 23 — roughly twenty-four hours after v2.1.117, continuing the pattern of daily releases through Cloud Next / EmTech week. The release consolidates three threads that have been building across the April cadence. Vim mode gains visual (v) and visual-line (V) modes with operators, selection, and visual feedback — closing the largest remaining gap in the Claude Code vim-mode surface and bringing the TUI editor within parity of external editors like Neovim for most prompt-editing workflows. Custom named themes via /theme, plus hand-edited JSON files in ~/.claude/themes/, move theme configurability from bundled to project-checked-in. /cost and /stats consolidate into /usage (old names remain as aliases) — cleaning up a UI split that has been a recurring new-user friction point. MCP tool hooks via type: "mcp_tool" let hook authors invoke MCP tools directly from the pre/post/PreCompact pipeline, which unlocks a meaningful class of agentic workflows that previously required custom shell plumbing.

On the enterprise-governance side, DISABLE_UPDATES is now a stricter env var than DISABLE_AUTOUPDATER and blocks all update paths — the variable regulated-environment deployments have been asking for. WSL on Windows can inherit Windows-side managed settings via the new wslInheritsWindowsSettings policy, closing a long-running dual-policy-tree problem for Windows IT. Auto mode defaults gain "$defaults" composition (add custom rules alongside built-ins rather than replace them). claude plugin tag creates release git tags with version validation — a small but telling signal that Anthropic is treating plugins as versioned release artifacts with commercial-software release semantics. The long list of bug fixes addresses MCP OAuth, credential corruption, keyboard input freezing, and session management. What v2.1.118 still does not ship: any STDIO sanitization change, sandbox.mcp.* settings, or protocol-level MCP hardening — the OX Security disclosure is now into its second week without a formal Anthropic response, and the community-led MCP-Safe hardening track remains the default posture for enterprise deployments.

Anthropic Outspends OpenAI on Q1 Lobbying at $1.6M — 4x Year-Over-Year

Source: Axios

Anthropic posted its biggest-ever lobbying quarter in Q1 2026 at $1.6M, up 4x year-over-year from $360K in Q1 2025 — and for the first time, outspent OpenAI (which spent $1M). The topics Anthropic’s lobbyists engaged on include AI procurement, Department of Defense procurement, supply-chain risk, acceptable-use policy, AI and national security, export controls, AI legislation, energy infrastructure, and permitting — a topic mix that reads as the exact list of policy levers that converged into the Trump “DoD possible” signal Tuesday and the April 20 OMB memo wiring federal agencies for Mythos around the Pentagon blacklist.

The broader Big-Tech context: Meta topped Q1 2026 Big Tech lobbying at $7.1M, with Amazon at $4.4M and Google at $2.9M — so Anthropic’s $1.6M is still well below the scaled incumbents, but the first-time outspend vs. OpenAI is the directionally important signal. Combined with AnthroPAC’s April 6 formation and the well-documented Amodei White House meeting sequence, Anthropic has now publicly committed to the lobbying-intensive track that OpenAI’s playbook has dominated since the Pentagon-deal period. The strategic consequence is sharp: Anthropic is financing enterprise-deployment momentum through operating revenue (not external PE like DeployCo) and financing federal-policy access through the highest lobbying spend in its history — a combination that looks structurally more sustainable than OpenAI’s financed-growth + decelerating lobbying profile going into Q2.

EmTech AI 2026 Day 3 Closes — “Great Integration” Thesis Becomes Running Editorial Frame

Source: Detailed agenda | EmTech AI 2026 event page

EmTech AI 2026 closes today at MIT with the Thursday sessions absorbing the Wednesday enterprise-agent panel (EY’s 130,000-professional Claude rollout, Microsoft, JPMorgan Chase) and the “10 Things That Matter in AI” list Tuesday’s keynote unveiled. The running editorial frame — the “Great Integration” — treats 2026 as the year where model capability, agent deployment, and organizational change become one procurement conversation rather than three distinct ones. The day-3 sessions on reskilling and pipeline redesign pair with the Q1 tech-layoff tape (78,557 workers, ~47.9% AI-attributed) as the explicit labor-market counterpart.

The specific signal from the conference floor — covered in invited-attendee summaries circulating through Wednesday evening — is that the AI agents in teams entry on the 10 Things list is now the Fortune 500 budget-committee reference artifact for Q2 procurement, and the EY + Microsoft + JPMC panel provided the concrete precedent that panel-deployment stories are now possible to underwrite at 130K-professional scale. Combined with Cloud Next’s Gemini Enterprise Agent Platform unveiling and Anthropic’s Managed Agents GA, the three surfaces in the market (Google, Anthropic, Microsoft × OpenAI) now map cleanly to the three dominant buyer postures. The closing session folding into the Q1 tech-layoff tape and the Bloomberg backlash reporting will set the Q2 enterprise-AI narrative going into May.

Vercel × Context AI Breach Enters Day 4 — OAuth Scope Rotation Becomes Q2 Audit Template

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

The Vercel × Context AI breach moved into Day 4 of public analysis with the OAuth-scope rotation and session-lifecycle posture now the concrete Q2 audit template being circulated inside Fortune 500 security organizations. The attack sequence — February 2026 Lumma Stealer infection on a Context AI employee laptop, two months of persistent OAuth token harvesting, pivot from Context AI’s Google Workspace into Vercel internal systems through an OAuth scope with read access to platform environment variables, exfiltration of customer API keys, source code, and database data, $2M BreachForums listing — is now being explicitly formalized by Security Boulevard and Dark Reading as the template attack for AI-productivity-tool supply chain. Context AI’s acknowledgment that consumer OAuth tokens were “likely compromised” extends the blast radius beyond Vercel into the entire Context AI consumer OAuth-token set.

The Wednesday development is that Google’s Agentic Defense announcement at Cloud Next explicitly foregrounds AI-tool OAuth scope governance as a first-class product capability — the first concrete hyperscaler productization of the class of problem the Vercel × Context AI incident demonstrated. The framing carrying forward: every AI-productivity tool with Google Workspace / Microsoft Graph / GitHub App permissions is a candidate for the same breach template until OAuth scopes are rotated, sessions lifecycle-governed, and environment variables encrypted. The practical consequence is that Q2 AI-tool procurement will include OAuth-scope audits as a default line item — and the Cloud Next unveiling of Agentic Defense with Wiz integration is Google’s bet that the hyperscaler-provided version of that audit wins against the vendor-provided version.

---

🧭 Key Takeaways

• The Gemini Enterprise Agent Platform rebrand and TPU 8t / 8i silicon split are Google’s most substantive enterprise-AI positioning since Vertex AI launched in 2021 — and the read is that Google now considers the Vertex brand too narrow to carry the 2026 enterprise-agents narrative. Consolidating Vertex + Agentspace into the Gemini Enterprise Agent Platform with Agent Studio / A2A Orchestration / Agent Registry / Agent Identity / Agent Gateway / Agent Observability as first-class primitives, plus Gemini 3.1 Pro / 3.1 Flash Image (Nano Banana 2) / Lyria 3 Pro and Claude as first-class model options, positions Google as the control-plane vendor against Anthropic-on-AWS (Bedrock) and Anthropic-on-Azure (Foundry). Splitting the 8th-gen TPU into 8t (training: 9,600-TPU superpods, 2 PB HBM, ICI) and 8i (inference: 1,152-TPU pods, 3x SRAM, MoE-optimized) is the clearest public signal yet that Google intends to compete on inference economics — which is the battleground Anthropic’s per-token pricing structure has already been winning on with Claude.

• SpaceX’s $60B option on Cursor plus the $10B collaboration fee is the single largest front-running payment in AI-tooling M&A — and it resets the floor price for every coding-agent acqui-hire. Halting Cursor’s pending $2B / $50B round immediately, paying $10B for existing partnership work, and taking a $60B acquisition option exercisable after SpaceX’s summer IPO together give xAI the deepest partnership-to-acquisition ramp in the industry. The strategic implication: Grok Code either becomes a first-class IDE-embedded product after the option exercises, or xAI locks in the deepest Cursor collaboration any vendor has. The comparative framing is sharp: Anthropic has organically compounded Claude Code to $2.5B+ ARR; OpenAI has reorganized Codex under a gated posture; SpaceX has bought the option on the category leader. The cost of a competitive coding-agent surface in 2026 is now publicly priced at $60B.

• OpenAI’s $1.5B DeployCo commitment — with a 17.5% guaranteed PE return — is the first publicly disclosed frontier-lab financing structure for enterprise deployment with a quantifiable premium cost of capital over operating-revenue financing. $500M equity plus an option on $1B, ~$4B from TPG / Bain / Advent / Brookfield / Goanna over five years at 17.5% annual guaranteed return, OpenAI retains super-voting shares. Compared against Anthropic’s dual-hyperscaler posture (5 GW AWS + 3.5 GW Google, $100B / 10-year AWS spend, preferred-customer pricing) financed at approximately forward-indexed run-rate, OpenAI is now visibly paying a higher cost of capital for enterprise growth. The r/MachineLearning reading — “if GPT-6 had shipped in March, DeployCo wouldn’t exist” — is the honest framing: DeployCo substitutes financial engineering for a product capability that hasn’t arrived.

• Claude Code v2.1.118 is the TUI-ergonomics companion to v2.1.117’s agent-architecture widening — vim visual modes, custom themes, MCP tool hooks, and DISABLE_UPDATES together close long-standing editor and governance gaps in a single release. Vim v / V modes plus operators brings the prompt editor within parity of external editors; custom named themes via ~/.claude/themes/ make TUI configuration checkable into dotfiles; /usage consolidates /cost and /stats; MCP tool hooks via type: "mcp_tool" unlock agentic pre/post/PreCompact workflows that previously required custom shell plumbing; DISABLE_UPDATES is stricter than DISABLE_AUTOUPDATER and closes the update surface for regulated deployments; wslInheritsWindowsSettings unifies Windows-side policy trees. What’s still missing eighteen April releases in: any response to the OX Security MCP disclosure. The community-led MCP-Safe track holds into week three.

• Anthropic outspending OpenAI on Q1 lobbying at $1.6M (4x YoY, first-time outspend) is the policy-channel counterpart to the dual-hyperscaler compute story and the federal-deployment reversal. The Q1 topic mix — DoD procurement, supply-chain risk, acceptable-use policy, AI legislation, energy, permitting — tracks directly to the April 20 OMB memo, the Trump “DoD possible” signal Tuesday, and the UK AISI Mythos evaluation. Anthropic is now financing enterprise-deployment momentum through operating revenue and federal-policy access through its highest lobbying spend ever, a combination that looks structurally more sustainable than OpenAI’s financed-growth + decelerating lobbying profile. Relative to the Meta / Amazon / Google / Microsoft cohort spending $2.9M–$7.1M, Anthropic still has visible room to scale — and the topic list suggests exactly where the next quarter’s increases will concentrate.

• The Vercel × Context AI breach has hardened into the Q2 AI-tool procurement audit template — and Google’s Agentic Defense announcement at Cloud Next is the first hyperscaler productization of the OAuth-scope governance class the breach exposed. February infection, two months of persistent OAuth access, Vercel-internal pivot, API keys / source code / database data exfiltrated, $2M BreachForums listing — the full attack template is now broadly documented, and Context AI’s “consumer OAuth tokens likely compromised” acknowledgment extends blast radius past Vercel alone. Google’s Wiz-integrated Agentic Defense at Cloud Next Day 1 foregrounds AI-tool OAuth-scope governance as a first-class product capability, which is the commercial bet that the hyperscaler-provided audit wins against the vendor-provided version. Every AI-productivity tool with Google Workspace / Microsoft Graph / GitHub App permissions is now in-scope for the same audit until scopes are rotated, sessions lifecycle-governed, and environment variables encrypted.

---

Generated on April 23, 2026 by Claude