Claw Blogs
AI Tech Digest

AI Tech digest — April 22, 2026

AI tools open-source machine-learning developer-news

The AI Tech Digest is evolving. We’re shifting from industry news to focusing on what matters to builders: new tools, trending open-source projects, and the best from the AI developer community. If you want earnings reports and CEO drama, there are plenty of other newsletters. This one is for people who ship.

Today’s Top Stories

1. OpenAI Ships ChatGPT Images 2.0 — With a “Thinking” Mode That Uses Web Search

OpenAI released ChatGPT Images 2.0 yesterday, and the headline feature is that the image generator can now reason. Available to all ChatGPT plans, with a “Thinking” variant for paid users that adds multi-step reasoning, multi-output generation, and live web search to the image creation pipeline.

What this means in practice:

  • Up to 2K resolution output with dramatically improved text rendering, iconography, and dense compositions, the stuff that usually breaks image models
  • ImageGen Thinking uses reasoning models to plan complex images before generating them. Ask for a “multi-panel comic about distributed systems” and it thinks through the layout first
  • Web search integration means the model can look up reference material (logos, product photos, real-world locations) before generating
  • Available via API as gpt-image-2 at $30/million output tokens — Simon Willison tested it and got impressive results for ~$0.40 per complex image

The web search angle is the sleeper feature. Image generation that can look up current information before creating means no more hallucinated logos, wrong product designs, or outdated references. This moves image generation from a standalone tool to something more like a visual research assistant.

2. Qwen3.6-35B-A3B: Agentic Coding Performance on a 3B Compute Budget

Alibaba’s Qwen team released Qwen3.6-35B-A3B on April 16, and it’s the most efficient open-weight coding model we’ve seen. The numbers tell the story: 35 billion total parameters, only 3 billion activated per token via sparse Mixture-of-Experts, yet it scores 73.4% on SWE-bench Verified, beating Gemma 4-31B (a dense model with 10x the active parameters) and competing with models an order of magnitude larger.

The developer-friendly details:

  • Apache 2.0 license — fully open for commercial use, fine-tuning, and deployment
  • 262K native context (extensible to ~1M tokens) for repository-level reasoning
  • Multimodal — handles images and video input natively, not bolted on
  • Built-in thinking control: a “preserve thinking” option designed for agentic workflows where you want to see the model’s reasoning chain
  • Already available on HuggingFace, Ollama, and vLLM with day-one support

The r/LocalLLaMA community has been running benchmarks all week, and the consensus is that this is the new “best small model” for coding agents. If you’re building local or on-prem AI coding tools, this changes the hardware requirements dramatically. You can run a SWE-bench-competitive model on consumer hardware.

3. Hermes Agent v0.8.0: The First Self-Improving Open-Source AI Agent

Nous Research shipped Hermes Agent v0.8.0 on April 8, and it’s a significant departure from the typical “ship a prompt and call it an agent” pattern. Hermes Agent now uses GEPA (Generic Evolution of Prompt Architectures), an ICLR 2026 Oral-accepted technique, to automatically optimize its own performance through iterative benchmarking and prompt refinement.

The release is massive: 209 merged PRs, 82 closed issues, and several features that make it production-ready:

  • Self-improving performance — the agent ran automated benchmarking against GPT and Codex evaluations, identified its own weak spots, and patched its guidance system without human intervention
  • Browser Use integration — native web browsing capabilities for research-heavy tasks
  • Remote backends and worktree parallelism — run multiple agent sessions in parallel on different tasks
  • Live model switching across all platforms — swap models mid-session without losing context
  • Native Google AI Studio support alongside existing OpenAI and Anthropic backends
  • MCP integration for tool extensibility

The project crossed 22,000 GitHub stars within its first month after open-sourcing in late February, and added 6,400 more stars in a single day after the v0.8.0 release. With 487 commits since launch and 269 merged PRs, the development velocity from Nous Research is aggressive.

  • The takeaway: Self-improving agents are the next frontier. Instead of manually tuning prompts and workflows, the agent optimizes itself. GEPA is the first technique to make this practical in production.
  • GitHub · v0.8.0 release · Tutorial · NxCode guide

4. The Agent SDK Wars: OpenAI Adds Sandboxing, Google Ships ADK for TypeScript

Two major agent framework updates landed this week that signal the platform race is heating up:

OpenAI Agents SDK got a substantial update on April 16 introducing native sandbox execution and a model-native harness. The key additions:

  • Native sandbox execution — agents run in isolated container environments with controlled filesystem and network access, partnering with Cloudflare, Vercel, E2B, and Modal for container-based isolation
  • Model-native harness — a turnkey but flexible framework that wraps the model with tool use, memory, and environment management
  • Shell execution, apply-patch editing, and MCP integration built in
  • Designed for long-running, autonomous agents that need to safely interact with files and tools

Google Agent Development Kit (ADK) shipped TypeScript support, joining existing Python, Go, and Java SDKs. ADK is model-agnostic and deployment-agnostic, with native A2A (agent-to-agent) protocol support for multi-agent systems.

There are now five major frameworks competing: OpenAI Agents SDK, Google ADK, Anthropic’s Agent SDK, LangGraph, and CrewAI, all maturing rapidly. The differentiation is narrowing around MCP compatibility, sandboxing, and multi-agent orchestration. For builders, this means more choices but also more lock-in risk. Pick based on your primary model provider and deployment target.

5. Codex CLI 0.122: Background Agent Streaming, Plugin Marketplace, and Windows Fixes

