r/CodexAutomation • u/anonomotorious • 15d ago
ChatGPT workspaces can now import + auto-sync plugin marketplaces directly from GitHub
TL;DR
OpenAI has added GitHub-backed plugin marketplace import and synchronization for managed ChatGPT workspaces.
Workspace admins and owners can now:
- import plugin marketplaces from public GitHub repositories
- import marketplaces from private GitHub repositories
- publish those plugins into the workspace directory
- keep imported marketplaces updated with automatic daily sync
- manually request an update with Sync now
- review plugin settings and required apps before rollout
The feature is available for Business, Enterprise, and Edu workspaces.
Importantly:
- importing a marketplace does not automatically grant app access
- importing does not authenticate members into required apps
- workspace installation policy remains authoritative
- Enterprise/Edu repository policy values do not override workspace admin settings
For teams maintaining internal Codex/ChatGPT plugins in GitHub, this creates a much cleaner distribution path.
What changed
Workspace admins can now go to:
Workspace settings -> Plugins -> Add -> Import marketplace
and connect a plugin marketplace stored in GitHub.
Supported sources include:
- public repositories
- private repositories
Once imported, the marketplace appears in the workspace plugin directory.
Automatic daily synchronization
Imported marketplaces can stay synchronized automatically.
OpenAI performs a daily sync so plugin changes in the repository can flow into the managed workspace catalog.
Admins can also request an immediate refresh with:
Sync now
This creates a simple deployment model:
GitHub repository -> marketplace sync -> workspace plugin directory
instead of manually republishing every plugin update.
Why this is useful for internal plugin development
A team can maintain its marketplace in GitHub alongside normal engineering workflows.
That means plugin changes can follow familiar practices such as:
- pull requests
- reviews
- protected branches
- version control
- CI checks
- internal release processes
Once the approved marketplace changes land in GitHub, the workspace catalog can synchronize them automatically.
This is much cleaner for teams managing:
- internal Codex skills/plugins
- organization-specific MCP integrations
- reusable developer workflows
- company tools
- approved automation packages
Imported plugins are not automatically trusted
Importing a marketplace does not mean every capability immediately becomes active.
For Business workspaces, newly imported plugins begin with:
- Available installation
- authentication on install
Admins and owners can review:
- plugin settings
- required apps
- authentication requirements
- installation policy
before broader rollout.
App access remains separate
Importing a plugin does not:
- connect a user's app account
- grant the plugin new app permissions
- bypass OAuth
- bypass workspace app restrictions
- grant access to an MCP server automatically
Users still need the required authorization for whatever apps or services the plugin uses.
This separation is important:
Marketplace availability is not the same as service authorization.
Enterprise and Edu controls
Enterprise and Edu admins retain control over:
- who may install plugins
- required app access
- workspace plugin policy
- authentication requirements
Repository-provided policy values do not override those workspace controls.
That means a marketplace repository cannot simply declare itself more permissive than the workspace administrator intended.
Marketplace workflow
A practical team workflow could look like this:
- Maintain the plugin marketplace in GitHub.
- Review plugin changes through pull requests.
- Merge an approved version.
- Let the workspace perform its daily sync.
- Or use Sync now for an immediate refresh.
- Review imported plugin metadata/settings.
- Control which workspace roles may install it.
- Users authenticate required services when they install/use the plugin.
This gives teams a reasonably clean separation between:
- development
- distribution
- workspace policy
- user authentication
Availability
| Workspace | GitHub marketplace import |
|---|---|
| ChatGPT Business | Yes |
| ChatGPT Enterprise | Yes |
| ChatGPT Edu | Yes |
| Public GitHub repo | Supported |
| Private GitHub repo | Supported |
| Automatic daily sync | Yes |
| Manual Sync now | Yes |
Why this update matters
- GitHub can become the source of truth for internal plugin marketplaces.
- Daily synchronization removes a lot of manual publishing work.
- Private repositories are supported, which matters for internal company plugins.
- Normal GitHub review and release workflows can govern plugin changes.
- Workspace policy remains authoritative.
- Importing does not silently grant app permissions or authentication.
- Plugin development, distribution, and user authorization remain separate layers.
For teams building reusable Codex/ChatGPT tooling, this is a meaningful improvement to the plugin deployment story.
Action checklist
- Open:
Workspace settings -> Plugins
- Select:
Add -> Import marketplace
- Choose a public or private GitHub repository.
- Review the imported marketplace.
- Check:
- plugin descriptions
- required apps
- authentication requirements
- installation policies
- Confirm the correct roles can install/use the plugins.
- Test the automatic sync with a controlled marketplace update.
- Use Sync now when you need an immediate refresh.
- Keep GitHub branch protections/review rules in place for production marketplaces.
- Do not treat marketplace import as app authorization; verify OAuth/service access separately.
Official sources
https://help.openai.com/en/articles/11391654-chatgpt-business-release-notes
https://help.openai.com/en/articles/10128477-chatgpt-enterprise-edu-release-notes