✦ Support
Stuck on a run? Here's where to look first.
Most issues with a run are covered below or in the troubleshooting guide. For anything else, the fastest path is usually opening an issue with your run's stdout attached.
Contact channels
Bugs & broken runs
Open a GitHub issue
Best for anything reproducible — a fix that corrupted a file, a stack that mis-detects, a run that returns success=false unexpectedly.
Open an issue →
Everything else
Email support
Account questions, access requests, or anything you'd rather not put in a public issue.
support@yourdomain.com →
How things work
Reference docs
Full API surface, the CSV schema, write-safety guarantees, and supported stacks.
Read the docs →
How to use it
Guides
Quick start, CSV prep, choosing which agents to run, and reading a run's output.
Browse guides →
Common issues
The five things almost every support request turns out to be.
500 — OPENAI_API_KEY not set
The key isn't in .env, or .env isn't being loaded before the server starts.
Process timed out after 10 minutes
Too many rows for one run — split the CSV or run technical-only first.
"No file mapped for {url}"
The URL doesn't match your app/pages routing, or the repo isn't a Next.js project.
A file came back unchanged
safe_write rejected a truncated or empty model response and kept the original on purpose.
Push fails after the agent runs
The GitHub token doesn't have push access to the target branch, or the branch is protected.
FAQ
Will this ever overwrite something I wrote by hand?+
On-page and technical fixes live inside marker-scoped blocks (
ONPAGE-AUTO-FIX, TECHNICAL-CANONICAL) and only replace what's between their own markers. Everything else in the file is left alone, and safe_write refuses to write anything that looks suspiciously truncated compared to the original.Is it safe to point this at my production branch?+
Technically yes, but we'd recommend a fork or a disposable branch for your first run on any repo. There's no dry-run mode yet — a submitted run commits and pushes automatically as each agent finishes.
What happens if the OpenAI call fails for one page?+
That page keeps its original content and the failure is logged with a ⚠️ marker in stdout. One failed page never stops the rest of the run.
Is my GitHub token stored anywhere?+
It's used to build an authenticated clone URL for that single run and passed through the subprocess environment — it isn't written to disk or logged.
Does this work on WordPress or Shopify sites yet?+
Not yet. Today it's Next.js only (App Router and Pages Router) for per-page fixes; other stacks only get the site-level technical files. Shopify and WordPress support are on the roadmap — see the docs page for status.
What about off-page optimization — backlinks, citations, mentions?+
That's intentionally manual right now. It isn't something a repo edit can produce or verify, so it's out of scope for the autonomous pipeline until there's a reliable way to automate it.
Reporting a security issue
If you find something that could expose a GitHub token, an API key, or let one user's run affect another's, please don't open a public issue for it. Email security@yourdomain.com directly with reproduction steps, and we'll follow up before any public disclosure.