4 integrations

Ask on iMessage what shipped, what broke and who is reviewing

Connect GitHub, BitBucket or Azure DevOps so you can check a deploy, find a recent change or chase a review by text — useful precisely when you are on call and nowhere near a laptop.

No code · Works on your own number · Live in minutes

This is a small category with a specific job. Nobody wants to write code by text, and this is not trying to make them. The value is the moment you are away from a desk and need to know whether the deploy went out, what changed in the last hour, or who has a review sitting on them.

The agent reads the same repos your team works in and answers plainly. Paired with an on-call rota, the first minute of an incident goes on the problem rather than on finding somewhere to open a laptop.

Because each engineer can connect their own account, the agent sees exactly the repos they do — which matters on private organisations and self-hosted Enterprise Server instances.

🤖 Eng Agent · iMessage
did the payments fix ship?
•••
Yes — PR #2184 merged 40 minutes ago and the production deploy finished at 18:12. Green.
what else went out today?
Three others: a rate-limit bump, a copy change on billing, and a dependency upgrade. Want the diffs?
↳ GitHub · scoped to the repos Maya can see

Who this is for

Engineers on call

Find out what shipped and what changed before you have found somewhere to sit down with a laptop.

Engineering managers

Ask what is waiting on review or what merged this week without opening five tabs to work it out.

Small teams without a bot fleet

One agent that answers repo questions, instead of wiring up a separate integration for each thing you want to ask.

Two ways to connect Dev Tools

Connected for the bot

Your account, every conversation

Connect a team-level account and the agent answers about the repos your organisation owns, for whoever is texting the number.

Enabled for customers

Their account, their data

Each engineer connects their own account, so the agent sees exactly the repos they do — which matters on private and self-hosted instances.

What people use this for

The same agent, asked different things by different people on the team.

Engineer

Check a deploy from your phone

Ask whether the release went out and get it from the repo, rather than from a notification you half-remember seeing.

On call

Triage before you open a laptop

Find recent changes to a service and who touched them in the first minute of an incident.

Engineer

Chase a stuck review

Ask what is waiting on you, or on someone else, and get a straight list back.

Eng manager

See what actually merged

Ask what went out this week across the repos you care about, without assembling it from tabs.

Engineer

File an issue from anywhere

Describe the bug while you remember it and have it land as a properly formed issue in the right repo.

Team lead

Answer "is it us?" quickly

Check whether anything shipped near the time a problem started, before pulling people into a call.

4 Dev Tools integrations

Dev Tools integration FAQs

Does this work with self-hosted GitHub?

Yes — GitHub Enterprise Server is supported alongside github.com, as are BitBucket and Azure DevOps.

Can the agent merge or push code?

Its abilities are bounded by the connected account’s permissions. Connect read-only access if you want it to answer questions and nothing more.

Is this meant to replace our alerting?

No. It is for asking questions and getting answers in a thread. Keep your existing paging and alerting for detection.

Do engineers see only their own repos?

When each connects their own account, yes — the agent inherits exactly their access, which matters on private organisations.

Other categories

Put it on a number your customers already text

Pick a model, write a prompt, connect the tools it needs, and go live in the blue bubble — no code required.