Health

flowchart TD
  Schedule([Every hour]) --> Inspect[query_logs and execute_sql]
  Inspect --> Signals["Server errors and connection pressure"]
  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

• API and Auth server-error rates in the last complete hour, compared with the preceding hour
• Current Postgres connection pressure

It uses query_logs and read-only execute_sql on project-scoped Supabase MCP.

When it watches

What it will output

This prompt reports new or changed problems with the affected service, measured error rate or connection usage, and a next investigation step. See what triggers a health 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. Save its alert state between runs so it can avoid repeat reports.