codex - 💡(How to fix) Fix Codex app: support local repo-scoped AGENTS instructions for app-created worktrees [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#21185Fetched 2026-05-06 06:25:16
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Component

Codex app / worktrees / AGENTS.md

Feature Request

Please support repo-scoped local instructions that are private to a developer but automatically available in Codex app-created worktrees.

For example, a repo could have a local-only instructions file such as AGENTS.local.md, or an equivalent app-managed setting, that is loaded alongside AGENTS.md without being committed to git.

Motivation

Some instructions are specific to a repo and a developer’s machine, so they do not belong in committed AGENTS.md, but global Codex instructions are too broad.

Examples:

  • setting KUBECONFIG before running kubectl
  • copying or linking .env into new worktrees
  • local cluster names, VPN notes, private paths, or machine-specific test setup

Today these either have to be committed, repeated manually, placed in global instructions, or handled partially through setup scripts. None of those quite fit repo-specific private instructions.

Expected Behavior

When the Codex app creates a new worktree for a repo, the repo’s local/private instructions should be available automatically in that worktree’s Codex sessions.

extent analysis

TL;DR

Implement a feature to load local, private instructions from a file like AGENTS.local.md or an app-managed setting, alongside the committed AGENTS.md, when creating a new worktree.

Guidance

  • Consider introducing a new configuration option or file format to store private instructions, ensuring they are not committed to the repository.
  • Investigate how to automatically load these private instructions when creating a new worktree, potentially using existing Codex app hooks or callbacks.
  • Evaluate the security implications of storing private instructions locally and ensure they are properly encrypted or access-controlled.
  • Research existing solutions or libraries that manage local, private configuration files to avoid reinventing the wheel.

Example

No code example is provided due to the lack of specific technical details in the issue.

Notes

The implementation details will depend on the specific requirements and constraints of the Codex app and its underlying technology stack. Careful consideration of security and privacy implications is necessary when handling private instructions.

Recommendation

Apply a workaround by introducing a new configuration option or file format to store private instructions, as this approach allows for a more flexible and secure solution.

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 Codex app: support local repo-scoped AGENTS instructions for app-created worktrees [1 participants]