Skip to content

Commit 1c54c1b

Browse files
committed
docs: clarify ChatGPT full access behavior
ChatGPT remote chats can continue requesting approvals even when Full access appears selected after reconnecting. Document how to select the mode, restart an affected task, and identify the upstream permission synchronization issue.
1 parent 2712b53 commit 1c54c1b

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

  • content/manuals/ai/sandboxes/integrations

content/manuals/ai/sandboxes/integrations/chatgpt.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,19 @@ remote project.
4848
For more connection options, see the OpenAI instructions to
4949
[connect to an SSH host](https://learn.chatgpt.com/docs/remote-connections#connect-to-an-ssh-host).
5050

51+
## Full access still prompts for approval
52+
53+
ChatGPT controls Codex permissions separately from the Docker Sandbox. To run
54+
commands without Codex approval prompts, select **Full access** from the
55+
permissions menu for the remote chat. Enabling **Full access** under
56+
**Settings > General** only adds the mode to the permissions menu. It doesn't
57+
change an existing chat.
58+
59+
If the chat continues to request approval while showing **Full access**, update
60+
the ChatGPT desktop app, then stop and restart the active task. Approval prompts
61+
that return after reconnecting can indicate a
62+
[Codex remote-permission synchronization issue](https://github.com/openai/codex/issues/29054).
63+
5164
## Related
5265

5366
- [Editor and app integrations](_index.md) — how SSH access works and how to

0 commit comments

Comments
 (0)