Welcome

FlareCode is a cloud control tower for coding-agent fleets. Connect your repos, give each one a persistent cloud workspace, hand off work in plain English, and review Pull Requests from anywhere. Agents plan, code, run checks, and open branches; you keep control of cost, review, and merge.

These docs are short and practical, written for builders running more software than they have desk time.

Two ways to work

• Goals — describe an outcome ("add a /healthz endpoint with a test"). The agent plans it, runs the work, checks itself, and opens a PR. Best for concrete deliverables you can review later.
• Interactive — drive an agent directly in a hosted workspace, like a coding terminal you steer in real time. Best for exploration and tight back-and-forth.
• Fleet — keep an agent on every repo, switch between them from one rail, and review the PRs as they land.

See Interactive vs goals for when to use each.

New here?

1. Getting started — sign in to your first PR in about five minutes.
2. Connect a repo — install the GitHub App, per repo, least privilege.
3. Submit a task — what to write and what happens next.

Good to know

• Your code stays yours. Your workspace is encrypted and private, backed up so you never lose work, never used for training, and deleted when you destroy the agent. See Security model.
• Cost cap you control. Every task carries a hard cost cap; exceed it and the task stops instead of drifting. See Costs and limits.
• Bring your own model, or use ours. Default to our bundled model, or drop in your own keys. See Choosing a model.
• Review proof, not claims. Agent work lands as a normal GitHub Pull Request with branch isolation, test output, and reviewable diffs.
• Found a bug or want a feature? File it on the public FlareCode GitHub repo — issues, feature requests, and the roadmap are all open there.