What to compare
- harness and pinned version
- release channel and date
- changed defaults, permissions and tools
- supported models and providers
- licence and data terms
Read the sources
Claude Code changelog ↗
Version-by-version changes to Claude Code, generated from the changelog in its public repository.
Public documentation. The page is long; read only the entries between the pinned and target versions. Claude Code is proprietary. Its repository states that use is subject to Anthropic's Commercial Terms of Service.
OpenAI Codex CLI releases ↗
Tagged releases of OpenAI's open-source Codex command-line coding agent.
Read the release notes on GitHub. Alpha pre-releases appear beside stable releases. Apache-2.0 licensed. Using OpenAI models through it is governed by OpenAI's terms.
OpenCode releases ↗
Tagged releases of the open-source OpenCode coding agent.
Read the release notes on GitHub. Older links under the sst organization redirect to this repository. MIT-licensed. Model access is configured separately and governed by each provider's terms.
Gemini CLI release notes ↗
Release notes for Google's open-source Gemini CLI across its stable, preview and nightly channels.
Public documentation on the site that the project's GitHub repository lists as its homepage. The project recommends the stable channel for general use. Apache-2.0 licensed. Using Gemini models through it is governed by Google's terms.
Cursor changelog ↗
Dated release notes for the Cursor editor and its agent features.
Public page. This collection does not install, configure or sign in to the editor. Cursor is proprietary software. Check its terms and data settings before standardizing a team on a version.
Aider release history ↗
Release history of the open-source aider terminal coding assistant, including unreleased changes on its main branch.
Public page. Check the date of the newest release before assuming active maintenance. Apache-2.0 licensed. Model access is configured separately and governed by each provider's terms.
When to look again
When a harness the team uses publishes a stable release, and before changing the team's standard setup.
Give your agent this question
Summarize changes between the team's pinned version and the newest stable release of each named harness. Flag changes to defaults, permission prompts, sandboxing and supported models, then propose a short trial on a real repository task before standardizing.