Ano
Example · Ano × Sentry

Run from Ano.

Error tracking and on-call routing. New events land in the right channel with the first stack frame and on-call engineer pulled.

Bring your team Visit Sentry
ano · acme workspace
# incidents synced · 12 ms
Priya Shah 02:14

Just got paged. Anyone seeing a spike on the checkout service?

Dev Raman 02:15

@sentry pull the latest 5 errors on checkout-api, last 30 minutes

Sentry
sentry COWORKER 02:15 via shell

5 fresh errors. TypeError in line-items.ts:78 (×142, owner @dev). Timeout on /stripe/webhook (×18, unowned). Plus 3 quieter regressions. Top stack frame and owner inline.

Mira is typing…
Message #incidents @ / ⏎
shell sentry cli
cwd: ~/acme · checkout-api
from #incidents · dev
latest 5 errors on checkout-api, last 30 minutes
> fetch fresh events for project checkout-api, last 30m, sort by count desc, include first stack frame and code owner
● sentry.issues_list(project: 'checkout-api', range: '30m')
→ 5 issues
● sentry.issue_enrich(include: ['first_frame', 'code_owner', 'event_count'])
→ ready to post
> type to drive sentry…

Your Sentry CLI / MCP, in the channel.

Ano's shell drives the `sentry-cli` and the official Sentry MCP. Pull events, assign issues, and resolve alerts straight from chat.

Errors land as messages.

Every event list or claim posts back as a real message with a 'via shell' badge. The first stack frame is right there, no tab-hop.

Hand the loop to a coworker.

A Claude Code coworker scoped to Sentry can route fresh events to the right channel, ping the on-call engineer, or auto-resolve known-good regressions.

live preview · free

Try from chat.

Download Ano and bring your Sentry setup into a channel. Free, open beta.

Free macOS + iOS