Feature Requests

Direct Image Display in CircleCI UI Add native image visualization and comparison capabilities to the CircleCI UI for Visual Regression Testing (VRT) workflows. This would eliminate manual workflow steps - no more uploading to external storage or manual PR comments. The ideal approach is a built-in comparison view showing expected vs. actual images, with highlighting of pixel differences, and basic zoom/pan controls for detailed inspection.

The project, pipelines and overview pages load slow for Bitbucket orgs with many repositories. Even with an active archival strategy and limiting read permissions for users, loading can take an unbearably long time or even time out. It would be great to improve this experience for Bitbucket orgs on the platform.

Summary: Today, publishing any orb version (including dev/alpha) requires a personal API token from an org owner; using a project API token results in AUTHORIZATION_FAILURE, even for dev orbs.[Ticket 167650] This forces teams to expose an owner’s personal token (or a bot owner token) via contexts so non‑owners can publish, which is a security and operational concern.[Non‑owner orb publish] Requested change: Support using project API tokens to publish development (dev/alpha) orb versions, while keeping production SemVer publishing restricted to org owners. Why this matters: Let's non‑owner developers independently publish dev/alpha orbs for testing. Keeps production orb releases under org‑owner control. Avoids sharing owner‑level personal tokens in contexts accessible to non‑owners. Reduces overhead of managing bot owner accounts just for orb publishing.[Ticket 167650] This would provide a clearer security boundary between development and production orb workflows.

It would be incredibly helpful if we could set and manage RBAC like controls for CircleCI user/groups within the platform, similar to how there is enhanced controls and visibility for Argo Rollouts. Keeping management related to CircleCI within CircleCI (or at least visibility to configuration) will improve security and platform management

Instead of having to tweak the configuration file to rightsize the resource class for a job, it would be helpful if CircleCI could automatically determine the proper size to use.

Re-creating branches in GitHub and then deleting them again is a terrible workaround and a big waste of valuable people's time. If you can't automate it, at least give us something to click in the CircleCI UI where we can delete branches, even if one by one. Just a simple page with the branch list and delete beside each one would seem to me to be super-easy. The ability to select a number of them and bulk delete would be even better. It just seems like such a simple thing that I don't understand not being there already. Thanks, Neil

Would be nice if the auto-cancel feature would be able to distinguish as different workflows in the same branch but with different incoming variables when using the API CCI-I-1419

I need better metrics to auto-scale machine runners effectively. Currently, our auto-scaling is time-based, and we need it to be on-demand based on queue times and other metrics.

I would like AI functionalities that can automatically detect flaky tests and track job performance over time. This would include identifying tests that fail intermittently and alerting users to address them.

I need CircleCI to have the capability to create or update Jira tickets directly from the pipeline, as this is crucial for our workflow automation.