sbx: document codex auth prompt before sandbox launch#25315
Conversation
sbx now prompts you to authenticate to Codex on the host before launching the sandbox when no OpenAI credential is stored. Update the Codex agent page and the credentials best practices to describe this flow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| **OAuth**: If you prefer not to use an API key, start the OAuth flow on your | ||
| host with: | ||
| **OAuth**: Start the OAuth flow on your host with: |
There was a problem hiding this comment.
[MEDIUM] Bold lead-in **OAuth**: violates STYLE.md — bold only for UI elements
**OAuth**: uses bold as a section/method label, which STYLE.md explicitly disallows. Bold is reserved for UI elements (buttons, menus, field labels) only. The **Term**: description format is called out as "marketing-style list formatting" that should be avoided.
Consider restructuring without the bold lead-in, for example:
To authenticate using OAuth, run:
```console
$ sbx secret set -g openai --oauth
Or use a sub-heading if the section warrants one.
<!-- cagent-review -->
| in your OS keychain. The OAuth flow runs on the host, not inside the sandbox, | ||
| so browser-based authentication works without any extra setup. | ||
|
|
||
| **API key**: Store your OpenAI API key using |
There was a problem hiding this comment.
[MEDIUM] Bold lead-in **API key**: violates STYLE.md — bold only for UI elements
Same issue as the **OAuth**: lead-in above: **API key**: uses bold as a term label rather than for a UI element. Per STYLE.md, the **Term**: description pattern in lists is disallowed.
Consider plain prose, for example:
To store your OpenAI API key using [stored secrets](../security/credentials.md#stored-secrets), run:
3 participants
Summary
sbxnow prompts you to authenticate to Codex on the host before launching the sandbox when no OpenAI credential is stored. Updated the Codex agent page and the credentials best practices to describe this flow, and reordered the Codex auth methods so OAuth (the host-side prompted flow) leads.Generated by Claude Code