Multi-repo projects
Use projects and agents to run work across several repos.
FlareCode is built for people who maintain more than one repo. The current hierarchy is Project → Agent → Session. A project usually maps to one repo or scratch workspace, agents belong to a project, and each run creates a session.
How it works
Connect several repos through the GitHub App. Create a project for each repo you want to operate. When you submit a task, choose the project and agent that should run it. The agent boots a sandbox for that repo, does the work, and opens the PR there.
Each project keeps its own:
- branch naming (
flarecode/task-<id>on that repo), - sandbox and workspace isolation,
- task history and cost tracking.
Fleet mode
On higher plans you can run several agents at once across different projects. The fleet view shows what's running, what's waiting on review, and what each project is costing. This is the point of FlareCode: a control surface for many repos, not a single-repo assistant.
Project and concurrent-agent limits by plan are on the pricing page and in Plans and billing.
Keeping repos isolated
Agents never share state across customers. A project working on repo A cannot see repo B's files unless you've connected B and created or switched to that project. See Security model for the isolation guarantees.