Cursor adds an auto-review mode so agents can work longer without constant approvals

What changed: Cursor added Auto-review Run Mode, which lets its coding agent run longer with fewer approval prompts while still checking risky actions. Shell, MCP, and Fetch calls can be allowed, sandboxed, rerouted, or sent back to the user for approval by a classifier subagent.

Why it matters: This is a practical middle ground between “approve every step” and “let the agent do anything.” Teams using Cursor for larger refactors or bug-fixing runs can reduce interruptions while keeping a review layer around commands, external tool calls, and web fetches.

Try/watch: Test it on a low-risk repo first, then add custom instructions for what your team considers safe, suspicious, or always-needs-approval.

GitHub gives admins a clearer view of who is actually using agent workflows

What changed: GitHub’s Copilot usage metrics API now classifies engaged users into adoption phases over a rolling 28-day window, including code-first, agent-first, and multi-agent usage. The reports also group enterprise and organization metrics by phase, including pull requests created, merged, and reviewed, plus median time-to-merge averages.

Why it matters: Buyers finally get a better way to separate “people have Copilot licenses” from “people are using agentic workflows.” For founders and engineering leaders, this makes rollout decisions more measurable: train teams stuck at autocomplete, or invest more where developers are already using cloud agents, code review, CLI, or the Copilot app.

Try/watch: If you manage Copilot, pull the new fields into your internal adoption dashboard and compare agent-first usage against actual PR throughput and review quality.

Claude Code’s dynamic workflows push coding agents toward parallel work

What changed: Reworked reported that Anthropic’s dynamic workflows feature for Claude Code lets Claude break complex coding tasks into subtasks, run multiple subagents in parallel, and synthesize the results after internal checking. The feature is in research preview across Claude Code CLI, Desktop, and VS Code extension for Max, Team, and Enterprise plans.

Why it matters: This is useful for codebase-wide migrations, audits, and modernization work where one agent working linearly is too slow. The buyer takeaway is not “replace the team,” but “package big maintenance work into well-scoped, test-backed jobs that can be split and checked.”

Try/watch: Use it only where you have strong tests and clear rollback paths; parallel agents can multiply both useful output and expensive mistakes.