AI News — June 5, 2026

Coding agents

• [2026-06-02] Cognition — retired the Windsurf brand and relaunched the editor as Devin Desktop, shipped as an over-the-air update (plans, pricing, settings, and extensions carry over). The centerpiece is the Agent Command Center: a Kanban board of every agent you’re running — local and cloud — grouped by status (in progress, blocked, ready for review). The local agent Cascade is replaced by Devin Local, rewritten from scratch in Rust, up to 30% more token-efficient, and now able to spin up subagents for subtasks; Cascade stays available only through July 1. It folds the IDE, the autonomous cloud agent, a CLI, and review into one “Devin” brand across four surfaces. (official, source, source) (This shipped during Build and got buried under the Microsoft news — surfacing it now as the window’s biggest uncovered coding-agents story.)

  The shift worth noting isn’t the rename but the surface: a board of running agents reframes the IDE from a place you write code into a console you supervise work from, so the day-to-day skill tilts toward triaging and unblocking agents rather than typing into a single buffer.

  For Software Developers: On a multi-part task — say a refactor spanning several modules — Devin Local can fan out a subagent per subtask while the Command Center groups them by status, so you watch one board and step in only on the cards marked blocked or ready for review instead of babysitting one linear session.

• [2026-06-02] Cognition — Devin Desktop launches with support for the Agent Client Protocol (ACP), an open protocol that standardizes editor↔agent communication the way LSP standardized language servers — so any ACP-compatible agent can run inside any ACP-compatible editor. At launch Devin Desktop drives Codex, Claude Agent, and OpenCode through it, alongside a new Spaces feature for sharing context (sessions, PRs, files) across agents. The interesting part isn’t the rebrand but the bet: managing several heterogeneous agents from one surface only works if there’s a common protocol, and Cognition is pushing ACP as that layer rather than locking you to its own agent. (official, source)

  The catch is the one LSP faced too: a protocol only delivers the no-lock-in promise once many editors and agents speak it, so the signal to watch is whether hosts beyond Devin Desktop adopt ACP — until then it’s a well-designed API with a single implementation.

  For Solution Architects: ACP gives you an integration contract to standardize on instead of a vendor — a team can let one engineer drive Codex and another Claude Agent inside the same Devin Desktop, with Spaces keeping sessions, PRs, and files consistent across them — so you mandate the protocol and leave individual agent choice open.

Watch list

• Gemini 3.5 Pro (this month): at I/O (May 19) Google said 3.5 Pro was already in internal use and would land “next month” — i.e. June — with no committed date. Google ships every 3.x model as a single blog.google post with the full benchmark grid, so watch for that model card, pricing, and the API model name on day one. The Flash tier already leads some agentic/coding benchmarks, making the Pro drop the one to watch for independent numbers. (source)

  What would make it significant is less the headline score than the API price: if it lands aggressively, Pro becomes a plausible default to swap a coding agent onto rather than just another benchmark entry.

• Cascade end-of-life (July 1): with Windsurf now Devin Desktop, the old Cascade local agent is deprecated and disappears July 1, replaced by the Rust-based Devin Local. Anyone with Cascade-specific workflows or muscle memory has a four-week migration runway. (source)

  The migration risk worth probing now is config and behavior parity — Devin Local is a from-scratch Rust rewrite, not a renamed Cascade, so workflows leaning on specific Cascade settings may need re-authoring rather than carrying over.

• Anthropic developer billing split (June 15): now widely reported with specifics — Claude Agent SDK, claude -p, Claude Code GitHub Actions, and third-party agents move off your subscription limit onto a separate monthly credit pool (~$20 Pro / $100 Max 5x / $200 Max 20x), metered at full API rates with no rollover. Anthropic still hasn’t detailed it on an official page. If it lands as described, a subscription seat no longer covers programmatic usage — worth pricing out ahead of the date. (source, source) (unconfirmed)

  Should it pan out, the sharpest impact is on bursty automation — CI runs and GitHub Actions that fire per-commit — where full-rate metering with no rollover turns an unpredictable usage spike into an unpredictable bill.

• MCP spec 2026-07-28 final: stateless core, Tasks, and MCP Apps move to stable, and clients must validate the iss parameter per RFC 9207. Server operators relying on sticky sessions will need to migrate — worth auditing deployments before the date. (source)

  Beyond the sticky-session work, the iss-validation requirement is a client-side change as much as a server one — even deployments that never used sticky sessions should confirm their clients pass and check iss, or they risk being non-conformant on the stable spec.