docs: warn about extended-agent OAuth - #25810
Open
dvdksn wants to merge 3 commits into
Open
Conversation
The Claude extension example implied that proxy-managed OAuth works for a third-party child kit. Document the working API-key setup, explain that sbx generates the binding during first-run approval, and warn that the prompt's OAuth option does not activate interception. Co-Authored-By: Claude <noreply@anthropic.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The PR correctly documents that proxy-managed OAuth is not supported for third-party kits that extend built-in agents, and guides users to the API-key setup flow as the working alternative. The added content in both kit-examples.md and credentials.md is accurate, well-scoped, and consistent with the existing document style. No style violations, broken links, or structural issues were found in the changed lines.
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
Two medium findings in the new content. No high-severity or style issues detected.
Tell users to review credential mechanisms individually and decline unsupported OAuth. Clarify the first-run behavior for third-party sandbox agents without removing OAuth binding coverage from the general documentation. Co-Authored-By: Claude <noreply@anthropic.com>
Keep the credential approval flow unchanged and state only that OAuth is ineffective for the extended agent. Restore the general first-run explanation for both API-key and OAuth bindings. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Explain that proxy-managed OAuth does not work for third-party kits that extend built-in agents, and document the working host-stored API-key flow and generated credential-binding approval.
Closes docker/sbx-releases#434
@netlify /ai/sandboxes/customize/kit-examples/
Generated by Codex