One agent.
Many skills.
No new tool to learn.

Bott reviews your pull requests, implements the fixes you approve, triages production errors and reports on delivery. It reads real context from the systems your team already uses, and it answers in Slack like a colleague would.

Book a walkthrough Watch it work

# eng-paymentsBott is online

Priya@Bott review #482 and fix what you find

BottAPP

Two findings, both fixable. Plan drafted, waiting on you.

ApproveDismiss

Reviews pull requestsImplements approved fixesTriages production errorsReports on deliveryLearns new skills

What Bott is

A single agent with specialised skills, built and operated by Axelerant.

You talk to it in a direct message or by mentioning it in a channel, and it answers from real context rather than from a generic model prompt.

It is one agent with many skills, not a collection of separate bots. Slack is the interface; everything Bott can do is reachable in plain language.

b.Bott orchestrates the tools you already run

Reviews and commits

Reads the ticket

Reads the spec

Reads the error

Where you talk to it

Bott orchestrates the tools you already run. It reads freely across them; any write waits for a person.

What Bott does

Seven skills, one conversation.

New skills are added by describing them, not by shipping another bot.

Pull request review

Reviews a pull request when it opens, posts findings on the PR, and re-reviews automatically when new commits land.

Build and fix

Describe a change, or point at an issue or a ticket. Bott drafts a plan, waits for approval, then implements it and opens a draft pull request.

Error triage

Reads a production error and its recent events, diagnoses the root cause, and proposes a fix into the same approval-gated pipeline.

Issue triage

Investigates a newly opened issue and comments the diagnosis back on the issue itself. Opt-in, off by default.

Delivery and reporting

Daily standups, sprint reports, delivery synthesis, portfolio risk roll-ups and security advisory digests, on a schedule.

Personal assistance

Reads your own mail, files and calendar, read-only, bound to your verified identity. Only ever your own data.

Skills it teaches itself

Describe a reusable workflow in plain language and Bott saves it as a new skill, available immediately and permanently.

Pull request review

Reviews a pull request when it opens, posts findings on the PR, and re-reviews automatically when new commits land.

Build and fix

Describe a change, or point at an issue or a ticket. Bott drafts a plan, waits for approval, then implements it and opens a draft pull request.

Error triage

Reads a production error and its recent events, diagnoses the root cause, and proposes a fix into the same approval-gated pipeline.

Issue triage

Investigates a newly opened issue and comments the diagnosis back on the issue itself. Opt-in, off by default.

Delivery and reporting

Daily standups, sprint reports, delivery synthesis, portfolio risk roll-ups and security advisory digests, on a schedule.

Personal assistance

Reads your own mail, files and calendar, read-only, bound to your verified identity. Only ever your own data.

Skills it teaches itself

Describe a reusable workflow in plain language and Bott saves it as a new skill, available immediately and permanently.

Hover a card to read it

How a review works

No command. A webhook, then a verdict.

Reviews can also be requested on demand, by mentioning Bott on the pull request.

A pull request opens

A webhook from the repository triggers a review. No command is needed.

Bott investigates the change in context

A background worker clones the repository and examines the change against the surrounding code, not just the diff in isolation.

Findings are categorised

Every finding is classified before anything is written up.

SecurityCorrectnessTestsConventionsOperational

A verdict gate runs

The review resolves to one of three verdicts before anything is posted.

ApproveSuggestionsIssues

The review is posted to the pull request

And mirrored into Slack, so the discussion happens wherever the team already is.

New commits trigger a fresh review

Pushing to the branch re-reviews it automatically.

Click a card to advance · hover to hold

1
A pull request opens
A webhook from the repository triggers a review. No command is needed.
2
Bott investigates the change in context
A background worker clones the repository and examines the change against the surrounding code, not just the diff in isolation.
3
Findings are categorised
Every finding is classified before anything is written up.
SecurityCorrectnessTestsConventionsOperational
4
A verdict gate runs
The review resolves to one of three verdicts before anything is posted.
ApproveSuggestionsIssues
5
The review is posted to the pull request
And mirrored into Slack, so the discussion happens wherever the team already is.
6
New commits trigger a fresh review
Pushing to the branch re-reviews it automatically.

