openai / openai/codex

Add a global "Disable local execution by default" setting for personal accounts

Open
#46,256 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement sandbox
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App

What feature would you like to see?

I'd like a global setting for personal accounts that disables local execution by default.

Currently, a normal prompt in the Codex/ChatGPT app can result in a task being executed locally, even when I did not explicitly ask Codex to access or modify anything on my computer.

I still want local execution to be available when I explicitly choose it. However, there should be an option such as:

Local execution: Explicit opt-in only

With this enabled:

  • Normal prompts must never start local execution automatically.
  • Local files, repositories, commands, or other resources on my computer must not be accessed unless I explicitly select/authorize local execution for that task.
  • Local execution should remain available as an explicit per-task choice.
  • Cloud execution should be the default.

Ideally this setting would apply consistently to both Codex Local and Work Local where applicable.

The important distinction is: I do not want to disable local functionality entirely. I want local access to require an explicit action from me each time, rather than being inferred from the prompt or current context.

Additional information

Related: #41926 requests an explicit Local vs. Cloud choice when starting Work, while #33475 requests clearer visibility of the currently active execution mode.

Those would address parts of this problem. This request goes one step further: I'd like a persistent account-level setting that makes Cloud the default and requires explicit opt-in before any task is allowed to run locally.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing related issues #41926 and #33475, then locate the account settings and local-versus-cloud execution flow in the Codex app. Done means personal accounts can persistently default to Cloud, local resources are not accessed without explicit per-task authorization, and local execution remains available as an explicit choice.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.