AI Coding — June 6, 2026

The read

Coding agents are bulldozers, not replacements — humans still frame the problem. When everyone has background agents and million-token context, differentiation shifts to taste, review, and what you ship, not whether you can generate code.

What moved

• Intelligent Terminal 0.1 ships ACP-native agent pane in Windows shell — Windows Command Line Blog Microsoft released Intelligent Terminal 0.1, an experimental Windows Terminal fork with a docked agent pane connected via Agent Client Protocol (ACP). GitHub Copilot CLI is the default agent, but any ACP-compatible CLI is configurable. Failed commands trigger auto-detected errors in the status bar; clicking loads shell output into the agent pane for explanation and fixes. Background agent tasks run in new tabs, and Command Palette prompt mode (?query) injects active-pane context without blocking the shell. Builder angle: Terminal-first developers can delegate multi-step shell fixes to any ACP agent without leaving the command line or manually copying error output.

• Cursor SDK adds custom tools, nested subagents, and headless auto-review — Cursor Changelog Cursor’s June 4, 2026 SDK release lets local agents register custom tools via function definitions exposed through a built-in custom-user-tools MCP server, visible to all nested subagents. Subagents can spawn subagents to arbitrary depth. Headless runs can set local.autoReview to route tool calls through a classifier steered by permissions.json allow/block instructions. Persistence options expand beyond SQLite to JSONL and custom LocalAgentStore implementations; each send() carries a platform requestId for CI correlation. Builder angle: CI and internal scripts can embed coding agents with first-class custom tools and graded auto-approval instead of standing up separate MCP servers or interactive review loops.

• GitHub Agent tasks REST API exposes programmatic Copilot cloud agent runs — GitHub Changelog Copilot Pro, Pro+, and Max users can start and track Copilot cloud agent tasks via a public-preview REST API authenticated with PATs or OAuth tokens. Cloud agents run in an isolated development environment, make and validate code changes, and open pull requests. Documented use cases include fan-out refactors across repositories, one-click repo scaffolding from internal portals, and scheduled release preparation with release notes. Builder angle: Background coding agents can be triggered from scripts, portals, or schedulers instead of only from IDE or Copilot app sessions.