Claude Code ships a substantive v2.1.122 plus a same-day OAuth hot-fix in v2.1.123, while Anthropic and OpenAI brief House Homeland Security on AI cyber capability and Goldman Sachs cuts Hong Kong banker access to Claude — a Wednesday where the visible action was procurement-side rather than model-side.

AI Digest — April 29, 2026

Your daily deep-dive on AI models, tools, research, and developer ecosystem news.

🔖 Project Releases

Claude Code

Claude Code v2.1.122 (April 28) is the substantive release of the day, followed within hours by a single-line hot-fix in v2.1.123 (April 29) for an OAuth 401 retry loop that surfaced when CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1 was set. The v2.1.122 changes most likely to surface immediately:

ANTHROPIC_BEDROCK_SERVICE_TIER — a new env var that picks default | flex | priority and is forwarded as the X-Amzn-Bedrock-Service-Tier header on each request. The first time Bedrock service tiers have been exposed to the CLI as a config knob; useful when an account has reserved priority capacity that the default tier won’t route through.
/resume finds sessions by PR URL — paste a GitHub, GitHub Enterprise, GitLab, or Bitbucket PR URL into the resume search box and it locates the session that produced that PR. Closes the inverse-lookup gap that previously forced you to scroll session history by description.
/mcp shows shadowed claude.ai connectors — when a manually-added MCP server has the same upstream URL as a claude.ai connector, the connector now appears with a hint to remove the duplicate. Previously the connector silently disappeared from the list.
OpenTelemetry: numbers as numbers — api_request and api_error log events now emit numeric attributes as numbers, not strings, and a new claude_code.at_mention log event covers @-mention resolution. Both are downstream-pipeline fixes that anyone aggregating Claude Code telemetry into a metrics store has been working around.
/branch regression fix — forking a session whose history contained entries from rewound timelines no longer produces forks that fail with tool_use ids were found without tool_result blocks. This is the kind of breakage that doesn’t surface in a fresh-session demo but bites long-running multi-fork workflows.
Quieter Vertex AI / Bedrock cleanup landed alongside: output_config: Extra inputs are not permitted no longer appears on session-title generation; Vertex count_tokens 400s behind proxy gateways are fixed; and Bedrock application-inference-profile ARNs now show the /model Effort option and receive output_config.effort.

Note

Two substantive Claude Code releases inside a week (v2.1.121 on April 28, v2.1.122 the same evening, v2.1.123 the next morning) is a faster rhythm than the early-April cadence. The shape isn’t a single big feature — it’s the Bedrock plumbing, the inverse-lookup affordances, and the long-tail telemetry fixes all moving in parallel. The OAuth hot-fix in v2.1.123 is the kind of release that suggests the regression was caught quickly, not that the codebase is unstable.

Beads

No new release this week. Latest is still v1.0.3 (April 24) — the bd gate create, bd prune, and BD_JSON_ENVELOPE release covered in 2026-04-26-AI-Digest.

OpenSpec

No new release this week. Latest is still v1.3.1 (April 21) — the canonical-artifact-path and telemetry-fix release covered in 2026-04-22-AI-Digest.

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

Qwen 3.6 27B BF16 vs Q4_K_M vs Q8_0 GGUF evaluation (626 upvotes, 141 comments, r/LocalLLaMA) — head-to-head benchmark of three quantization formats on HumanEval, HellaSwag, and a function-calling suite. The author’s numbers for Qwen3.6-27B: Q4_K_M is ~1.45× faster than BF16, with ~48% lower peak RAM and a ~68.8% smaller file. Function-calling scores are near-identical across all three formats; the cost is concentrated in HumanEval, which drops ~5.5 points from BF16 to Q4_K_M. The takeaway picked up downthread is the one practitioners have been guessing at: Q4_K_M remains the default sweet spot for consumer-hardware inference, and the codegen gap is the thing to register if Qwen 3.6 is doing pure code work rather than reasoning or tool-use.

Nemotron-3-Nano-Omni-30B-A3B-Reasoning, New model? (183 upvotes, 71 comments, r/LocalLLaMA) — discovery thread for an unannounced NVIDIA release on Hugging Face: a 30B-parameter audio + image + video → text reasoning model published in BF16 and GGUF formats without an accompanying NVIDIA blog post. Selftext is empty; what’s drawing the comment volume is the size class (A3B in the name suggests a 3B-active mixture-of-experts) and the multimodal scope landing as a stealth drop rather than a launch event. Treat as preliminary until NVIDIA documents it; the pattern of large-shop “leaks first, post second” model releases has been more frequent over the last two months.

