Control plane | Overlane Docs

Claims and leases on scope, hard budget stops, one rules source for every agent, risk-based pull request routing, and an egress allowlist with brokered credentials.

When several agents work on one project at once, four things go wrong: they edit the same files, a loop spends past what you meant to allow, each agent reads a different copy of the rules, and a flood of pull requests waits for the same reviewer. A fifth risk sits underneath: an agent in a sandbox can reach any host and hold credentials it never needed.

The control plane is Overlane’s answer to those five. Every part is a deterministic check on the server or in your checkout. A model is used in exactly one place, as an optional signal that can only make a pull request wait longer.

Claims and leases: an agent claims the files or modules it will change. Another agent’s overlapping claim waits its turn, and git merge-tree flags a real conflict before either pull request merges.
Budgets: a run stops at its limit before the spend, per task, agent, project and team, with exit code 6 and a stored record.
Rules sync: one rules source written to AGENTS.md, CLAUDE.md, Cursor and Gemini files, with drift reported by overlane doctor and CI.
Pull request routing: deterministic checks first, an optional model label that can only raise the lane, a fast path with independent-agent approval, and batching of related pull requests.
Egress and credentials: an allowlist of the hosts sandboxes may reach, and per-task credential grants whose value never reaches the agent, a log or the workspace.

overlane claim list
overlane budget show
overlane rules check
overlane doctor

Agent use and the override

An agent token for the team can use every command on these pages. Nothing waits on a person under the default autonomy setting. Raising a spending limit is a safety class action, so it asks for an independent agent’s approval in every mode (see Autonomy). A person can always do the same thing, and can override or undo any of it.

Native projects (hosted by Overlane) and projects connected to GitHub use the same commands and the same checks. Where a check needs a runner that Overlane operates for native repositories, the page gives the command to run in your own checkout.