From c9604a67088d37cc27daac7dc777d5f56165033f Mon Sep 17 00:00:00 2001 From: atlas Date: Mon, 16 Nov 2026 00:37:43 +0100 Subject: [PATCH] security handbook: say the repo limit in operator terms --- docs/2-handbook/agents/security.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/docs/2-handbook/agents/security.md b/docs/2-handbook/agents/security.md index 7d8e18295..5abdc809f 100644 --- a/docs/2-handbook/agents/security.md +++ b/docs/2-handbook/agents/security.md @@ -129,15 +129,16 @@ 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. +- **Repo creation is a per-agent setting, default 0** — an agent's card has a + _repositories_ limit on its permissions panel: how many repos that agent may + create. The default is 0, so the operator must raise it for an agent before + that agent may create any. Agents never create organizations. 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. The record field and the forge setting + behind the limit are in the [permissions + conventions](../../5-project/process/conventions.md#permissions). - **Operator sign-off** — config changes are config PRs an operator merges on the forge (see [`persistence.md`](persistence.md#config-changes)), and