Debug Vercel-Hosted App End-to-End

I want to debug a Vercel App End-to-End.

INSTALL (run in my terminal)
  curl -fsSL https://composio.dev/install | bash
  composio login

You have access to 1000+ app integrations through the Composio CLI.
search → find tools. execute → run them. link → connect accounts.

Workflow: search → execute. If execute fails with an auth error, run link, then retry. Don't preemptively link accounts. Bias toward action — input validation and auth errors are self-descriptive, just try it.

CORE COMMANDS

  search
    Find tools. Use this first — describe what you need in natural language.
    composio search <query> [--toolkits <slug>] [--limit <n>]

  execute
    Run a tool. Handles input validation and auth checks automatically.
    If auth is missing, the error tells you what to run.
    composio execute <slug> -d '<json>'

  link
    Connect an account. Only when execute tells you to.
    composio link <toolkit>

EXAMPLE

  composio search "create github issue"
  # → returns GITHUB_CREATE_ISSUE
  composio execute GITHUB_CREATE_ISSUE -d '{ repo: "owner/repo", title: "Bug" }'
  # → if auth missing: "Run `composio link github` first"
  composio link github
  # then retry execute

TASK: Debug Vercel-Hosted App End-to-End
Likely toolkits: Vercel, GitHub, Supabase.

Steps:
  1. List recent production deployments
  2. Pull runtime logs for the active deployment
  3. Identify the error pattern (file, line, message)
  4. If the error touches the DB, check Supabase for active queries
  5. Reproduce the bug in a headless browser — navigate, fill the form, click submit
  6. Capture network responses and console errors
  7. Fetch the source file from GitHub
  8. Propose a patch — commit to a new branch and open a PR
  9. After merge, redeploy and re-run the browser repro to verify

Ask me before any action that sends messages or modifies data in a connected app.