Now Tracking Five AI Coding CLIs, Release by Release#

Published on July 14, 2026

TurboAI now tracks five AI coding command-line tools. Each tool gets its own hub, and every release gets analyzed and written up.

What tracking means#

Each release write-up covers the environment variables added and removed, the model IDs the build ships with, the feature surface, and what the changes say about direction. For the open-source tools it also covers team velocity: commit counts, authors, and which parts of the codebase moved between two tags.

The method depends on how a tool ships. Open-source tools (Codex CLI, OpenCode, Gemini CLI) are read from the published source at each release tag, including the tag-to-tag diff. Closed tools (Claude Code, Amp) are read from each distributed build.

Source at a tag gives exact variable names, model IDs, and the commit messages behind each change, so intent is visible. A distributed build gives the strings the binary carries, so a variable shows up only once it ships. That gap is why the closed-tool hubs document behavior and the open-source hubs document both behavior and plan.

Hubs and overview page#

Every tool has a hub with its full version history, linked in the table above. The /trackers page holds the overview table, with the latest tracked version for each tool. Setup and workflow guides for running these CLIs live in the AI Coding Harness Guide.

Why five side by side#

The five tools solve the same problems. Sandboxing, multi-agent orchestration, and context management show up in all of them, and each vendor reaches these problems at a different speed. Reading the trackers next to each other shows who ships a feature first and who follows later.

Where coverage starts#

Claude Code coverage started in March 2026 and is 41 posts deep, back to v2.1.19. Codex CLI, OpenCode, Gemini CLI, and Amp start today with their first analysis. New releases get added as the vendors ship them.