AI developer tools 1.0 cluster: Cursor + Claude Code + Codex CLI + Gemini CLI + CodeRabbit + Graphite — every dev tool ships a 1.0 milestone in one week

8 sources

The week of 2026-08-07 saw a cluster of AI developer tool milestones: Cursor 1.0 (Composer-2 + multi-agent inline edits + codebase indexing), Claude Code 1.0 (Skills + sub-agent orchestration), Codex CLI 1.0 (image input + parallel tool calls + sandbox), Gemini CLI 1.0 (extension system + multimodal input), CodeRabbit CLI 1.0 (line-by-line AI code review), Graphite CLI 1.0 (AI-stacked PR review). The Decoder frames the cluster as 'every dev tool ships a 1.0 milestone in the same week'. The pattern: AI dev tooling is now a stable buyer-side market with two IDE-class surfaces (Cursor) and three CLI-class surfaces (Claude Code / Codex CLI / Gemini CLI), plus two code-review-class surfaces (CodeRabbit / Graphite).

Why now

The cluster is the editorial framing that turns six independent tool milestones into a single coherent 'AI dev tooling is now a stable buyer-side market' story for creators — useful because the comparison is most informative when shown side-by-side.

Why it is worth publishing

Demo potential: a side-by-side of the same coding workflow (a multi-file refactor + code review) across all six tools, measuring time-to-finish and surface quality.

Evidence basis

The Decoder + IT之家 weekly roundups + six independent vendor primary sources

“Six AI developer tools shipped 1.0-class milestones in one week — Cursor, Claude Code, Codex CLI, Gemini CLI, CodeRabbit, Graphite — and the AI dev tooling market just stabilized across two IDE-class, three CLI-class, and two code-review-class surfaces.”

Angle

Use the cluster to introduce the 'AI dev tooling is now a stable buyer-side market' pattern — IDE / CLI / code-review surfaces — and use that lens to compare approaches side-by-side.

Format

Long-form explainer

Demo idea

Record a 16-minute comparison explainer: 2 min intro on 'stable buyer-side market' framing, then 2 min per tool (Cursor / Claude Code / Codex CLI / Gemini CLI / CodeRabbit / Graphite), then a 4-min side-by-side of the same multi-file refactor + code review across all six.

Platform notes

Each tool's release notes frame its release against the competitive set the vendor cares about; The Decoder and IT之家 are editorial framing layers, not independent verification. Confirm any specific primitive or API surface against the underlying tool docs before stating it on the record.

Usable claims

Cursor shipped 1.0 — Composer-2 multi-file edit model, inline multi-agent edits (Cursor spawns sub-agents to verify and refine), codebase indexing GA with semantic search, team workspaces for shared indexes.
Anthropic shipped Claude Code 1.0 GA — Skills integration, sub-agent orchestration (Claude Code can spawn isolated sub-agents for parallel tasks), /mcp slash command for explicit MCP server connection.
OpenAI shipped Codex CLI 1.0 — image input support, parallel tool calls (multiple tool calls in one turn), sandbox execution model, AGENTS.md convention for project-level agent instructions.
Google shipped Gemini CLI 1.0 — extension system (third-party packages that add commands and tools), multimodal input support (image + audio + video), /memory slash command for persistent project context.
CodeRabbit shipped CLI 1.0 — line-by-line AI code review from the terminal, PR-comment generation, inline --review flag.
Graphite shipped CLI 1.0 — AI-stacked PR review (multiple AI reviewers produce layered feedback), stacked-diff workflow for incremental PRs, AI reviewer conflict resolver.

Evidence pipeline

From the news

Breakdown

Six AI dev tools shipped 1.0-class milestones in one week — the editorial framing ('AI dev tooling is now a stable buyer-side market') is useful but turns into a vendor directory if you don't introduce the underlying pattern. This explainer uses the cluster to introduce the 'IDE / CLI / code-review surfaces' pattern and uses that lens to compare approaches side-by-side, while keeping the per-tool differences honest (Cursor on visual context, Claude Code on Skills + sub-agents, Codex CLI on sandbox + AGENTS.md, Gemini CLI on extensions + multimodal, CodeRabbit on rich inline review, Graphite on layered reviewers + conflict resolver).

Sources

Risks

Use The Decoder and IT之家 as media-type corroboration, but read the underlying tool docs for any specific primitive or API surface before stating it on the record. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific pricing beyond the captured summary is not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific primitive signatures and behavior details beyond the captured summary are not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.

Demo ideas

Side-by-side multi-file refactor + code review across all six tools, plot time-to-finish and surface quality.
Decision tree: 'which tool for which workflow' (visual refactor → Cursor, sub-agent / Skills / parallel → Claude Code, sandboxed execution → Codex CLI, multimodal input → Gemini CLI, inline review → CodeRabbit, layered review → Graphite).
Surface comparison matrix: IDE vs CLI vs code-review — plot each tool on richness vs composability vs isolation.