Support project-level skills discovery from repository workspace

Open 💬 1 comment Opened May 9, 2026 by urolzeen

What variant of Codex are you using?

App, IDE Extension, CLI

What feature would you like to see?

Codex currently discovers skills mainly from user-level ~/.codex/skills, but project-specific skills are not automatically loaded from the repository workspace.

This makes team workflows fragile:

  • Skills are easy to miss after reinstalling the OS or switching machines.
  • Project-specific AI workflows cannot travel with the repo.
  • Different developers may have different local skills installed.
  • AGENTS.md and project rules are workspace-aware, but skills are not, which feels inconsistent.

Expected behavior:

  • Codex should automatically discover workspace-level skills from a conventional repo path such as:
  • <repo>/.codex/skills/<skill-name>/SKILL.md
  • or <repo>/.agent/skills/<skill-name>/SKILL.md
  • The available skills list should show where each skill comes from:
  • system
  • user
  • workspace/project
  • plugin

Security:

  • Since project-level skills come from the repository, Codex could require a one-time workspace trust confirmation before loading them, similar to VS Code Workspace Trust.
  • If two skills have the same name, Codex should define a clear precedence rule or report the conflict explicitly.

Why this matters:
This would make Codex much easier to use in team repositories and portable development environments. Project-specific AI workflows could be versioned together with the codebase instead of requiring every developer to manually copy skills into ~/.codex/skills.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