codex - 💡(How to fix) Fix Repository-scoped marketplace and plugin configuration in project config [1 participants]

TL;DR

To address the issue, consider adding support for repo-scoped plugin configuration through ./.codex/config.toml to manage marketplace registrations and plugin enable/disable settings.

Guidance

• Review the current implementation of ./.codex/config.toml to understand how project config is handled and identify potential areas for extension to support plugin-related config.
• Investigate the feasibility of adding a new section to ./.codex/config.toml for marketplace registration and plugin settings, similar to the proposed example.
• Consider the potential impact on existing user-scoped configurations and how to handle conflicts or overrides between user and repo-scoped settings.
• Evaluate the need for additional tooling or scripts to manage and synchronize plugin configurations across teams and repositories.

Example

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

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

This example illustrates the proposed syntax for declaring marketplace registrations and plugin settings in ./.codex/config.toml.

Notes

The implementation details and potential challenges of adding repo-scoped plugin configuration are not fully specified in the issue, so further investigation and discussion may be necessary to determine the best approach.

Recommendation

Apply workaround: Implement a custom solution using the proposed ./.codex/config.toml syntax to manage marketplace registrations and plugin settings at the repository level, as this would improve onboarding, reproducibility, and team-shared tooling.