CircleCI
CircleCI is on the roadmap. Agents will read pipelines, workflows and job logs, explain why a build failed, and flag the jobs that keep going flaky — while re-running or cancelling a pipeline stays a destructive-tier action that waits for your approval.
What your agents can do with CircleCI
- Read pipelines, workflows and job logs
- Explain why a build failed
- Re-run or cancel pipelines (with approval)
- Trigger workflows on build events
How to connect CircleCI to Velaris
- 1
Get early access
Join the waitlist — we open access in waves.
- 2
Request CircleCI
Vote for the CircleCI connector in the community.
- 3
Get notified
We'll ping you the moment CircleCI goes live.
Popular ways to use it
CircleCI + Velaris — common questions
Can an agent re-run a failed CircleCI job automatically?
No — re-running spends build credits, so it is approval-gated. The agent tells you which job it would re-run and why, then waits for your confirmation.
Will Velaris see my CircleCI contexts or environment variables?
No. Agents read pipeline metadata and job output — the values held in contexts and project environment variables are not pulled into agent context.
Can Velaris find which of my tests are flaky?
Yes — an agent can scan recent runs of a workflow, group repeat failures by test, and hand you a ranked list with links to each run.