codex - 💡(How to fix) Fix Profile repo-only still allows reading outside the repo / injecting workspace-write

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…
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

v0.132.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.5.0 arm64

What issue are you seeing?

/status reports:

text Permissions: Profile repo-only (workspace with network access, on-request)

I expected this to restrict filesystem reads to the current repository unless explicit approval was granted.

However, during the session, Codex was still able to read outside the repo and list my home directory contents without requesting approval.

Current repo:

text ~/repos/codex/bridge

Example interaction:

text › What is in my home directory? • Your home directory contains: Applications Desktop Documents Downloads Library Movies Music Pictures repos ...

This appears inconsistent with the meaning of Profile repo-only.

What steps can reproduce the bug?

  1. Start Codex in a repository.
  2. Confirm /status shows: text Permissions: Profile repo-only (workspace with network access, on-request)
  3. Ask Codex to inspect or list files outside the repo, e.g.: text ls ~
    or: text What is in my home directory?
  4. Codex reads/list files outside the repository without requesting approval.

What is the expected behavior?

Under Profile repo-only, filesystem reads outside the current repository should either:

  • be blocked, or
  • require explicit approval before access

The current behavior makes the scope of “repo-only” unclear.

I searched the repo-local config and did not find any explicit workspace-write, sandbox_mode, or related overrides in:

  • AGENTS.md
  • .agents/
  • .codex/config.toml
  • top-level config.toml

So this behavior appears to come from the active Codex permission profile/runtime rather than repository configuration.

Additional information

No response

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 Profile repo-only still allows reading outside the repo / injecting workspace-write