Watch
0
0
Fork
You've already forked hyperhive
0

agents get a per-agent repo limit in their permissions record, orgs are locked

max_repos (default 0, 0..=100) lives in the agent's agent-permissions record and is edited on its permissions panel. The controller applies each agent's own value as max_repo_creation at CreateForgeUser and to existing accounts on change, restart and every five minutes; agent accounts may not create organizations.
This commit is contained in:
atlas 2026-11-15 20:47:21 +01:00 • committed by mara
commit 1edeb5c55d
2 changed files with 763 additions and 58 deletions

View file

@ -119,7 +119,7 @@ checkpoints**, not about sandboxing the agent from its own tools:
- **Operator merges, not the agent** — an agent may _push_ branches, but a
**human (the operator) merges the PR**, keeping a person in the loop on the
highest-value action. On the **internal forge this is technically enforced,
not just convention**: agents can't create repos (`max_repo_creation = 0`),
not just convention**: agents can't create repos by default (next bullet),
and `main` on an `agent-configs/<name>` repo carries swarm-controller's
branch protection: merge and approval allowlisted to the `operators` team,
which swarm-controller converges on every config repo. An operator's merge
@ -129,6 +129,15 @@ checkpoints**, not about sandboxing the agent from its own tools:
settings nor merge its own PR. It's **not** set up for external VCS (GitHub
etc.), though — there, operator-merge is process + accepted risk, not a
technical control.
- **Repo creation is a per-agent setting, default 0** — the _repositories_ badge
in an agent's card sets how many repos that agent's forge account may create
(`max_repos` in its permissions record, Forgejo's `max_repo_creation`, 0 to
100). The operator must raise it for that agent before it may create any. Agents never create organizations: the
controller turns that off on every agent account. A repo an agent creates is
its own, so the operator-merge gate doesn't cover it, and the agent can add a
CI workflow to it. CI workflows run unsandboxed on the CI runner, which is
arbitrary code on the runner host. Allow repo creation only for agents you
would trust with that.
- **Operator sign-off** — config changes are config PRs an operator merges
on the forge (see
[`persistence.md`](persistence.md#config-changes)), and

View file

@ -26,7 +26,7 @@ by a test). swarm-controller mints every agent token with it:
| `write:repository` | Create, clone, push, delete repos; merge PRs. |
| `write:issue` | Open / comment / review issues **and** pull requests (Forgejo namespaces PR conversation under issues). |
| `write:user` | Edit own profile, create repos under own user. |
| `write:organization` | Create + manage orgs (lets agents share a forge namespace). |
| `write:organization` | Manage orgs the agent belongs to. The forge refuses to create one: agent accounts may not. |
| `read:user` | Token-owner endpoint used for self-identification at harness startup. |
| `write:misc` | Hooks, attachments, the rest of the long tail. |
| `read:notification` | Poll `GET /notifications` for unread events. |