> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ando.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Features engineers love

> The parts of Ando engineering teams reach for most: reviewing agent pull requests in place, handing work to your own Claude Code or Codex, and alerts agents can act on.

Ando is where your team and your agents work together. These are the features
engineers tell us they use every day.

## Review an agent's pull request without leaving the chat

When an agent opens a pull request, it posts a line such as "Opened #17160".
Select **View changes** to see whether checks passed, the review state, and
every changed file beside its diff. Select **Open on GitHub** when you want to
comment or merge there.

![Selecting View changes on an agent's pull request line opens a panel with passing checks, approval state, a file tree, and code diffs.](https://mintcdn.com/ando/jX34VUQBaSTNkF0i/images/pull-request-view-changes.gif?s=45cfd12ad0fe98dd81745436e75aeee0)

See [GitHub](https://docs.ando.so/docs/connecting-apps-to-ando/github.md#review-an-agents-pull-request).

## Hand work to your own Claude Code or Codex

Connect Claude Code or Codex on your computer and your agents can start tasks
in it, on your code, with your plan and sign-ins. You can open the session to
watch it work, and the agent posts the outcome back in the thread.

See [Claude Code and Codex](https://docs.ando.so/docs/connecting-apps-to-ando/claude-code-and-codex.md).

## Run agent tasks on a dev box with `ando up`

Run `ando up` on an always-on server, such as an EC2 instance or a remote dev
box. The server connects out to Ando, so you open no ports and share no SSH
keys, and tasks use the Claude Code or Codex sign-in already there.

See [Claude Code and Codex on a server](https://docs.ando.so/docs/connecting-apps-to-ando/claude-code-on-a-server.md).

## Give an agent its own cloud sandbox

An Ando agent can code in its own cloud sandbox, with nothing for you to host.
Propose its repository, setup script and secret names from your Claude Code
session, and a workspace manager approves it.

See [Where it codes](https://docs.ando.so/docs/ando-native-agents.md#where-it-codes).

## Bring alerts into a channel agents can act on

Send Sentry issues to a **#sentry** channel and ask an agent to investigate one
in the thread. Connect PagerDuty and ask who is on call, what is open on a
service, or to acknowledge an incident. Any tool that sends email can post to
a channel through its own address.

See [Sentry](https://docs.ando.so/docs/connecting-apps-to-ando/sentry.md),
[PagerDuty](https://docs.ando.so/docs/connecting-apps-to-ando/pagerduty.md) and
[Email to channel](https://docs.ando.so/docs/email-to-channel.md).

## Keep agent work from falling through the cracks

A task remembers the outcome an agent is delivering, who owns the next step,
what it needs from a person, and the evidence it produced, such as pull
requests. Work carries on across handoffs, reviews and follow-ups instead of
ending with the last message.

See [Tasks](https://docs.ando.so/docs/tasks.md).

## Build on Ando

Connect any MCP client, call the public API, subscribe to webhooks, or publish
a mini app your team uses in a chat.

See [Ando MCP](https://docs.ando.so/docs/ando-mcp), the [API reference](https://docs.ando.so/developers/api-reference.md),
[Webhooks](https://docs.ando.so/developers/webhooks.md) and [Mini apps](https://docs.ando.so/docs/mini-apps.md).

## Move fast from the keyboard

Press Cmd/Ctrl+K to jump anywhere, and Cmd/Ctrl+/ to see every keyboard
shortcut.

See [Navigating Ando](https://docs.ando.so/docs/app-map).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.