Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Docs: "Protected paths in writable roots" omits .aws (protected since 0.159.0)

Open Beginner friendly
#50,098 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
documentation

Research direction

Start with the "Protected paths in writable roots" section of the Agent approvals & security page and compare its list with the rust-v0.160.0 permissions.rs metadata names and the 0.159.0 release notes. Done means the documentation lists <writable_root>/.aws with the same top-level protection semantics as the existing entries, including the permissions-page mention if needed.

Written by the indexing model from the issue text.

Description

CLI documentation sandbox
What is the type of issue?

Documentation is incorrect, Documentation is missing

What is the issue?

Since 0.159.0, .aws under a writable root is protected as read-only by default (release notes: ".aws directories are protected by default under writable roots", #48176). The "Protected paths in writable roots" section of the Agent approvals & security page still lists only .git, the resolved gitdir, .agents, and .codex. The permissions page has no .aws mention either.

Steps to reproduce

  1. Read "Protected paths in writable roots" on the page linked below.
  2. In a Git repository containing a top-level .aws/ directory, run codex sandbox -P :workspace -C <repo> -- sh -c 'echo x > .aws/probe' with codex-cli 0.160.0.

Expected: the documented list matches the shipped default and includes <writable_root>/.aws.

Actual:

  • The page lists .git, the resolved gitdir, .agents, and .codex only.
  • The command in step 2 fails with .aws/probe: Operation not permitted.
  • In the same run, <writable_root>/sub/.aws/ is writable, consistent with top-level-only protection like the other entries.

Evidence

  • Release notes for rust-v0.159.0, Bug Fixes: "Approved commands retain explicit filesystem denials, and .aws directories are protected by default under writable roots. (#48155, #48176)".
  • In codex-rs/protocol/src/permissions.rs at rust-v0.160.0, the protected metadata names include .aws.
  • Environment: codex-cli 0.160.0 on macOS 27.0 arm64; docs fetched 2026-10-01.

Impact: users who read the docs do not know why writes to a project's .aws fail, or that granting them needs an explicit filesystem rule.

Suggested fix: add <writable_root>/.aws to the section with the same semantics as the other entries. This mirrors #25546, which added .agents to the same list.

Where did you find it?
Dominant language
Rust
Stars
129k
Forks
20.3k
Avg merge
1m
Merged PRs (30d)
998

Getting set up

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.