docs: SENTRY_AS_PRODUCT.md — wire Sentry into every Vibn project
The Sentry wiring shipped today catches errors in the platform itself. The bigger product opportunity is wiring Sentry into every project Vibn ships, then feeding those errors back into the user's AI chat — turning the AI from "codes for you" into "owns the product." Proposal lays out 4 staged shippable chunks (~8 hr total): 1. Auto-provision per-project Sentry on first deploy 2. Bake Sentry into every scaffold template 3. Expose project_recent_errors / _detail / _resolve as MCP tools 4. Auto-surface unresolved errors at chat-turn start Folded into BETA_LAUNCH_PLAN.md as Phase 2.9. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -96,6 +96,7 @@ server: {
|
||||
| 2.6 | Bake `HEALTHCHECK 127.0.0.1` into `vibn-frontend/Dockerfile` so future apps inherit | AI | ✓ done 2026-05-01 | Already in `vibn-frontend/Dockerfile:67-68`; comment explains the IPv6 trap |
|
||||
| 2.7 | Audit other Dockerfile-based apps for the same `localhost`/IPv6 trap | AI | ✓ done 2026-05-01 | Audited `vibn-dev/Dockerfile` and `vibn-agent-runner/Dockerfile` — neither defines a HEALTHCHECK, so neither can hit the localhost/IPv6 trap. No action needed today; revisit when either gets a healthcheck added. |
|
||||
| 2.8 | **Tool-error recovery middleware** (AI_HARNESS_GAPS.md §1) — pattern-match known-recoverable tool errors and inject synthetic instructions before the model's next round | AI | ✓ done 2026-05-01 | `vibn-frontend/lib/ai/error-recovery.ts`. Initial rules: orphan container conflict, image pull denied, port allocated. Wired into `app/api/chat/route.ts` tool-result loop. |
|
||||
| 2.9 | **Sentry-as-product loop** (SENTRY_AS_PRODUCT.md) — auto-provision per-project Sentry, bake into scaffolds, expose error feed to AI as MCP tools, auto-surface unresolved errors at chat-turn start | AI | 8 hr | Highest-leverage item still ahead of beta. Turns AI from "codes for you" into "owns the product." Reuses today's Sentry org + tokens. See proposal doc for staged rollout (4 sub-stages, each independently shippable). |
|
||||
|
||||
**Definition of done:** force-fail a route in staging → Sentry alert lands in
|
||||
< 1 min. Force-fail a Coolify deploy → notification fires. Reproduce an
|
||||
|
||||
Reference in New Issue
Block a user