Sanaf AI
Start free
Developer Tools

CircleCI, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your CircleCI account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 9 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What CircleCI is

CircleCI is a continuous integration and delivery platform that automates build, test, and deployment pipelines for software development.

You paste in a key from your own CircleCI account. It is kept encrypted, and you can withdraw it from inside CircleCI whenever you like.

How a run works

One message in, the work done in CircleCI.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in CircleCI. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own CircleCI account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

9 tools it already has

What it can do in CircleCI

These are the ready-made tools your AI employee already has in CircleCI. It is not limited to them, but it never has to be taught these.

  • Get Job ArtifactsTool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.
  • Get Job DetailsTool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.
  • Get Pipeline ConfigTool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
  • Get Test MetadataTool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.
  • Get User InformationTool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.
  • List Pipelines for ProjectTool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).
  • List Self-Hosted RunnersTool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.
  • List Workflows by Pipeline IDTool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.
  • Trigger PipelineTool to trigger a new pipeline for the specified project. use when you need to start a build on a branch or tag programmatically.
Access, and who is in charge of it

You stay the boss of your CircleCI account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own CircleCI account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in CircleCI is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in CircleCI and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about CircleCI

Can an AI employee really work inside CircleCI?
Yes. It signs in to your own CircleCI account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of CircleCI?
No. Nothing moves and nothing is replaced. Your records stay in CircleCI, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my CircleCI account?
You paste in a key from your own CircleCI account. It is kept encrypted, and you can withdraw it from inside CircleCI whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in CircleCI?
It has 9 ready-made tools in CircleCI today, among them Get Job Artifacts, Get Job Details and Get Pipeline Config. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use CircleCI and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in CircleCI and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in CircleCI?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in CircleCI is written down with what it did and when.