Troubleshooting
Common failure modes and how to get unstuck.
When a task fails you get a log with what was attempted and where it stopped. Here are the usual causes and fixes. If you're still stuck, email support@flarecode.sh with your task ID.
The agent can't install dependencies
The sandbox installs deps before working. If install fails:
- make sure your lockfile is committed and matches
package.json(or the equivalent for your stack), - check that all dependencies resolve from public registries — the egress allowlist blocks private registries by default,
- if you use a private registry, that's not supported in V0; vendor the dependency or open an issue with us.
Tests fail that pass locally
Usually an environment gap:
- a test needs a secret or service that isn't available in the sandbox — provide it via secret injection, or scope the task so those tests are skipped,
- the test depends on machine-specific state (a local DB, a fixed port) — make it hermetic, or tell the agent which tests to run.
The task hit its cost cap
Every task has a hard maxCostUsd. If it's exceeded, the task stops with no PR and isn't billed. Either the task is bigger than the cap allows, or it got stuck looping. Raise the cap for that task, or split it into smaller tasks with clearer done conditions. See Costs and limits.
The agent opened a PR that isn't quite right
Treat it like any PR from a teammate: leave review comments, or submit a follow-up task referencing the PR ("in PR #123, also handle the empty-input case"). You can also jump into interactive mode to steer it directly.
No PR appeared and no failure log
Rare. Check that the GitHub App still has access to the repo (it may have been revoked) — see Connect a repo. If access is fine and the task shows no result, email support with the task ID.
Provisioning is slow
First boot for a repo takes longer (clone + dependency install). Later tasks on the same repo are faster because the image is cached. Very large repos take longer to clone; oversized repos may be rejected.
Still stuck?
Email support@flarecode.sh with the task ID (and a link to the PR if there is one). During open beta you're writing to a person, not a ticket queue. For bugs and feature requests you'd rather track in the open, use the public FlareCode GitHub repo — issues, discussions, and the roadmap live there.