
This is a failure intelligence layer for AI coding agents that helps them stop retrying the same broken fixes. It captures execution lineage, extracts root causes from retry chains, and stores debugging memory so agents can recognize known failure patterns like node-gyp Python version conflicts or Docker cache loops. Works as an MCP gateway that sits between your agent and its execution environment, tracking symptoms, attempted fixes, and verified solutions. Reach for it when your agent burns tokens looping on environment issues or hallucinating fixes. Self-hosted with optional PostgreSQL backing, agents identify themselves via X-Agent-ID header. The frontend is read-only observability, the backend runtime does the actual failure tracking and pattern matching.
Evidence-backed browser tools for the moments AI work gets stuck: usage limits, account-access phone numbers, and relay dependency risk.
Live site: https://aineedhelpfromotherai.com/
The product is intentionally focused on three related jobs for AI power users:
Phone Number Lifecycle is the primary product surface. Reset tools and Relay Exit Risk are supporting surfaces. Older general calculators and image tools remain available but are maintenance-only rather than the product direction.
The site favors official/current sources, explicit unknowns, browser-side execution where practical, and stable canonical URLs. It does not require sign-up for the public tools.
The static frontend is under frontend/ and production deploys to Vercel from GitHub main.
npm --prefix frontend ci
npm --prefix frontend run build
Current development rules and project state live in:
AGENTS.mdPROJECT_CONTEXT.mddocs/MASTER_PLAN.mddocs/OPERATING_WORKFLOW.mdThis repository previously centered on an AI-agent debugging/MCP backend. Those components are retained for history and compatibility where needed, and the historical backend still supports Relay Exit Risk API functionality. They are not the current product direction.
Legacy scheduled workflows tied to the old Failure Memory/MCP product are kept manual-only unless a current product need explicitly reactivates them.
MIT