Visualizing Loss Landscapes of Neural Networks [P] (101 upvotes, 8 comments, r/MachineLearning) — interactive web tool that maps optimizer trajectories through loss landscapes using the Li et al. (NeurIPS 2018) filter-normalization method. Runs entirely client-side, supports MLPs through ResNet-8, and ships with synthetic and real-data examples. The novelty is pedagogical: it converts a high-dimensional optimization story into an observable 3D surface for an audience that has read the paper but hasn’t watched the trajectory move. Worth flagging that filter-normalized 2D slices can hide as much as they show — comments raise this; the tool is a useful starting point, not a substitute for reading the original geometry.

📰 Technical News & Releases

Anthropic and OpenAI Brief House Homeland Security on AI Cyber Threats

Source: Axios | https://www.axios.com/2026/04/28/openai-anthropic-congress-cyber-briefings

Anthropic and OpenAI separately briefed House Homeland Security Committee staff on April 28 on AI-enabled cyber capability and the disclosure protocols each lab is using around it. Anthropic continued to withhold public release of Claude Mythos Preview — the cybersecurity-optimized model first announced via Project Glasswing (covered in 2026-04-24-AI-Digest) — and OpenAI described its release approach for GPT-5.4-Cyber as tiered: not a broad public rollout, just consortium and design-partner availability with staged capability unlocks.

The careful read here is narrow. One Hill briefing isn’t evidence that government buy-in is becoming a hard deployment gate for cyber-aware frontier models, and neither lab framed it that way. What it is evidence of is two competitors converging on a “talk to government first, then ship” sequence around capabilities that have plausible offensive use — a posture that wasn’t present at the GPT-5 or Claude Opus 4 launches a year ago. The arc to watch is whether Mythos and GPT-5.4-Cyber ship with disclosure boilerplate that references these briefings; that would be the first concrete sign the briefings are becoming part of the launch artifact rather than a one-off PR move.

Goldman Sachs Cuts Hong Kong Banker Access to Claude

Source: Bloomberg | https://www.bloomberg.com/news/articles/2026-04-29/goldman-staff-in-hong-kong-lose-access-to-anthropic-s-claude

Goldman Sachs revoked access to Anthropic‘s Claude for staff based in Hong Kong on April 28, citing a strict reading of contractual region restrictions in the bank’s Anthropic agreement. Bloomberg’s reporting frames the change as compartmentalization rather than a full vendor rip-out — Claude continues to be used in Goldman’s other geographies; Hong Kong specifically has been carved out. The Financial Times corroborated the carveout the next morning.

What this is, narrowly: a single major financial-services customer exercising a regional contract clause. What it isn’t yet: evidence that enterprise contracts for frontier AI are broadly incorporating geopolitical clauses, or that other US banks with Hong Kong desks are about to follow. Hong Kong-specific governance is unusually heavy in financial services in a way it isn’t in most enterprise software, and Goldman’s contract reading may be a function of that vertical rather than a sector-wide shift. The pattern worth watching is whether Morgan Stanley, JPMorgan, or Citi — all with substantial HK trading operations — make analogous moves over the next four to six weeks. Until then, “Goldman moves first” is the right framing.

Tip

Today’s two news stories share a thread that’s more interesting than either alone: frontier labs and their largest enterprise customers are negotiating the terms under which model capability gets deployed, with both Congressional briefings and contract-level regional carveouts as expressions of the same caution. Read both as procurement-side governance stiffening compared to a year ago, not as regulatory step-change.

🧭 Key Takeaways

Claude Code’s release cadence is feature-bearing again. v2.1.122 lands Bedrock service-tier control, PR-URL session lookup, OpenTelemetry numeric attribute fixes, and the /branch rewound-timeline crash fix in a single drop, with v2.1.123 right behind as a one-line OAuth hot-fix. The velocity (three releases in two days, two of them substantive) is the signal worth registering, not any single feature.
Frontier offensive-capability disclosure now has a Hill cadence. Anthropic and OpenAI separately briefed House Homeland Security on April 28 with their respective frameworks for handling cyber-aware models. Claude Mythos Preview remains withheld; GPT-5.4-Cyber is gated to design partners. The new posture across both labs — talk to government first, then ship — is a procurement-process change, not yet a regulatory one.
Enterprise carve-outs by jurisdiction are surfacing publicly. Goldman Sachs‘s Hong Kong banker cutoff is one data point, but it’s the first major-bank, identifiable-geography carve-out of frontier AI access to leak. The question for the next month is whether other US banks with HK operations follow; until then, treat as a Goldman-specific contract reading rather than a sector trend.
Q4_K_M is the practitioner default, with a measurable codegen tax. The Qwen 3.6 27B quantization study quantifies a tradeoff that consumer-hardware users have been guessing at: ~1.45× throughput and ~48% RAM reduction at ~5.5-point HumanEval cost. For reasoning and tool-use the gap effectively disappears; for pure codegen, the cost is real and BF16 starts to make sense again.

Generated on April 29, 2026 by Claude