Resources

flowchart TD
  Schedule([Once each morning]) --> Inspect[execute_sql and query_logs]
  Inspect --> Signals["Resource measurements and request growth"]
  Signals --> Review{Anything new to report?}
  Review -->|Yes| Report[Finding and next step]
  Review -->|No| Silent[Stay silent]
  Inspect -->|Missing data or access| Gap[Report new or changed gaps]

What it watches

• Database and table sizes, including indexes
• Current connection counts by role and state
• API request growth across the last two complete UTC days
• Resource growth toward a confirmed limit, when enough history is available

It uses read-only execute_sql and query_logs on project-scoped Supabase MCP. Request counts do not establish billing totals.

When it watches

What it will output

This prompt reports new or changed request-growth signals and resource-limit risks. When saved measurements support a forecast within 14 days, it includes the estimated date, calculation, and scaling guide. If history or a matching limit is missing, it explains what it needs instead of inventing a date. See what triggers a resource report.

If a check cannot run, the agent tells you what is missing. Clear checks and unchanged findings stay quiet.

When the agent finds an issue, it reports in the harness. Send that report wherever you already triage work. Use the connections your harness already has. For example, Codex can open a Linear issue.

Keep the Supabase project read-only. Filing a ticket is work in the harness, not a change to the project.

If you want that routing on every scheduled run, add it to the prompt.

Set up the agent

Allow the agent to read the documentation linked in its prompt. Configure your harness to save measurements and alert state, then reload them on each run. Forecasts need at least seven daily measurements and a confirmed limit for the same resource and units.