Coding

Post a daily Sentry error digest to Slack with a Claude routine

A team runs a Claude routine with no internet except Slack and Sentry that compares errors to source code and posts a daily digest.

By mhammerc on Hacker News · Posted · Added Oct 15, 2026

Difficulty
IntermediateOur rating
Time to build
est. 1-2 hoursOur estimate
Monthly cost
Not reported
Revenue
Not reportedWe only show revenue the source states
Engagement
0 replies to HN commentComment in “Ask HN: Who is using MCP in production?” (198 points, 201 comments) · fetched Oct 15, 2026

What they did

mhammerc’s team runs a Claude routine whose only network access is the Slack API and the Sentry MCP. It reads errors, compares them to the app source, and posts a daily digest.

How it went

They say the reports are very accurate.

Worth knowing

Limiting network access to exactly two services keeps the routine safe.

Builder recipe

Our own starting point, written from the source. Adapt it to your setup.

Stack

  • Scheduled Claude routine
  • Sentry MCP
  • Slack API
  • Read-only repo access

Steps

  1. Open the repo in your coding agent and describe the goal and constraints.
  2. Ask for a plan first, then let it implement in small, reviewable steps.
  3. Run the tests or the app after each step and feed errors back.
  4. Review the diff before merging.

Starter prompt

Read the last 24h of new Sentry issues. For each, find the likely line in the repo, explain the cause in one sentence, rate severity, and post a digest to #eng-alerts.

Tags

Agent Claude
Industry Software

Read the original

Related use cases

The Daily 5.

Five real AI agent use cases each morning, each with a recipe and a source. Plus a Sunday roundup. Free.