Skip to main content

Describe the change.
Review the pull request.

Operator is Kaer for software teams. Connect a GitHub repository, describe what should change, and it reads the code, makes the change on its own machine, runs the tests and opens a pull request for you to review.

What you review

A normal pull request on GitHub, with a note on why each change was made.

  • Your repository, your review. It works on a branch and opens the pull request there.
  • Why, next to what. Each change comes with a short explanation.
  • Ask for changes in the chat. It updates the same pull request.

Where it stops

Reading, editing and testing on its own machine are its job. Merging, deploying and anything that costs money are yours.

It stops for you

The merge
A person merges. Never the agent.
Deploys
By default, putting a change live waits for you.
Payments
Anything that spends money asks first.
Access
Only the repositories and tools you connect.

It gets on with it

Reading
Files, history and tests.
Its own machine
The work runs there, not on your laptop.
Tests
As often as it needs, on its branch.
Fixing its mistakes
A failing test sends it back to the code.

Give it the change you keep postponing

Connect GitHub and describe one change.

Common questions

What does Operator do?
Operator is Kaer for software teams. Connect a GitHub repository and describe what should change. It reads the code, makes the change on its own machine, runs the tests and opens a pull request for you to review.
Does Operator merge or deploy code on its own?
No. Reading, editing and testing on its own machine are its job. Merging, deploying and anything that costs money are yours.
Where does Operator make its changes?
It works on a branch in your repository and opens the pull request there. Each change comes with a short note on why it was made.
How do I ask Operator to change a pull request?
Ask for changes in the chat and it updates the same pull request.