From db26828610f700e9e17e6440f05ba22d66155ec3 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Fri, 14 Aug 2026 11:53:55 +0000
Subject: [PATCH] docs: remove extended-agent OAuth workaround

Extended-agent OAuth interception is fixed for the upcoming sbx v0.40 release by docker/sandboxes#4985. Remove the temporary limitation and API-key workaround while retaining the credential-binding approval clarification.

Co-Authored-By: Codex <noreply@openai.com>
---
 .../ai/sandboxes/customize/kit-examples.md    | 21 ++-----------------
 .../ai/sandboxes/security/credentials.md      |  7 -------
 2 files changed, 2 insertions(+), 26 deletions(-)

diff --git a/content/manuals/ai/sandboxes/customize/kit-examples.md b/content/manuals/ai/sandboxes/customize/kit-examples.md
index ebae4807705..331b4372e9f 100644
--- a/content/manuals/ai/sandboxes/customize/kit-examples.md
+++ b/content/manuals/ai/sandboxes/customize/kit-examples.md
@@ -364,25 +364,10 @@ the child kit's name:
 $ sbx run claude-sonnet --kit ./claude-sonnet
 ```
 
-Proxy-managed OAuth isn't supported for a third-party kit that extends the
-built-in `claude` agent. Store an Anthropic API key on the host before the first
-launch:
-
-```console
-$ sbx secret set anthropic
-```
-
 When you launch the kit for the first time, `sbx` prompts you to approve its
 inherited Anthropic credentials. Because this is a third-party schema v2 kit,
 `sbx` records your approval as a
-[credential binding](../security/credentials.md#credential-bindings). The
-sandbox receives a sentinel value, and the proxy injects the real API key into
-requests to the domains declared by the kit.
-
-> [!WARNING]
-> The approval prompt also lists OAuth, but OAuth doesn't work for the extended
-> agent. If you use Claude Code's `/login` command, Claude Code stores the real
-> OAuth tokens inside the sandbox.
+[credential binding](../security/credentials.md#credential-bindings).
 
 OpenCode supports an additional config file through `OPENCODE_CONFIG`. Keep the
 kit's config separate from the sandbox-managed
@@ -451,9 +436,7 @@ sandbox:
 
 The child inherits the built-in image, credentials, network permissions,
 persistent volumes, settings, MCP integration, and agent instructions. Its
-`sandbox.entrypoint` replaces the inherited entrypoint. Proxy-managed OAuth
-isn't supported for the extended agent, so follow the
-[Anthropic API-key setup](#customize-agent-settings) before launching it.
+`sandbox.entrypoint` replaces the inherited entrypoint.
 
 Launch with the kit's `name:` as the agent argument to `sbx run`:
 
diff --git a/content/manuals/ai/sandboxes/security/credentials.md b/content/manuals/ai/sandboxes/security/credentials.md
index 9507522ac57..93083d4d751 100644
--- a/content/manuals/ai/sandboxes/security/credentials.md
+++ b/content/manuals/ai/sandboxes/security/credentials.md
@@ -348,13 +348,6 @@ If a third-party kit declares the same service itself, that service also
 requires approval. Kits on `schemaVersion: "1"` inject their declared
 credentials without a binding.
 
-> [!WARNING]
-> Proxy-managed OAuth isn't supported for third-party sandbox agents, including
-> kits that extend a built-in agent. Repeating the parent's OAuth declaration in
-> the child kit doesn't activate OAuth interception. Use a stored API key when
-> the service supports one. Otherwise, an OAuth login performed inside the
-> sandbox stores the real token there.
-
 ## Registry credentials
 
 Registry credentials authenticate to private OCI registries when pulling