Settings & config
The settings that shape how Leroy works for your account — how much it does on its own, what it can spend, which repos it touches, and who's on the team. You set these in the app; you don't edit config files or environment variables.
01 Oversight & policies
Policies decide how much Leroy does without checking in. Every piece of work passes three gates — intake (picking it up), plan (starting to code), and ship (merging the PR) — and at each one Leroy either runs on Auto or Always asks you first. Set a baseline for the whole account, then refine it per source or per repo as you build trust.
02 Spend cap per task
Set a dollar cap per ticket. If a piece of work runs over it, Leroy stops, marks the ticket stuck, and asks you before spending more. It's a hard stop — it applies even when every gate is on Auto.
03 Connected repos
Leroy works in the GitHub repositories you connect. Connecting installs the Leroy GitHub App with access scoped to the repos you choose, so it can read code, open branches, and raise pull requests — and nothing outside that list. You can add or remove repos at any time.
04 Risky paths
List file globs that should always get a second look — billing/**, auth/**, infra config. If a change touches one of them, Leroy pauses for your approval before shipping, even when the ship gate is on Auto. Like the spend cap, it sits above the gates and can't be turned off by loosening policies.
05 Team & invites
Invite teammates to the account so they can file tickets, review PRs, and answer Leroy's questions. Tickets a teammate files from the app are treated as trusted by default and skip the intake gate; if someone's submissions need a closer look, you can flip them to gated on the team screen so their tickets go through intake review like any inbound signal.