# Sentry Projects at AI Tinkerers

> Canonical HTML: https://aitinkerers.org/technologies/sentry
> Markdown URL: https://aitinkerers.org/technologies/sentry.md
> Technology record last updated: 2026-09-18T15:13:45Z
> Generated: 2026-09-20T15:43:41Z

Sentry delivers code-level observability: real-time error tracking and performance monitoring for production applications.

Sentry is the developer's platform for diagnosing, fixing, and optimizing code performance. It automatically captures unhandled exceptions and critical performance issues, providing full context: stack traces, suspect commits, and user session details (via Session Replay). The platform supports over 100 coding languages and frameworks, integrating directly with your workflow tools like GitHub, Slack, and Jira. With Sentry, teams can move from alert to resolution in minutes, not hours, ensuring stability for the 150K organizations and 4M developers who rely on it daily.

- Official technology site: https://sentry.io/
- Public AI Tinkerers demos and talks: 3
- Result page: 1 of 1

## Recent Public Talks and Demos

### [Eliminating Waste in the AI Augmented SDLC](https://nashville.aitinkerers.org/talks/rsvp_uMKhslYmRfU)

When AI can use the same tools you use - Jira, GitHub, Sentry - the bottleneck in software development shifts from writing code to everything around the code. I applied lean manufacturing principles (Toyota Production System) to my own AI-augmented workflow and systematically removed entire categories of waste: manual ticket management, error triage, deployment monitoring, and ambiguous specifications that lead to expensive rework. I’ll walk through the specific patterns - MCP tool handoff, Gherkin specs as agent contracts, pre-flight checklists derived from PR review audits - and show how each elimination is permanent and reveals the next layer.

- Event context: AI Tinkerers Nashville – Software Development in the Age of AI — 2026-03-25 — Nashville
- Public talk page: https://nashville.aitinkerers.org/talks/rsvp_uMKhslYmRfU

### [From Error to Agent: Automating Sentry Issue Triaging](https://sf.aitinkerers.org/talks/rsvp_kRf3Je0l3SI)

Engineering teams use Sentry to capture errors and performance issues, but turning that signal into action remains largely manual. Most teams ignore errors until things break. I'll demo an agentic workflow that goes from ignored Sentry errors to triaged PRs using AI agents. We've built a first-class integration that maps Sentry's project-based error model to GitHub repositories, letting developers review issues directly inside Continue. The system allows teams to filter and surface relevant errors, then launch an agent to investigate, summarize, or propose fixes. This Continuous AI workflow originated from a YC company struggling with their massive Sentry backlog. Their ask was simple: "Let me look at my Sentry inbox, decide what matters, and offload the rest to an agent." The result is a tight loop between runtime issues, developer intent, and automated AI-powered actions. Attendees will learn how to design AI-driven triage workflows, how agents can listen to Sentry webhooks to create tasks instantly, and how teams can turn noisy error data into structured, actionable work.

- Event context: AI Tinkerers x Google Cloud SF Meetup — 2025-11-21 — San Francisco
- Public talk page: https://sf.aitinkerers.org/talks/rsvp_kRf3Je0l3SI

### [From Error to Prod in 3 Minutes: My Replit → Sentry → GitHub → CodeRabbit Ship Loop](https://seattle.aitinkerers.org/talks/rsvp_9nHH45wrtts)

I’ll demo a real developer workflow where an error in production is detected in Sentry, triaged, and fixed end-to-end using AI-assisted tooling. The loop: (1) trigger a live bug and open the Sentry issue with stack trace + breadcrumbs; (2) use Replit (with AI assist) to generate the patch and a unit test; (3) push a branch to GitHub; (4) CodeRabbit reviews the PR; (5) CI runs tests, static analysis, and coverage gates; (6) on merge, GitHub Actions creates a Sentry Release and deploys; (7) Sentry auto-resolves the issue and links the fix to the release. One measured improvement I’ll show: lead time from error → fix → deploy.

- Event context: AI Tinkerers Seattle Meetup: Dev Tools Track — November 3, 2025 — 2025-11-04 — Seattle
- Public talk page: https://seattle.aitinkerers.org/talks/rsvp_9nHH45wrtts

## Related Technologies

- [MCP](https://aitinkerers.org/technologies/mcp) ([Markdown](https://aitinkerers.org/technologies/mcp.md)) — 129 public demos
- [Claude](https://aitinkerers.org/technologies/claude) ([Markdown](https://aitinkerers.org/technologies/claude.md)) — 173 public demos
- [Claude Code](https://aitinkerers.org/technologies/claude-code) ([Markdown](https://aitinkerers.org/technologies/claude-code.md)) — 214 public demos
- [Coderrabbit](https://aitinkerers.org/technologies/coderrabbit) ([Markdown](https://aitinkerers.org/technologies/coderrabbit.md)) — 1 public demo
- [Gherkin](https://aitinkerers.org/technologies/gherkin) ([Markdown](https://aitinkerers.org/technologies/gherkin.md)) — 2 public demos
- [Gherkin acceptance criteria](https://aitinkerers.org/technologies/gherkin-acceptance-criteria) ([Markdown](https://aitinkerers.org/technologies/gherkin-acceptance-criteria.md)) — 1 public demo
- [GitHub](https://aitinkerers.org/technologies/github) ([Markdown](https://aitinkerers.org/technologies/github.md)) — 74 public demos
- [GitHub Actions](https://aitinkerers.org/technologies/github-actions) ([Markdown](https://aitinkerers.org/technologies/github-actions.md)) — 20 public demos
- [Heroku](https://aitinkerers.org/technologies/heroku) ([Markdown](https://aitinkerers.org/technologies/heroku.md)) — 2 public demos
- [Jira](https://aitinkerers.org/technologies/jira) ([Markdown](https://aitinkerers.org/technologies/jira.md)) — 4 public demos
- [MCP servers](https://aitinkerers.org/technologies/mcp-servers) ([Markdown](https://aitinkerers.org/technologies/mcp-servers.md)) — 5 public demos
- [Playwright](https://aitinkerers.org/technologies/playwright) ([Markdown](https://aitinkerers.org/technologies/playwright.md)) — 32 public demos
- [Replit](https://aitinkerers.org/technologies/replit) ([Markdown](https://aitinkerers.org/technologies/replit.md)) — 8 public demos
- [Ruby on Rails](https://aitinkerers.org/technologies/ruby-on-rails) ([Markdown](https://aitinkerers.org/technologies/ruby-on-rails.md)) — 5 public demos
- [TypeScript](https://aitinkerers.org/technologies/typescript) ([Markdown](https://aitinkerers.org/technologies/typescript.md)) — 205 public demos