Agent run issue
Include the project name, run ID, prompt summary, approval state, and what you expected the agent to produce.
Support
Founder-friendly support with the project trail intact.
If Supr blocks a run, billing looks wrong, or an agent output needs review, start from the dashboard support page. Tickets keep the project, account, billing, runtime, and audit context close enough to investigate quickly, without making you reconstruct the whole story from memory.
Billing issue
Include your account email, current plan, Stripe checkout or portal context, and whether the issue blocks agent runs.
Login or access
Tell us the email you used, the page that failed, and whether you can still access the dashboard.
Security or abuse
Send the affected URL, account, logs, screenshots, or suspicious activity. Do not include secrets in email.
What to include
The fastest support ticket has a project, a run, and the exact failure.
When possible, include your account email, project name, relevant agent-run ID, billing plan, screenshot or error text, and a short description of what happened. That lets support connect the visible issue to usage records, audit logs, subscription state, and runtime status.
For legal, privacy, security, or login issues that prevent dashboard access, contact[email protected].
Priority guide
Route the issue by what it blocks.
Supr support is most effective when the ticket says whether the problem blocks agent work, billing, account access, or platform security.
Blocked run
The app is reachable, but usage, billing, approval, or runtime state prevents a needed agent run.
Billing problem
Checkout, portal access, subscription status, cancellation, or failed-payment state looks wrong.
Account access
You cannot log in, reach the dashboard, or access a project that should belong to you.
Security report
You found a vulnerability, suspicious access, exposed secret, or abuse pattern.