What this agent helps you do
A Firebase and Sentry backend debugging agent helps teams investigate errors involving data, auth, rules, functions, hosting, or release changes. Firebase provides backend configuration and project context, while Sentry provides error volume, stack traces, release signals, and affected user evidence.
When to use this workflow
Use it for mobile or web app incidents, backend release regressions, auth failures, security rule issues, and customer-impacting errors where the stack trace points toward Firebase-backed behavior.
How Firebase and Sentry give the agent context
Connect both plugins and provide the incident window, release, route, or feature area. Sentry should identify the error pattern and user impact; Firebase should help check whether rules, functions, auth, hosting, or data configuration could explain it. Keep deployments and configuration changes approval-based.
Example starter prompt
Correlate Sentry errors for this release with Firebase project context. Identify likely backend causes, affected users, validation checks, and approval-ready fixes. Do not deploy or change Firebase configuration without approval.Suggested workflow steps
Start with the highest-impact Sentry issue and trace when it began. Have the agent inspect related Firebase rules, functions, auth settings, hosting changes, or data assumptions, then compare the timing and affected feature path.
Expected handoff
Ask for a timeline, evidence from each system, likely causes, checks to run, user impact, risk level, and approval-ready remediation options.