Summary
A mid-July 2026 competitive scan comparing Claude Code (v2.1.195‑206) and Cursor (v3.11), with implications for the Yoyo coding agent. The scan focuses on features that manage developer attention: side chats, background subagents, transcript search, and configuration‑friction reduction (e.g., /doctor as a fixer). Both competitors outpace Yoyo in durability, context‑cost auditing, and background‑by‑default parallelism.
Key Points
- Both Claude Code and Cursor are shifting focus from raw model capability to managing developer attention — side chats, background subagents, and transcript search are now core features.
- Claude Code’s
/doctorevolved into a unified diagnose‑and‑repair tool that audits unused skills/MCP/plugins, deduplicates configs, and proposes cleanup with user confirmation. - Cursor side chats are durable, full‑agent conversations branched off a main agent with pull‑back via
@mention; Yoyo’s/sideis stateless and one‑shot. - Background subagents are default in Claude Code; Cursor offers isolated‑VM background agents that open PRs.
- Claude Code’s browser control (“Claude in Chrome”) and Cursor’s cloud agents expand beyond terminal CLI; Yoyo lacks this (out of scope).
- Yoyo’s
/spawnand/sideare in the right design family but are shallower: no durable side threads, no unified diagnose‑and‑repair, and no background‑by‑default subagents surfacing results into the main session.
Concepts
- /doctor (Claude Code): Unified diagnose‑and‑repair command (alias
/checkup) — checks install health, finds unused skills/MCP/plugins, deduplicates local vs checked‑in CLAUDE.md, trims derivable content, flags slow hooks; reports first, asks before fixing. - Side chats (Cursor): Durable agent threads launched via
/sideor/btwfrom a running main agent. Each keeps its own context, is revisitable, and can pull results back into the main thread via@mention. - Background subagents: Agents that execute in the background while the main conversation continues, absorbing returned results. Claude Code defaults to this; Cursor uses isolated VMs. Yoyo’s uses worktree isolation but is not background‑by‑default.