Operations | Monitoring | ITSM | DevOps | Cloud

CircleCI can now run supported GitHub Actions workflows directly on CircleCI infrastructure, using the YAML you already have. In this quick demo, we’ll walk through setting up a CircleCI project with an existing GitHub Actions workflow and running your first build. You’ll see how to: GitHub Actions compatibility is currently available in open preview on Linux. Not all GitHub Actions features are supported yet, so check the documentation for current compatibility.

CircleCI Chief Legal & People Officer on why learning fast, experimenting, and staying curious matter more than ever.

Connect Codex to CircleCI and give your coding agent direct access to the CI feedback it needs to keep working. In this tutorial, we’ll walk through setting up the CircleCI CLI and CircleCI plugin for Codex, then show how Codex can check pipeline results, validate your CircleCI config, diagnose failed builds, trigger new pipelines, and keep iterating on a fix until CI is green. Instead of bouncing between your terminal and CircleCI to copy logs and errors back to your agent, you can bring the full CI feedback loop directly into your Codex session.

CircleCI now works with Cursor Origin. Connect your repo, push a commit, and run your existing CircleCI pipeline. Now in beta.

Give Claude Code direct access to CircleCI and let it diagnose failed builds, fix issues, and keep iterating until your pipeline is green. In this tutorial, we walk through how to connect Claude Code to CircleCI using the CircleCI CLI. You’ll see how Claude can read pipeline results, identify test failures, make fixes, trigger new builds, and monitor CircleCI without leaving the terminal.

CircleCI now integrates with Cursor Origin, bringing scalable CI/CD to Origin-hosted repositories. In this demo, see how to connect an Origin repository to CircleCI, configure your pipeline triggers, run a build, and report CI status back to your Origin pull request. Already using CircleCI? Your existing.circleci/config.yml works as-is, with no Origin-specific CI syntax or separate config to maintain.

They’re gonna need some context.