General availability made coding-agent administration visible.
During a preview, a small group can treat the agent like an experiment. Once it is used across teams and repositories, the system needs owners, boundaries, and a recovery path. The agent writes into shared workflows and creates review work for other people. “Try the thing” becomes “operate the thing.”
The permission model should describe real actions:
read only:
inspect repository
summarize code
inspect logs
write with guardrails:
edit scoped paths
run tests in a sandbox
open pull requests for review
never by default:
touch secrets
change deployment configuration
publish without approval
That list belongs in the product and admin layer, not only in a prompt. If the policy is “be careful,” there is no enforceable policy.
The environment is part of the contract too. Packages, shell tools, filesystem state, network rules, secret access, caches, and resource limits all affect the result. The admin surface should make basic facts easy to answer: which repository received which sandbox, whether the checkout was clean, which commands were allowed, and whether network access was granted.
Usage volume is a weak operational metric. Better slices include repository, team, accepted versus abandoned runs, command failures, review rework, repeated sandbox denials, and entry point. The question is whether the agent is moving work forward or producing review-shaped debris.
Slack and SDK integrations make delegation less obvious. A thread may contain a secret, a customer detail, or a repository reference that should not flow into code. The admin layer should record which channel can start work, how it maps to a repository, which identity the run uses, and where the receipt lands.
The real gate is review quality. Small diffs, real project instructions, default checks, and clear ownership make the safe path easier. General availability did not remove the need for those controls. It made them ordinary infrastructure.
Related posts

About Jeremy London
Engineering leader and builder in Denver. I write about AI platforms, agents, security, reliability, homelab infrastructure, and the parts of engineering work that have to survive production.