Full access ignored in new chats

“I created a new local chat with Full access selected, but the agent received an explicitly restricted managed filesystem profile.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/18797/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 1 report or thumbs-up in the last 7 days and none the week before, down from 2 a week at the late-October peak.

Full access selection runs chats with workspace-write sandbox. New chats report workspace-write, restricted networking and a managed permission profile, so writes outside the project fail with access denied.

Is this your bug?

File my report

Where: Desktop app
Error text: permission_profile type: managed
Versions: 0.164.0
Platforms: macOS, Windows
How bad: Breaks a normal workflow.

Part of: Full access/network setting not applied3 bugs

Shell network blocked7 people
Network blocked despite setting on6 people

Not quite your bug?

Full access control disappears3 people
Full access permissions not applied3 people

Original reports3, newest first

Oct 24, 2026[Windows Desktop] Selecting "Full access" sends permission_profile: "managed" that is not defined locally, silently falling back to workspace-writeOn GitHub#56663
Oct 21, 2026macOS Desktop 26.1016.51333: new Full access chat receives managed workspace-write permissionsOn GitHub#55922
Oct 17, 2026Full access selected, but local Work execution remains restricted across new chats.On GitHub#54837