[Feature Request][Codex Desktop] Add a “Run” button for executable scripts in the Files view

What variant of Codex are you using?

Codex in the ChatGPT Desktop app (Beta).

What feature would you like to see?

I would like to have the ability to run executable script files directly from the Files view in Codex / ChatGPT Desktop.

Currently, when I open a project and navigate to Files, executable scripts such as .py files can be viewed and opened, but there is no convenient way to run them directly from the file browser.

To execute a script, I currently have to either:

• manually run it through the integrated terminal; or
• open the file/project in an external application such as VS Code and run it from there.

This adds unnecessary friction, especially for small scripts or when testing changes made by Codex.

Suggested implementation

For executable or runnable files, add a Run button next to the existing Open dropdown in the file viewer.

For example:

[ Run ▶ ] [ Open ▼ ]

The same action could also be added to the file context menu:

Right-click file → Run

For a Python file, clicking Run could essentially execute:

python <filename>.py

using the project's configured Python environment/interpreter.

The same concept could later support other executable file types such as .js, .ts, .sh, .ps1, etc.

Execution behavior

Ideally, the Run action should:

• use the project's working directory;
• automatically use the configured interpreter/environment when available;
• show stdout / stderr in the integrated terminal or a dedicated output panel;
• use the same sandbox, permissions, and approval rules that Codex already applies when running commands through the terminal;
• allow the running process to be stopped from the UI.

If multiple interpreters or execution configurations are available, the Run button could have a dropdown similar to:

• Run Python File
• Run in Terminal
• Select Interpreter / Environment

Why this would be useful

Codex Desktop already provides project navigation, file editing, an integrated terminal, and the ability to execute commands.

Adding a direct Run action to runnable files would make the Files view much more useful as a lightweight development environment.

For quick scripts and small projects, this would remove the need to switch to VS Code or manually type the script command into the terminal just to test a file.

It would also make the workflow more intuitive:

Open project → edit with Codex → open file → Run → inspect output → continue editing.

Additional information

No response

The issue does not identify implementation files, tests, or a desktop entry point. Start by locating the Files view and existing terminal command execution, then define supported file types, interpreter selection, output, stopping, and approval behavior; done means a Run action works within the existing execution rules.