codex - 💡(How to fix) Fix Allow per-session sandbox override for local VM and benchmark [2 comments, 2 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#19322Fetched 2026-04-25 06:11:45
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1unlabeled ×1

Root Cause

Codex can edit and build code in my local workspace, but in some cases it cannot run the actual benchmark because the session sandbox blocks required host-side operations.

RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

I have encountered several issues when using Codex for I/O benchmarking involving QEMU/KVM.

Codex can edit and build code in my local workspace, but in some cases it cannot run the actual benchmark because the session sandbox blocks required host-side operations.

A concrete example is virtio-fs benchmarking with QEMU + virtiofsd. The workflow works from my normal shell, but Codex cannot complete it because the sandbox blocks the local socket/IPC setup needed by virtiofsd.

This makes systems and performance work harder than it needs to be. Codex can prepare the code and scripts, but I still have to run them manually and send the results back.

Requested improvement:

  • allow an explicit per-session sandbox override
  • make it opt-in and clearly visible
  • ideally support local VM/socket/process-heavy workflows without requiring a separate environment

Thanks for your concern.

Additional information

No response

extent analysis

TL;DR

Allowing an explicit per-session sandbox override in Codex may resolve the issue with blocked host-side operations during I/O benchmarking with QEMU/KVM.

Guidance

  • Investigate the current sandbox configuration in Codex to understand the specific restrictions causing the issue.
  • Consider the security implications of allowing a per-session sandbox override and weigh the benefits against potential risks.
  • If an override is feasible, design an opt-in mechanism with clear visibility to ensure users understand the implications of bypassing sandbox restrictions.
  • Explore alternative solutions, such as integrating QEMU/KVM support directly into Codex or using a separate environment for benchmarking, as a temporary workaround.

Notes

The requested improvement requires careful consideration of security trade-offs and potential implementation complexities.

Recommendation

Apply a workaround, such as using a separate environment for benchmarking, until a more integrated solution can be developed, to minimize the impact on systems and performance work.

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 Allow per-session sandbox override for local VM and benchmark [2 comments, 2 participants]