Operations | Monitoring | ITSM | DevOps | Cloud

Stop manually pushing branches, hunting for logs, and pasting errors back into your editor. This video shows you how to connect Cursor to CircleCI using the CircleCI CLI so your AI agent can trigger pipelines, read build output, and fix failures autonomously without you ever leaving the IDE. In this demo, we introduce a bug, let CI catch it, and watch the agent diagnose and fix it on its own, monitoring the pipeline until it comes back green. No tab-switching. No copy-pasting logs.

CircleCI’s CRO on why this moment calls for learning faster, getting better, and embracing a little discomfort.

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.

JFrog is bringing software supply chain governance to AWS Kiro. Operating as a power plugin within Kiro, JFrog delivers package safety, agentic access to the JFrog platform, and the JFrog AI Catalog. With simple setup, AI agents make supply chain aware decisions right inside the IDE, ensuring dependencies come directly from Artifactory rather than unverified public registries.

JFrog is bringing software supply chain governance to Devin. The plugin bundles JFrog Platform Skills and registers the JFrog remote MCP server, so Devin resolves dependencies, MCP servers, and skills only from governed sources, authenticated once, with provenance preserved for every session.

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

Thanks to AI, vulnerability disclosures are exploding. In mid 2026, we're seeing 130+ a day and climbing, with roughly a quarter already being exploited in the wild before they're even disclosed. The result: security teams that used to have 30 days to respond now feel pressure to issue patches in a few days or hours. This video covers why "are we safe?" isn't a question you get to answer once: That last drill is what separates teams that panic when a real incident hits from teams that already know the answer.

Think of an SBOM as your ingredient list. A common language describing everything that goes into a piece of software, every dependency and version, in one place. This video covers why SBOMs have gone from niche to mandatory, and why they're harder to pull off than the concept suggests: The concept is simple. Operationalizing it across a large, diverse tech stack is where it gets hard.

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.

CRA compliance is similar to other frameworks, like ISO 27001, SOC 2, GDPR, or PCI DSS, in that the same approach applies: define your scope, figure out your product classification, then work through the list of controls. This video covers why that's less daunting than it sounds: CRA compliance isn't a one-time milestone. If you're selling into Europe, you need to continuously meet it.

Hardened base images are a great secure foundation. They're minimal, security-vetted, and have few dependencies to worry about. But almost nobody ships a bare base image. Teams build on top of it. This video cover whys that "on top of it" layer is where the risk actually lives: Skip the base image hardening and you're building on a shaky foundation. Skip artifact management and you're leaving everything built on top of that foundation ungoverned. A strong posture uses both.

An SBOM is more than a compliance checkbox. It's literally a bill of materials for your product: every software component that makes it into what you ship, plus the metadata that tells you whether it's safe to use. This video covers what that metadata actually does for you: An SBOM earns its keep when it shows you what's actually there, version to version, on a continual basis.

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

A documented policy only works if every engineer remembers it, every time, under deadline pressure. That's the gap policy-as-code closes. This video covers what that actually looks like in practice: The instructions don't change. What changes is whether something actually enforces them, or just hopes someone reads them.

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.

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.