codex - 💡(How to fix) Fix Multiple start-as user support for windows [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21195Fetched 2026-05-06 06:25:05
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App

What feature would you like to see?

We want the possibility to run codex as a specific windows-user where we on a AD / user-level have restrictions of what codex is allowed to do and not to do. So we can run codex without restrictions within the app, and be sure that it does not have the possibility to by mistake to breaking changes to machine running it.

We've kind of gotten this to work by wrapping the start process with a command, but one problem we run into is that the built in buttons to for example start vscode or similar also always use that user. And I would like the possibility to say

  1. Possibility to choose what user codex-app should start vscode and similar with
  2. Possibility to Start Codex-App with user x, to be able to restrict on a AD-permission level what it can do.

Additional information

This is so we pretty much have the environment sandboxed, without having to trust codex to not being able to do stuff, and have possibility to run it on local machine

extent analysis

TL;DR

Run Codex as a specific Windows user with restricted permissions to prevent unintended changes to the machine.

Guidance

  • Investigate using Windows built-in features such as RunAs to launch Codex and associated applications (e.g., VSCode) with a specific user account.
  • Consider modifying the Codex app to accept a configurable user parameter for launching external applications, allowing for more fine-grained control over user permissions.
  • Explore Active Directory (AD) permission settings to restrict the actions that Codex can perform on the machine, even when running within the app.
  • Evaluate the feasibility of sandboxing the Codex environment to prevent any potential security risks.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The solution may require coordination with system administrators to configure AD permissions and Windows user settings. Additionally, the feasibility of implementing these changes may depend on the specific Codex variant and version being used.

Recommendation

Apply a workaround by using Windows built-in features (e.g., RunAs) to launch Codex and associated applications with a specific user account, as this approach can provide an immediate solution to the problem while a more permanent fix is being developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Multiple start-as user support for windows [1 participants]