Changelog

We’ve consolidated the Smarter Testing CLI experience under the CircleCI CLI. Please apply these changes by September 14, 2026.

Installation

The testsuite is now managed as a CircleCI CLI extension. Remove the standalone tap and install via the CLI:

$ brew uninstall circleci/tap/circleci-testsuite
$ circleci extension install testsuite

Install the CLI here: https://cli.circleci.com/

Command changes

testsuite is now a top-level command with dedicated subcommands:

• circleci run testsuite → circleci testsuite run
• circleci testsuite "ci tests" → circleci testsuite run "ci tests"
• circleci testsuite "ci tests" --doctor → circleci testsuite doctor "ci tests"
• circleci testsuite "ci tests" --lists-tests-only → circleci testsuite list-tests "ci tests"

Flag changes

Test impact analysis flags have been renamed for consistency:

• --test-selection / --select-tests → --run-tests
• --test-analysis → --analyze-tests

Plugins now on public registries

Smarter Testing plugins have moved to a monorepo (circleci-public/smarter-testing-plugins) and are published to their respective package registries:

• npm: @circleci/jest-circleci-coverage, @circleci/cypress-circleci-coverage, @circleci/mocha-circleci-coverage, @circleci/vitest-circleci-coverage, @circleci/v8-coverage-collector
• PyPI: pytest-circleci-coverage
• RubyGems: rspec-circleci-coverage

The Fix with Claude Code option is now accessible from two additional surfaces.

- On the Pipelines page, click the wrench icon (🔧) on any failing workflow in the workflows list.

- Inside a failing workflow, click the Fix dropdown in the header toolbar.

In both cases, selecting Fix with Claude Code opens your terminal with Claude Code pre-loaded to diagnose the failure and produce a fix.

You can now triage and fix failing workflows using Claude Code directly from the CircleCI UI.

Navigate to a pipeline run, click the wrench icon on a failing workflow, and select Fix with Claude Code. This opens Claude Code in your terminal with a pre-loaded prompt that pulls failure diagnostics using circleci run get --failure-report and produces a fix for the root cause.

You can now generate a condensed failure report for any pipeline run using circleci run get --failure-report. The report prints output for every failed step, formatted for AI agent consumption.

Pipe it to your local coding agent to diagnose and fix failing builds. By default, the CLI retrieves the latest run from your current git remote and branch. If the run did not fail, the report returns nothing. Pass a run ID to retrieve a specific run instead.

A new version of the CircleCI CLI is in Beta.

The new CLI has several enhancements including a built in MCP server, the ability to trigger and watch pipeline runs, and access build output for jobs. The new CLI is also optimized for agents like Claude Code and Codex to use.

Visit https://cli.circleci.com for installation instructions and full release notes.

To reduce load on Maven Central and help avoid rate limit errors when pulling dependencies, CircleCI has introduced a registry cache and proxy. You can opt in to this by running the following command in your job before any dependency installation steps:

circleci experiment registry config --maven

This writes a Maven settings file to ~/.m2/settings.xml that mirrors Maven Central through the CircleCI proxy. It also exports CIRCLECI_MAVEN_REGISTRY_ENDPOINT and CIRCLECI_REGISTRY_TOKEN to $BASH_ENV for use in subsequent steps.

Additional flags are available:

• --gradle configures Gradle to use the proxy
• --lein configures Leiningen to use the proxy
• --all configures all three (Maven, Gradle, and Leiningen)
• --env exports registry credentials as environment variables only, without writing config files

This is an experimental command and the interface may change. We plan to add support for additional package registries and to make this configuration automatic in future updates.

We will be removing the upstream_concurrency_map and upstream_job_ids fields from the v1 API. This change will take effect starting April 13th.

If you have integrations that consume v1 API responses, please ensure they do not depend on the upstream_concurrency_map or upstream_job_ids fields. No other fields in the v1 API are affected. The v2 API is unaffected by this change.

If you have any questions or concerns, please reach out to CircleCI Support.

New and improved docs site

We’re excited to launch our revamped documentation site at https://circleci.com/docs with better navigation, organization, and layout.

What’s new:

