Project account locks
Account locks restrict which AI subscriptions and Git accounts may be selected for a Project group or repository. Defaults remain preferences. A saved default cannot override a lock, and an unavailable locked account does not authorize an automatic fallback to another subscription or credential.
An owner can narrow their own Project-group and repository choices. The canonical infrastructure operator can separately impose a ceiling for one server user, one of that user's Project groups, or one repository. Effective access intersects those administrator ceilings with owner narrowing and current account ownership or shared-account grants. Another user with an administrator role does not gain the canonical operator's ceiling authority.
null inherits at the edited layer; [] permits no accounts of that kind.
Removing owner narrowing does not remove an administrator ceiling. AI and Git
selections are independent. These settings do not create or copy credentials,
share another owner's Git connection, add a team membership, or increase the
quota of a shared AI subscription.
Changes are checked on new launches, resume and account changes, including every attached repository. They do not stop an active provider, rewrite its credentials or change its selected account. A restricted Git repository cannot bypass its required account with an explicit-none, read-only or shell launch. A repository without a Git remote can still operate without Git credentials.
Read and save as the owner
The console uses the existing Projects account-lock settings. The same controller routes and CLI preserve the signed-in owner's scope:
devctl account-locks scopes
devctl account-locks get repository-id
devctl account-locks group project-group-id
Reads return configured, inherited, administratorCeiling, ownerNarrowing
and effective selections, current safe choices, saved defaults, revision
and effectiveRevision. A selectable account's permittedByParent records the
inherited boundary. Labels are for display; use the exact current owned or shared
facade ID. Unavailable or revoked choices stay unavailable.
Save the complete change in a local JSON file and pass --file FILE or --file -:
{
"scope": {"kind": "repository", "id": "repository-id"},
"revision": 3,
"effectiveRevision": "REPLACE_WITH_THE_CURRENT_64_CHARACTER_HASH",
"agentAccountIds": ["current-owned-or-shared-facade-id"],
"gitAccountIds": null
}
devctl account-locks put --file account-lock-change.json
Use the actual revisions from the read. revision protects this layer;
effectiveRevision also detects inherited policy and available-choice changes.
On HTTP 409, reread and preserve the user's intended change rather than replaying
an obsolete replacement. Mutations are not automatically retried. A lost response
requires readback before another write.
The equivalent typed operator MCP tool is project_account_locks:
{"action":"show","scope":{"kind":"repository","id":"repository-id"}}
Use action:"scopes" for owned scopes. To save, pass
{"action":"save","change":{...}} with the complete typed change above.
The transport retains the caller's actual controller principal; an actor,
ownerUserId or arbitrary operation URL is not an account-lock argument.
Separate administrator ceilings
Only the canonical infrastructure operator administrator can use these operations:
devctl account-locks ceilings targets
devctl account-locks ceilings scopes server-user-id
devctl account-locks ceilings get server-user-id --kind user
devctl account-locks ceilings get server-user-id --kind project-group --id group-id
devctl account-locks ceilings get server-user-id --kind repository --id repository-id
devctl account-locks ceilings put --file ceiling-change.json
A ceiling change adds targetUserId to the same complete change shape. A user-wide
scope is exactly {"kind":"user"}; group and repository scopes require their
exact id. Use the target user's legitimate account choices. A canonical shared
AI source ID is resolved only through its exact current active grant to that
user's facade; it never grants access by itself. Ordinary owners use facade IDs.
Operator MCP exposes the fixed actions ceiling-targets, ceiling-scopes,
ceiling-show and ceiling-save. Reads with ceiling-scopes or ceiling-show
require targetUserId; ceiling-show also takes scope. Saves take a complete
change including targetUserId. The controller checks canonical operator
identity independently of the arguments.
The existing operator catalog documents these routes:
GET /v1/project-account-locks/scopesandGET/PUT /v1/project-account-locks.GET /v1/project-account-locks/ceilings/targetsandGET /v1/project-account-locks/ceilings/scopes.GET/PUT /v1/project-account-locks/ceilings.
Discover exact schemas with controller_operations filtered by
project-account-locks. controller_request uses the existing authenticated
handler; catalog discovery does not grant administrator authority. If a connected
controller does not expose the operation, report its unsupported version instead
of guessing another route.
Managed-session inspection
The session MCP tool get_project_account_locks({}) reads only the authenticated
session's current repository and owner. In a secondary checkout it describes
that checkout's Project. It accepts no repository, owner, actor, scope, selection
or credentials. The session CLI equivalent is:
devctl account-locks get
Use its existing native MCP socket or session-token transport and omit PROJECT.
Owner/group/ceiling commands reject native authority before reading input files.
Managed sessions cannot edit account policy or administrator ceilings, even when
the session owner is an administrator. Ask an authorized owner/operator to change
the settings if the required account is excluded. A prose approval or permission
rule does not change the actual account lock.
The host broker and controller publish this read through the existing built-in workflow tool group, subject to current MCP policy. A broker catalog update does not prove that a running native client refreshed its cached tool list. Use an already authorized session CLI/socket where available; preserve active providers and report unavailable native discovery rather than restarting them.