CircleCI, without opening CircleCI.
What broke the build, and which test has been lying to you.
“@Ray why did the deploy pipeline fail on main?”
What Ray can and cannot do in CircleCI
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in CircleCI
- Pipelines, workflows and jobs, with status, timing and artifacts
- Flaky tests and test metadata for any job
- Workflow and project insights: duration, success rate and trends
- Credit usage by project, plus schedules, runners and orbs
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Triggering a pipeline, with the branch and parameters on the card
- Creating a project in your organisation
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Read or write environment variables, in a project or a context
- Create contexts or change who can reach one
- Manage organisation groups, or delete a project, namespace or context
How Ray works with CircleCI
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect CircleCI
CircleCI has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in CircleCI, and tell Dana it is being looked at.
Create a CircleCI project
- Waiting on
- your approval
What does connecting CircleCI to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect CircleCI and it can do the CircleCI part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
CircleCI has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see CircleCI. Every write still stops for approval first.
Security and permissions
- You paste the CircleCI key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect CircleCI in a message. Uninstall Ray and every connection it held is revoked.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in CircleCI.
Free to start, no credit card, and it asks before it acts.