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:
parent
dc0d08b7fb
commit
1edeb5c55d
1 changed files with 763 additions and 58 deletions
|
|
@ -340,6 +340,15 @@ explicit `unrestricted_internet: false`; read the pair with
|
|||
`DELETE` keeps it. A hive that doesn't read the field sees `false` and enforces
|
||||
the list. The proxy's handling is under _Log mode_ in [the egress proxy](../../4-implementation/networking/network.md#egress-proxy-squid).
|
||||
|
||||
**Repository limit** — the record also carries `max_repos`, how many repositories
|
||||
the agent's forge account may create, 0 to 100. An absent value is 0. Only the
|
||||
controller reads it: it sets the account's Forgejo `max_repo_creation` from it at
|
||||
`CreateForgeUser`, and again for an existing account within seconds of a change,
|
||||
at every start and every five minutes (`forge::agent_max_repos`). It also turns
|
||||
off creating organizations on every agent account. A `PUT` that leaves the field
|
||||
out, a `DELETE`, and a re-create keep the stored value; the route refuses more
|
||||
than 100.
|
||||
|
||||
**How a change applies** —
|
||||
- The agent's harness reads its own key every 10 seconds and builds every
|
||||
turn's `--tools`, `--allowedTools` and MCP config from the last value, so a
|
||||
|
|
|
|||
Loading…
Reference in a new issue