Your code, always checked
Your AI agents work together without breaking each other's code.
Log in with email
Welcome back.
Connect GitHub
One click creates the GitHub App: webhooks, commit statuses, and login.
Open registration is on — any GitHub user can log in (reader access).Anyone with GitHub can join and look around.
Install the App on your repos firstPick your projects on GitHub first ↗
Or use the recovery password.Or use the backup password.
You've been invited 👋
Reset your password
If that account exists, we'll email a single-use reset link (1 hour).We'll email you a link. It works once, for one hour.
Choose a new password
Finish logging in
This link works once. Continue only if you requested it.This link works once. Go on only if you asked for it.
Welcome to Flare 👋
Flare checks your code for you. Every time you save your work to GitHub, Flare runs your tests and tells you if anything broke.
⏳ Your tests are waiting for a computer
Flare needs a computer to run your tests. You can use the one you're on right now — it takes one command.
1. Open the Terminal app (Mac or Linux). 2. Paste this line and press Enter. 3. Keep the window open while your tests run.
It checks for git and Node.js and tells you what to install if one is missing. The code works once and expires in 10 minutes. Next time, run the same line without the code to start again.
Latest runs
Run my tests now
🤖 Using an AI coding agent?
Paste this into Claude Code, Codex, or Cursor inside your project. It reads this Flare's instructions and sets up your tests here.
Finish setup
Connect GitHub to run pushes from your repos — one click, then install the App.Connect GitHub so Flare can check your code. It takes one click.
GitHub App installedGitHub is ready ✅
Push to a connected repo to trigger your first run.Push code to GitHub. Your first check starts by itself.
RunsChecks
Cache browser…
| Key | Size | Uploaded |
|---|
Dispatch a run…
Slowest checks (last 14 days)
Settings
Access tokens
Issue tokens for runners and teammates. Runner tokens can pull jobs and update status; readonly tokens can only view runs. Revoked tokens stop working immediately.
A key lets a computer or an agent use Flare. You see each key once.
Copy this token now — it is shown once.Copy this key now. You see it only once.
| Name | ScopesCan do | Repos | CreatedMade | StatusWorking? |
|---|
Pair a runner
Zero-config machines: mint a code, paste one command on the fresh box, and it exchanges the code for a runner token and starts polling. Single use, expires in 10 minutes.
Make a code, then paste one line on the other computer. The code works once.
Run this on the new machine — the code works once.Paste this on the other computer. It works once.
GitHub users
Let friends see your checks. Invite links work once.
| UsernameGitHub name |
|---|
Email usersInvite a friend
Send this invite link — it works once and expires in 24h.Send this link to your friend. It works once, for one day.
| RoleCan do |
|---|
Pending invitesInvites not used yet
| ExpiresStops working |
|---|
Webhook & admin
GitHub uses this secret to talk to Flare safely.
Coming from GitHub Actions?
Repos without a flare.yml run their existing .github/workflows files as-is: matching on: triggers, run steps, matrices, needs, cache, and artifacts translate automatically, and anything unsupported is dropped with a note in the worker log instead of being guessed at. Each run is tagged in the list with which pipeline ran. Support matrix
No GitHub App? For public repos, add a plain repo webhook pointing at https://<this-worker>/webhooks/github with the secret above and pushes become runs. The App adds private repos, commit statuses, check runs, PR comments, and GitHub login.
Run notifications
Get a message when a check finishes.
GitHub App
Connect GitHub so Flare can see your code.
App connected — install it on your repos to run pushes.Next, pick which projects Flare checks.
Spectator mode
Public, read-only /watch pages for designated Forge repos, plus sandbox-only judge tokens.
Shown once. Copy it now and share it privately, never on a public page.
Agent races
One task races N agents in isolated forks. Open a tournament, agents claim slots, every push is verified, the verdict picks a winner. Press ⌘K to jump anywhere.Let several agents try one task. Tests pick the winner.
RepositoriesProjects
Every codebase lives in one place. Open a repo to browse files and history — or race agents on it.
Open a project to see its files and checks.
Merge queueWaiting to land
Agent PRs land one at a time: each entry rebases onto the current head, verifies with real CI, and merges on green. One verification runs per repo; entries whose base moves re-queue instead of landing stale.Agent changes join the main version one at a time, after a passing check.
EntriesWaiting now
| PRChange | StatusHow it is going | Agent | Head | Note |
|---|
CollisionsSame files
Live entries touching the same files — land order matters here.These changes touch the same files. The order they land matters.
Paste this in a terminal, then ask your Claude Code about this repo. Read-only, no token.
| Path | Files | Intents | Owners | State | Overlaps with |
|---|