Repository-scoped marketplace and plugin configuration in project config

[yshrsmz]

What variant of Codex are you using?

Codex CLI

What feature would you like to see?

Codex supports project config via ./.codex/config.toml, but plugin-related config is still effectively user-scoped.

A repo can provide a local marketplace via ./.agents/plugins/marketplace.json, but it cannot declare:

• remote marketplaces that should be available for that repo
• plugin enable/disable settings that should apply for that repo

This makes team-wide plugin setup hard to share and hard to reproduce across machines.

Request

Please add repo-scoped support for:

• marketplace registration
• plugin enable/disable settings

Ideally this should work through ./.codex/config.toml or an equivalent repo-local config mechanism, so teams can commit their Codex plugin setup to the repository.

Example:

[marketplaces.my_team]
source = "github.com/my-org/my-codex-marketplace"

[plugins."review-tools@my_team"]
enabled = true

Why this matters

Today, marketplace registrations and plugin states are effectively read from user config, so each developer must configure Codex manually.

Repo-scoped plugin config would improve:

• onboarding
• reproducibility across machines
• team-shared tooling
• multi-repo plugin development and consumption

Additional information

No response