From review to fix

Bott never acts on its own initiative.

Where a review's findings are concrete edits, Bott can implement them. Every write, to a repository or to any connected system, waits behind an Approve or Dismiss decision made by a person.

Review posted“fix the issues”Plan drafted

A human decidesApproveDismiss

Code committed to the PR brancha fresh review runs

Fixes commit to the pull request’s own branch, and the resulting push triggers a normal re-review. No new pull request, no separate command.
New work opens a draft pull request when the change is described from scratch, or comes from an issue or a ticket.
Bott never merges anything. Every change lands through your normal review and merge process.
It refuses up front, with a reason, if it lacks write access to the repository or the branch lives in a fork.

#eng-paymentsLive · try approving

GitHubAPP10:02

feat(payments): retry webhook delivery · #482 opened by priya

BottAPP10:03

Reviewed #482 against the surrounding code. Two things worth fixing before merge.

2 correctness1 test gapno security findings

webhooks/retry.py:64

The retry loop has no ceiling. A permanently failing endpoint requeues forever.

webhooks/retry.py:81

Backoff reads local time, so clock skew can produce a negative delay.

Priya Sharma10:05

@Bott fix both of those on the branch

BottAPP10:05

Plan: cap retries at five attempts with jittered exponential backoff, and switch to a monotonic clock. Two files, no schema change.

Approval required · writes to your repository

You decide

How Bott connects to your code

Two halves. They install separately.

The Slack side

You just talk to it.

Nothing to install on your side. Ask in plain language, in the channel you already use.

# eng-checkoutBott is online

Dev Kapoor@Bott what changed in checkout this sprint?

BottAPP

Nine pull requests merged. Two touched tax rules.

9 merged2 tax rulestickets linked

Ask Bott anything…

The GitHub side

One GitHub App, on the repos you pick.

An owner installs it. That installation is the whole boundary: no second credential, no back door.

metadata: readEverything

pull_requests: writeReviewing

contents: readReviewing

contents: writeFixes only · withholdable

Security and control

Fails closed, by design.

Uninstalling the GitHub App revokes Bott's access immediately and completely. Everything below holds until that moment, and after it there is nothing left to hold.

Human approval

Writing code, opening a pull request, or any write to a connected system posts an Approve or Dismiss decision first.

One boundary

The GitHub App installation is the authorization boundary. Bott reaches exactly the repositories your organisation granted, and nothing else.

Advisory output

Review output is a faster first pass, not a replacement for human review. Bott never merges.

Opt-in automation

Automatic triage is off by default and enabled deliberately, per engagement.

Isolation

Every interaction is scoped to a verified user and conversation, so no team’s context reaches another’s.

Credentials

Encrypted at rest, with secret-redacting logs throughout. Personal data requests are bound to the verified Slack identity of the person asking.

Four things Bott will never do

Merge a pull requestWrite anything without an approvalCarry one team’s context into another’sGuess when configuration is missing

How Bott is built

One application. No bots to keep in step.

Agent

One agent, many skills

A single Agno agent running as one AgentOS application. No routing between bots.

Models

Pluggable model gateway

OpenAI Codex, AWS Bedrock and OpenRouter, chosen per task. Swap the model, not the product.

Execution

Durable job queue

Reviews, fixes and triage run as background jobs that survive restarts.

State

One PostgreSQL datastore

Jobs, approvals, credentials, authored skills, sessions and review traces, in one place.

Edges

Modular connectors

Each system is independent, declares its own auth, and can be left switched off.

Five layers, one deployment, one PostgreSQL database on Axelerant-operated infrastructure. Nothing in the stack knows about a second bot, because there isn't one.

Private beta

See Bott review a real pull request of yours.

Forty-five minutes with the engineers who built it. Bring a repository, and leave knowing exactly what Bott would and would not touch.

Book a walkthrough