Changelog

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.

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

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.