Connect a repo
Install the GitHub App per repo, create projects, and revoke access at any time.
A FlareCode project usually maps to one connected repo. Projects contain agents, and agents create sessions for each run. You stay in control of which repos FlareCode can see, and you can take that access back at any time.
Install per repo
When you create a repo-backed project, GitHub asks which repositories to grant. Pick one, several, or "all" — your call. We recommend installing per repo: grant only what the project needs right now.
Install is always per repo, never per org. FlareCode never reads your org membership graph or org settings.
Add more repos later
You can extend an existing install from GitHub.com → Settings → Applications → Installed GitHub Apps → FlareCode → Configure. Add a repo to the list and save. Back in FlareCode, create or switch to the project for that repo. See Multi-repo projects.
What the app can do
Within a connected repo, an agent can:
- clone the default branch into its sandbox,
- create and push branches named
flarecode/task-<id>, - open and describe Pull Requests,
- read CI status to know when a PR is ready.
It cannot push to your default branch, change repo settings, manage collaborators, or delete anything. Branch protection enforces this server-side, and the agent enforces it client-side too.
Revoke access
Two options, both immediate:
- Per-repo. GitHub → Installed GitHub Apps → FlareCode → Configure → adjust the repo list → save.
- Full uninstall. Same screen → Uninstall. All access ends immediately; we delete the install record on our side within 60 seconds.
After you revoke, any PRs the agent already opened remain on GitHub — those are yours. Your workspace is held only as a private, encrypted snapshot for the life of the agent, and deleted when you destroy it. See Data and retention.