Codex sandbox with network policy silently does nothing unless `feature.network_proxy` is enabled

Open
#33,351 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli, networking, security

Research direction

Start by tracing how new permission profiles handle network policies and the feature.network_proxy setting. Reproduce the configuration described in the issue, then verify that configured policies either activate the proxy or produce a validation error.

Written by the indexing model from the issue text.

Description

bug CLI config connectivity sandbox
What issue are you seeing?

After configuring network permissions, I noticed they were not active.

What steps can reproduce the bug?

Configure network restrictions in new permission profile.
Do not set features.network_proxy to true.
Let codex access the restricted network domain.

What is the expected behavior?

If network-policies are configured, this should imply activation of the network proxy.
If this is not possible to auto-activate, then at least a validation error should be thrown.

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.