Skip to main content
Connecting CircleCI to AgentRail lets your agents get compact CI status summaries instead of parsing raw pipeline logs. AgentRail verifies your project access, creates a starter .circleci/config.yml if one is missing and it is safe to do so, and configures how it will fetch pipeline results for agent branches. Run agentrail provider connect circleci to get started.

​
Connect CircleCI

The interactive setup prompts for your CircleCI API token in a hidden prompt, then asks for the full CircleCI project slug in this format:
After you provide the slug, AgentRail:
  1. Verifies your token has access to the project.
  2. Checks the repo for a .circleci/config.yml file.
  3. Creates a starter Node workflow config if the file is missing and a safe inference is possible.
  4. Configures the CircleCI pipeline-run API as a fallback if automatic branch builds are not available and your token can access a pipeline definition.
  5. Runs provider readiness checks and reports any blockers it cannot fix locally.
For non-interactive environments, set environment variables before running the connect command.

​
Webhook verification

AgentRail verifies inbound CircleCI webhook requests using the CIRCLECI_WEBHOOK_SECRET environment variable. To receive push-based pipeline status updates instead of polling, configure your CircleCI webhook to deliver to your AgentRail server’s /providers/circleci/webhooks path and set CIRCLECI_WEBHOOK_SECRET in your server environment before starting AgentRail.

​
What it sets up

​
Health check

provider doctor runs full provider readiness — it is not just a token check. A passing result means CircleCI is ready for AgentRail’s lifecycle operations. You can also check all providers at once:

​
Troubleshooting