• Improved navigation structure
• Version switching for CircleCI Server docs
• Cleaner visual layout

Behind the scenes: We’ve migrated from our custom-built platform to Antora, which brings a number of benefits

• Improved organization of our source files
• Enhanced collaboration opportunities. Once our repo is public (coming soon) anyone can contribute including building the site in their local environment
• A more stable site with lower upkeep requirements
• Significantly faster publishing pipeline

Share your feedback: Try out the new site and let us know what you think on our community forum.

Known issues

• The docs repo (from which this new site is built) is not yet public. This means that all links from our docs to the repo are currently broken. This will be fixed in the coming days.
• Our 404 page is currently broken.

CircleCI’s Visual Studio Code extension now lets customers trigger pipelines from VS Code based on local, unversioned configuration files. Users can choose to run a full pipeline, or select only the individual jobs and workflows they want to run by using checkboxes. This will shorten the feedback cycle and enable developers to iterate fast on their configuration, without having to commit their trial and error changes to the VCS.

This feature is controlled by an org-level opt-in setting, and an opt-out project level setting.

Check out the feature docs for more information.

What’s New

CircleCI Personal and Project API access tokens have a new format. Previously, token values included a 40-character hex string. Newly created tokens will now include a CCIPAT or CCIPRJ prefix for personal access tokens or project access tokens, respectively:

CCIPAT_<base58-UUID>_<40-char-hex string>

For example: CCIPAT_ULUhR6rJLxYbyzyrP19iMZ_8fb1e3510325f7f09361de22b9420346c53ca2cb

Existing tokens are not impacted.

What’s New

CircleCI’s CLI now includes an env subst command, which serves as a wrapper around the popular envsubst CLI tool. The command is used to substitute environment variables in a text string or file.

circleci env subst is available in both the local CLI and inside all CircleCI jobs (coming to CircleCI server v4.2+). More information and usage examples can be found in the docs as well as in this Discuss post.

What’s New

Visual Studio Code users can now re-run CircleCI jobs with SSH, through either the integrated terminal, or a dedicated remote development window. You can automatically open an SSH connection within the terminal, or use a remote window to work on a CircleCI remote machine as if it was a VS Code workspace, which allows you to browse and view files easily, as well as take advantage of supported extensions.

For more details, see the Discuss post (including a quick demo), or the docs on VS Code Marketplace.

What’s New

The CircleCI VS Code extension is now generally available. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

By making existing CircleCI features available in VS Code and facilitating configuration file editing, the extension reduces context switching for CircleCI users (i.e. between the code editor and the browser).

Head to the VS Code Marketplace to view the full list of capabilities and download the extension for free.

What’s New

We have published the official CircleCI Visual Studio Code extension. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

By making existing CircleCI features available in VS Code and facilitating configuration file editing, the extension reduces context switching for CircleCI users (i.e. between the code editor and the browser).

Head to the VS Code Marketplace to view the full list of capabilities and download the extension for free. The CircleCI VS Code extension is currently in open preview.

What’s New

The orb source, orb info, and orb/config validate CLI commands have been updated to work successfully with private orbs.

While the orb source and orb info commands operate the same as they do for public orbs, the orb/config validate command is different.

For more information on how to use the updated orb/config validate tool, please refer to the Private Orbs technical documentation.

What’s New

CircleCI has just release 7 new Insights API endpoints to improve pipeline observability and tracking. You can now access even more insights features such as:

• flaky tests
• workflow time series
• organization performance data
• project performance data.

For more information about these new endpoints, refer to the CircleCI API v2 Insights documentation.

What’s New

• Auto-cancel of redundant builds now supports workflows. Customers will need to turn on the Build Processing option under Advanced Settings in their project settings. See the istructions for Enabling Auto-Cancel for Workflows Triggered by pushed to GItHub or the API for details.

• A new version of the Local CLI is available. Customers using the existing Local CLI can update using the circleci-update command followed by the circleci switch command. Refer to Using the CircleCI Local CLI for the update instructions.

• Performance customers can now see the billing period dates on the Plan Overview page.

• A new Plan Overview page that shows the details for plan selection and a new Plan Usage page that shows usages for any applicable Linux and macOS plan.