CircleCI NewsSep 1, 20264 min read

CircleCI is now available on Cursor Origin

Nathan Fish

Director of Product Management

CircleCI now integrates with Cursor Origin as a beta release, bringing scalable, agent-ready CI/CD to Origin-hosted repositories.

Origin is built for teams pushing beyond the limits of traditional Git infrastructure. CircleCI extends the same approach to software delivery, with CI/CD designed for fast feedback, high concurrency, and the higher validation volume of agentic development.

Teams with repositories on Origin can connect them to CircleCI in a few clicks and get pipelines running on every push and pull request, with results reported back to the Origin PR.

CircleCI on Cursor Origin demo

Agent-friendly CI/CD for the agent-friendly VCS

AI coding agents increase activity across the delivery lifecycle. More code means more commits, more builds, and more validation work.

Origin is designed to handle higher Git workloads as repository activity grows. Its Continuity storage system handles horizontal scaling elegantly as demand increases.

CircleCI is built to handle the corresponding increase in CI demand. High concurrency and flexible compute let teams run more builds and tests in parallel as development volume rises, stopping validation from being the bottleneck.

Bring validation into the agent loop

As agents generate and revise code continuously, fast, useful validation becomes critical to maintaining development speed.

CircleCI supports validation throughout the agent SDLC:

  • Validate before the push: Chunk sidecars are cloud-hosted ephemeral microVMs where coding agents run microbuilds to check changes against relevant tests as they loop. Agents get feedback in seconds and fix what’s broken before CI ever sees it.

  • Run only impacted tests: Smarter Testing reduces unnecessary test work through test impact analysis and smarter splitting. Teams can use it in CI or inside a sidecar for targeted validation earlier in the loop.

  • Scale without limit: Parallel execution, flexible compute, and high concurrency (unlimited Linux concurrency for Scale customers) support integration, security, and release checks as validation volume grows.

  • Return CI feedback to the agent: The CircleCI CLI and MCP let agents like Cursor inspect runs, retrieve test results and failure logs, and take CI actions directly from the agent workflow.

Agents validate and fix before pushing, and CI pipelines run against changes that have already cleared a bar. Agents consume fewer tokens, developers have better control and visibility, cleaner code arrives in the pipeline, and more changes make it into production.

Keep your existing CircleCI config

Origin works with standard CircleCI pipelines. There’s no Origin-specific CI syntax, translation layer, or separate config to maintain.

If you already use CircleCI, your existing .circleci/config.yml works with Origin repositories, including the jobs, workflows, executors, test config, and other capabilities you already have in place. Or you can set up a new pipeline in minutes and use the same powerful features available across our other VCS integrations.

Connect an Origin repo to CircleCI

  1. Open the Apps tab in Cursor Origin.
  2. Select CircleCI and authorize access to your Origin organization.
  3. Select or create the corresponding organization in CircleCI.
  4. Go through Project Setup and choose the Origin repository you want to connect.
  5. Push a commit. CircleCI will detect your .circleci/config.yml and run the pipeline.

Push and pull request events trigger CircleCI pipelines, with status reported back to the Origin PR. You can also connect from within the CircleCI app or by using the CircleCI CLI.

See the full setup and workflow in action in the demo below.

Scale agentic development with CircleCI and Origin

Agentic development only works if validation can scale with code generation. Origin gives teams repository infrastructure built for higher development volume. CircleCI provides the builds, tests, and delivery workflows needed to validate every change at the same pace.

CircleCI support for Origin is currently in beta. Push and pull request triggers, API-triggered pipelines and scheduled pipelines are all available today.

Existing CircleCI users can connect an Origin repository and keep their current configs and workflows. New to CircleCI? Create a free account and connect your Origin organization to get started.

Frequently asked questions

Do I need to change my existing CircleCI config to use Origin?

No. Existing .circleci/config.yml files work with Origin repositories without a separate Origin-specific syntax or translation layer.

Which CircleCI features work with Origin during the beta?

CircleCI on Origin works the same way it does on any other VCS: your existing config, with pipelines triggered from pushes and pull requests. See our doc for the full list of supported features.

Can I use my existing CircleCI organization with Origin?

Yes. Existing CircleCI customers can connect to Origin using their existing CircleCI organization and continue using their current CircleCI setup.

How do pipeline results appear in Origin?

CircleCI reports pipeline status back to the Origin pull request, so teams can see validation results alongside the change.