From c494ad93df63d1e2f3df6f1701a02e27d6d0f402 Mon Sep 17 00:00:00 2001 From: Codeman maintainer Date: Fri, 6 Nov 2026 08:23:43 +0100 Subject: [PATCH] fix: name codexConfig.networkAccess in the API reference (release review) The field had no mention. It opens the sandbox's network and does not touch codex's approvals, so it sits beside the sentence about them. Co-Authored-By: Claude Opus 5.5 --- docs/api-reference.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/api-reference.md b/docs/api-reference.md index 84c048e7..f484247c 100644 --- a/docs/api-reference.md +++ b/docs/api-reference.md @@ -287,7 +287,8 @@ long turn, but a worker that never comes back is far more likely to be working t blocked, and polling `blocked` alone will sit at its timeout. **`blocked` on `codex` is read off the screen**, because codex has no hooks and is -launched with its approvals on unless `codexConfig.dangerouslyBypassApprovals` is set. +launched with its approvals on unless `codexConfig.dangerouslyBypassApprovals` is set +(`codexConfig.networkAccess` opens the sandbox's network and does not change that). A codex pane showing a command, edit or network approval, a question (`request_user_input`) or the startup trust prompt raises `blocked` (plus the red alert, push and webhook a Claude `permission_prompt` raises, alert-only: answer it in the terminal), and the session reads