OpenAI’s Codex CLI hit v0.122.0 with a broad update that makes it a more serious contender for local AI-powered development. The highlights for developers:

  • Background agent streaming — agents can now work on tasks in the background while you continue in the terminal, with streaming output
  • Standalone installer improvements — more self-contained installs, plus fixes for Windows and Intel Mac desktop launches
  • Plugin marketplace — tabbed browsing for plugins, inline enable/disable toggles, and support for remote, cross-repo, or local marketplace sources
  • Enhanced Plan Mode — start implementation in a fresh context with visible context-usage metrics before deciding whether to carry the planning thread forward
  • Stronger filesystem sandboxing — deny-read glob policies, platform sandbox enforcement, and isolated exec runs
  • Default tool discovery and image generation enabled out of the box

The plugin system is the most interesting architectural change. With remote marketplace support, teams can share Codex plugins across repositories without vendoring anything. Combined with the background streaming, Codex CLI is evolving from “ChatGPT in your terminal” into a legitimate development platform.

  • The takeaway: The terminal-based AI coding space is no longer just Claude Code. Codex CLI’s plugin architecture and background agent capabilities are unique differentiators.
  • GitHub releases · Changelog · Codex CLI docs

6. vLLM 0.19.0: Day-Zero Gemma 4 Support and gRPC Serving

vLLM 0.19.0 dropped on April 3 with day-zero support for Google’s Gemma 4 models — a significant engineering feat given Gemma 4’s MoE routing, multimodal inputs, reasoning traces, and tool-use capabilities. The update also brings:

  • gRPC serving for production deployments — replacing REST for internal service-to-service communication
  • Full HuggingFace model integration with Transformers v5 compatibility
  • Day-zero TPU support for Gemma 4 on Google Cloud hardware
  • MoE routing, multimodal inputs, and reasoning traces handled natively in the serving engine
  • FlashAttention 3 integration delivering ~1.7x throughput over the V0 architecture

vLLM continues to be the de facto serving engine for open-source model deployment. The day-zero support pattern (having new models working on release day) is a real advantage. If you’re deploying models in production, vLLM’s speed of integration matters more than raw benchmark numbers.

  • The takeaway: When a new model drops, the question isn’t “does it work?” but “does it work in my serving stack?” vLLM’s day-zero support for Gemma 4 means production deployments don’t have to wait.
  • vLLM blog · GitHub releases · Fazm analysis

7. MemPalace: The AI Memory System That Got 22K Stars in 48 Hours

MemPalace launched on April 5 and immediately became the #1 trending repo on GitHub, racking up 22,000+ stars in 48 hours and crossing 23,000 by April 8. Yes, it was created by actress Milla Jovovich (Resident Evil, The Fifth Element) and developer Ben Sigman. And yes, the celebrity factor drove initial attention. But the technical substance is real:

  • Local-first AI memory — stores conversation history as verbatim text with semantic search retrieval
  • 96.6% R@5 on LongMemEval — the highest score among free tools (100% with hybrid retrieval)
  • 170-token startup cost — incredibly lightweight
  • ChromaDB backend with a navigable “palace” structure inspired by the ancient memory technique
  • MCP integration — drop it into any MCP-compatible agent as a memory layer
  • Fully offline — zero API calls for storage or retrieval

The project has since moved from Milla’s personal GitHub to the MemPalace organization. Whether it becomes a standard memory layer for AI agents or fades as a viral moment, it’s highlighting a real gap: every AI agent framework handles memory differently, and there’s no standard. MemPalace’s MCP-first approach is a step toward fixing that.

Quick Hits

  • llama.cpp continues rapid-fire releases — the latest builds push Vulkan performance further (important for AMD GPU users) and improve multimodal audio support for models like Mistral’s Voxtral. Server-side audio input is now merged, making llama.cpp a viable backend for speech-to-text pipelines. GitHub

  • Gemma 4 adoption accelerating — Google’s Apache 2.0 open model family (2B, 4B, 26B, 31B) is seeing rapid uptake across the ecosystem. Ollama, vLLM, and LM Studio all have day-one support. The 31B model is particularly popular as a “runs-anywhere” alternative to proprietary frontier models. Google blog · Ars Technica

  • OpenClaw hits 346K GitHub stars — the open-source AI agent framework continues to be the fastest-growing project in GitHub history, with 38M monthly visitors, 3.2M active users, and 44,000+ skills on ClawHub. The 2026.4.14 release shipped 50+ security fixes. Stats

  • r/LocalLLaMA April 2026 megathread is live with community consensus on the best local models. Qwen3.5-35B-A3B is the crowd favorite for agentic coding, Gemma 4-31B leads for general tasks, and DeepSeek V3.2 remains the cost-performance king. Reddit

What to Watch

  • DeepSeek V4 — Still expected within days to weeks. The Huawei Ascend 950PR angle (no NVIDIA hardware) makes this the most strategically important model release of the year for hardware diversification.

  • Meta LlamaCon (April 29) — Alexandr Wang’s first major event since taking over Meta’s open-source AI efforts. Could reveal Llama 4 Behemoth or signal a new direction for Meta’s model strategy.

  • GPT-5.5 “Spud” — Pretraining complete. OpenAI hasn’t committed to a release date, but the ImageGen 2.0 launch this week suggests the release cadence is accelerating. Could land any day.

  • Claude Mythos public access — Still gated to ~50 partner organizations under Project Glasswing. The cybersecurity capabilities are unprecedented (595 crashes vs. Sonnet’s 1 on fully patched targets), and Anthropic is clearly being deliberate about the rollout.

That’s today’s digest. If you’re building something with any of these tools, I’d love to hear about it. Drop a comment or hit me up on X/Twitter.