Browser and Chrome plugins fail trusted-path validation on Windows after update #39502

Activity

1. Andy-rateria

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Aug 19, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   browser

   on Aug 19, 2026
3. github-actions commented on Aug 19, 2026

   

   github-actionsBot

   on Aug 19, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • [Windows] Browser plugins fail trusted RPC dependency validation #39486
   • Windows regression that completely disables both the built-in Browser and Chrome control. #39414
   • Windows: shared Browser runtime rejects bundled browser-service during trusted RPC validation #39407
   • [Windows] Browser/Chrome plugin fails trusted RPC dependency path validation #39399
   • OpenAI Support Diagnostic: Browser and Chrome Runtime Bootstrap Failure #39252

   Powered by Codex Action
4. xMythicx commented on Aug 31, 2026

   

   xMythicx

   on Aug 31, 2026

   More actions

   @Andy-rateria

   Ok so I believe this issue is perhaps related to project level config profiles when the global .codex/config.toml specifically sets sandbox_mode = "workspace-write". Removing this setting and creating a new task with the permission profile set to "ask for approval' seems to have fixed the RPC error for me, This raises more questions as I am using custom project level configuration profiles. Perhaps I need to move those rules up to global and just use the global config for now. As Open ai docs do state the project level permission are still in beta. Thought to share if others are hitting this wall too. It has impacted my productivity since the Aug 20 release , and thought this detail may help others get passed the blocker.
5. xMythicx commented on Aug 31, 2026

   

   xMythicx

   on Aug 31, 2026

   More actions

   @Andy-rateria , following up, What I have come to find through troubleshooting this RPC error is that it has to do with your permission profile hierarchy and boundaries. Set in your global config and in project-level config. Here is the thing that helped me get past this blocker . If either profile specifically has a setting for "/your-home-dir" = deny , then this supersedes all later configured settings for attempts to access it. Even if you later have a custom subdirectory read permission . Example: "/your-home-dir/subpath" = "read" . That later setting seems to be discarded and the earlier deny is enforced. Yes, it seems odd, so Codex task needs access to your home directory from many processes it runs. How to give it controlled access without allowing it access to personal data? For me, I created a custom profile that extends :workspace, named it :safe-workspace, then white-listed all the custom paths in the home folder that I did not want the threads to access . Then my project-level permission profiles extend that safe workspace. Here is an example from my global ~/.code/config . This lets Codex access its needed directories inside the home folder while securing my personal directories. I have not been successful with any other configuration to restore Chrome or Browser. This also restored an issue I was having when sending messages from mobile and my permission profile was being downgraded. Hope this helps :), this took me weeks to sort, so hoping it’s helpful to others, the down side to this is you must explicitly list every private directory. But I have not found any other way .

   Global config.toml
   ~/your-home-dir/.codex/config.toml
   
   default_permissions = "safe-workspace"
   
   [permissions.safe-workspace]
   description = "Workspace access with selected sensitive personal paths denied."
   extends = ":workspace"
   
   [permissions.safe-workspace.filesystem]
   # Personal folders that are not current project locations
   "~/Desktop" = "deny"
   "~/Downloads" = "deny"
   "~/Movies" = "deny"
   "~/Music" = "deny"
   "~/Pictures" = "deny"
   
   # Sensitive macOS application data
   "~/Library/Accounts" = "deny"
   "~/Library/AddressBook" = "deny"
   "~/Library/Calendars" = "deny"
   "~/Library/Mail" = "deny"
   "~/Library/Messages" = "deny"
   "~/Library/Mobile Documents" = "deny"
   "~/Library/Safari" = "deny"
   
   # Codex authentication material
   "~/.codex/auth.json" = "deny"
   

   Then my project level config , extends this profile

   model = "gpt-5.6-sol"
   model_reasoning_effort = "medium"
   approval_policy = "on-request"
   approvals_reviewer = "user"
   
   [permissions.custom-profile]
   description = "Coordinate registered repositories while sensitive personal paths remain denied."
   extends = "safe-workspace"
   
   [permissions.custom-profile.filesystem]
   Redacted system file paths
   
   [permissions.custom-profile.workspace_roots]
   "path-to-project" = true
   
   [permissions.custom-profile.network]
   enabled = true
   
   [permissions.custom-profile.network.domains]
   "github.com" = "allow"
   "api.github.com" = "allow"
   "objects.githubusercontent.com" = "allow"
   "raw.githubusercontent.com" = "allow"
   "codeload.github.com" = "allow"
   "chatgpt.com" = "allow"
   
   [agents]
   max_concurrent_threads_per_session = 5