AI AgentsGain a Control Plane
Eight signals point in one direction: sessions, evaluation, cache placement, transactions, and failure domains are becoming explicit control surfaces for agent systems.
RISC Machine Primer
RISC = the four systems that make an agent production-ready
A production-grade agent needs more than a brain. It must keep operating, survive failure, resist overreach, and participate in real organizational workflows.
AI Agent Radar
Claude and Qwen move sessions into the control plane
Model-switch hooks, recache estimates, named tasks, and daemon APIs show long sessions gaining authority, identity, and recovery semantics.
Microsoft and Deep Agents connect the evidence chain
Immutable checkpoints, continuation validation, and rubric hooks shift the question from whether work finished to how it can be recovered and accepted.
Mistral and AWS rewrite placement logic
One sends requests to the rank that holds the prefix; the other spreads replicas across failure domains. Performance and resilience are no longer merely model properties.
New Features Worth Watching
Claude Code 2.1.251 brings model switching and remote subtasks into the control plane
What changed: Claude Code 2.1.251 adds PreModelSwitch and PostModelSwitch hooks that can block, confirm, or annotate a model change. Resumed sessions expose cache staleness and estimated recache cost, while foreground subagent tool calls can stream to Remote Control. It also fixes post-authorization symlink-swap escapes and plugin path traversal.
Why it matters: Model changes, remote observation, and permission checks are beginning to share one execution control plane, reducing blind spots in long sessions.
Who should care: Engineering teams running long Claude Code sessions, remote coding, or multi-model workflows.
Qwen Code 0.22.3 lets one chat manage eight persistent tasks
What changed: Qwen Code 0.22.3 adds owner-scoped named sessions in Channels, with up to eight persistent tasks per chat. A standalone daemon API can create, list, resume, archive, and delete top-level sessions. It also adds PR-state binding, review-fix constraints, file-marker projection, and cross-platform process cleanup.
Why it matters: The core unit of a coding agent is shifting from one terminal turn to a named, resumable, archivable task set linked to review state.
Who should care: Teams managing parallel coding work through chat channels, Web Shell, or a background daemon.
Google AI Mode moves from travel advice to alerts and booking
What changed: Google added flight price alerts to AI Mode using prices from more than 300 airlines and travel sites, with availability in over 180 countries and territories. Points-and-miles price search is now available globally, while U.S. English users can compare hotels, review cancellation terms, and complete bookings with Google Pay.
Why it matters: Search agents are moving from recommendations into monitoring, eligibility calculations, and transactions, extending product responsibility to inventory, terms, and payment.
Who should care: Product teams building travel, commerce, search, payment, or other high-intent consumer agents.
Open-Source Finds on GitHub
Stars are a publication-time snapshot of attention, not a quality ranking. Licenses follow the official repositories and model cards.
Microsoft Agent Framework 1.16 hardens background waits and checkpoints
What changed: Microsoft Agent Framework Python 1.16.0 adds a configurable timeout for the first background-agent completion and programmatic OpenTelemetry service metadata, resource attributes, and OTLP setup. It also preserves backend-owned session snapshots, validates incremental continuation input, and prevents workflow checkpoints from being mutated outside storage.
Why it matters: Background work, telemetry, continuation, and checkpoint immutability now meet in one framework release, directly affecting diagnosis and recovery trust.
Who should care: Platform teams building background agents, observable workflows, and multi-provider session continuation in Python.
OpenHands 1.16 tightens Agent Canvas with explicit skill allow-lists
What changed: OpenHands 1.16.0 replaces its all-on skill catalog with an explicit allow-list. It also adds provider selection, a model-switching toggle, live automation phases, and the Canvas Extensions frontend. The release also includes a Linux desktop build and fixes for local backends, working directories, polling, and credential display.
Why it matters: A self-hosted agent console needs visible controls for skill activation, model choice, and automation state, not only more coding backends.
Who should care: Teams deploying OpenHands, Agent Canvas, or self-hosted consoles across multiple coding backends.
Mistral steers KV-cache hits to the correct rank
What changed: Mistral added data-parallel-aware KV event indexing and prefix scoring to its public llm-d Router branch, so independent rank caches inside one pod are no longer merged incorrectly. The scheduler can pin requests to the matching rank and strip client rank headers, preventing routing bypass.
Why it matters: Pod-level routing on a shared-port data-parallel server can send an apparent cache hit to the wrong rank, forcing recomputation and increasing time to first token.
Who should care: Infrastructure teams operating vLLM, SGLang, llm-d, or large prefix-cache inference clusters.
Global Technology and Market Watch
Deep Agents 0.7.11 adds SDK hooks for rubric graders
What changed: LangChain’s Deep Agents 0.7.11 adds SDK integration hooks that let external rubric graders enter the post-run evaluation path. This small release does not expand model or tool access; it creates an explicit handoff where a task result can be scored against defined criteria.
Why it matters: Agent evaluation needs to move from one-off offline scripts into a reusable SDK lifecycle that links task standards, run evidence, and regression results.
Who should care: Engineering teams maintaining agent SDKs, regression evaluation, quality gates, or task acceptance systems.
Salesforce spreads Agentforce inference across availability zones
What changed: AWS says Salesforce Agentforce uses SageMaker Inference Components with AvailabilityZoneBalance and SPREAD to distribute model copies across availability zones under a maximum-imbalance constraint. Scale-out and scale-in preserve the distribution, while background CONSOLIDATION repairs skewed placement.
Why it matters: Shared GPUs can reduce cost, but default placement may concentrate replicas in one failure domain. Agent-service availability has to become a scheduler constraint.
Who should care: Platform teams hosting enterprise agents, shared-GPU inference, and multi-zone service-level agreements on SageMaker.
Sources
- Claude Code: Claude Code 2.1.251 brings model switching and remote subtasks into the control plane Official release
- Qwen Code: Qwen Code 0.22.3 lets one chat manage eight persistent tasks Official release
- Google Search AI Mode: Google AI Mode moves from travel advice to alerts and booking Official announcement
- Microsoft Agent Framework: Microsoft Agent Framework 1.16 hardens background waits and checkpoints Official open-source release
- OpenHands: OpenHands 1.16 tightens Agent Canvas with explicit skill allow-lists Official open-source release
- Mistral llm-d Router: Mistral steers KV-cache hits to the correct rank Official repository update
- Deep Agents: Deep Agents 0.7.11 adds SDK hooks for rubric graders Official open-source release
- AWS and Salesforce Agentforce: Salesforce spreads Agentforce inference across availability zones Official architecture case study
