Two agent controls and two GitHub policies need a decision before they become the default path.
- Docker’s Sandbox Kit is an OCI image headed to the CNCF.
- Docker Cloud Sandboxes run an agent after the laptop shuts.
- GitHub can require a fresh login before a high-impact action.
- Copilot’s default feature policy takes effect on 22 October.
Architecture
Docker puts an agent’s permissions in an OCI image
Docker says a Sandbox Kit is an ordinary OCI image that carries an agent, its tools, and a typed list of the hosts, credentials, and volumes it asks to reach. The spec is Apache 2.0, and Docker says it is bringing that spec to the CNCF. Docker Sandboxes is the first runtime that enforces a Kit. Docker says it built Kits with AWS, Box, Datadog, Dynatrace, JFrog, and others.
This week. If an agent’s allowlist lives in a chat transcript or a shell history, write that list into a Kit and review the image diff before the next run.
Platforms
Docker Cloud Sandboxes keep an agent running after the laptop closes
Docker says Cloud Sandboxes are available now, so an agent workflow can keep running in Docker’s cloud after a developer’s laptop shuts down. The same announcement says teams can extend a local sandbox or start in the cloud, without provisioning their own machines for that run.
This week. Decide whether an agent that must outlive the laptop is allowed to run in Docker’s cloud, and name the Kit it must use before anyone starts one.
GitHub can demand a fresh login before a high-impact action
GitHub says Enterprise Cloud administrators can require an interactive re-authentication or a multi-factor challenge before a member takes a high-impact action. The public preview is limited to managed-user enterprises on github.com and to GitHub Enterprise Cloud with data residency, and only when Microsoft Entra ID is the SSO provider through SAML or OIDC. GitHub’s examples are creating a token, editing webhooks, changing organization security settings, and viewing recovery codes. After a successful check, that browser session can repeat high-impact actions for two hours. The setting does not turn on by itself. Support before pull-request merges is coming soon.
This week. If the enterprise is on Entra ID, turn on proof of presence for token creation and webhook edits before an agent or a stolen session can do either.
Copilot features left unset will follow a default on 22 October
GitHub says Business and Enterprise administrators can set a global default for eligible Copilot features: enabled, disabled, or let organizations decide. The policy can be configured now and does not change access yet. On 22 October, features still marked unconfigured follow that default. GitHub says an explicit enable or disable is kept, and preview features stay opt-in. The policy also covers Copilot code review and MCP servers in Copilot.
This week. Open AI Controls and set Default policy for new features before 22 October, so an unset feature does not follow a choice nobody made.
Link of the day
Docker’s note on packing an agent and its allowlist into one image: Sandbox Kit spec.
Leave a Reply