Getting started
From signup to your first Pull Request in about five minutes.
Five minutes from signup to your first PR. Here's the whole loop.
1. Sign in with GitHub
Go to /login and continue with GitHub. Sign-in currently requests read:user, user:email, and GitHub's repo OAuth scope so FlareCode can identify you, show your reachable repositories, and support older repo flows. Repository work is still authorized separately through the GitHub App install in the next step.
2. Install the GitHub App on a repo
From the app, choose New project or connect a repo from an existing project. We send you to GitHub's install screen. Pick exactly the repositories you want FlareCode to reach — install per repo, never per org.
The app asks for four scopes, and nothing else:
| Permission | Why |
|---|---|
contents: write | Commit changes to a feature branch. |
pull_requests: write | Open the Pull Request. |
metadata: read | Look up the default branch. |
actions: read | Read CI status to know when the PR is ready. |
It never requests admin:repo_hook, delete:repo, admin:org, or any org-level scope. Details in GitHub permissions.
3. Spin up the project and agent
Pick a repo-backed project. Projects contain agents, and agents create sessions for each run. We boot a sandbox, clone the default branch, and install dependencies. First boot for a repo takes 10–30s; later boots are faster because the private encrypted workspace is retained for the life of the agent.
If you already use Claude Code, Codex, Cursor, or VS Code locally, you can also run the import helper to discover local agent history and repo rules:
npx --yes @flarecode/import-memory@latestSee Import local agent memory for the curl wrapper and dry-run options.
4. Hand off the task
Describe the work in plain English:
Add a /healthz endpoint that returns the package.json version.
Add a passing test. Open a PR titled "feat: healthz endpoint".The agent edits, runs your tests in the sandbox, commits to a branch named flarecode/task-<id>, and opens the PR. You can close the tab — it keeps working.
5. Review
When the PR is ready you get a notification (email, GitHub mobile, or Slack, depending on your settings). Open it, read the diff, approve or close. We never push to your default branch.
That's the loop. Next: Connect more repos or learn Interactive vs goals.