ChatGPT Workspaces Can Sync GitHub Plugin Marketplaces Daily
ChatGPT workspace admins and owners can now import plugin marketplaces from public or private GitHub repositories and keep them synchronized automatically. The feature gives teams a central way to distribute Codex and Claude-compatible plugins while keeping installation policies and app permissions under workspace control.
ChatGPT workspaces can now import a plugin marketplace from a public or private GitHub repository and keep it synchronized automatically. OpenAI Developers amplified the workspace feature in an approved-source post on August 29, describing support for ChatGPT Business and Enterprise and daily updates from the repository. (OpenAI Developers on X)
The durable documentation describes the feature as a team-distribution workflow: an administrator imports a JSON marketplace catalog, reviews the imported plugins, and lets ChatGPT check the source each day for additions and updates. An admin can also request a manual sync without waiting for the daily pass. (OpenAI plugin management documentation; ChatGPT Business release notes)
Key Takeaways
- Central GitHub source: Admins can import a marketplace from a public or private GitHub repository.
- Daily updates: New marketplaces have automatic daily synchronization enabled.
- Manual refresh: Admins can choose Sync now when a repository change should be picked up sooner.
- Workspace governance stays separate: Importing a marketplace does not connect a member's app account or grant app access.
- Plugin formats: A marketplace is a JSON catalog and can reference supported Codex, Claude-compatible, Agent Plugins 1.0, and skill packages.
- Safe failure behavior: If an existing plugin update is invalid, the last working version remains in place while the report records the error.
What the GitHub Connection Adds
Teams often keep reusable agent workflows in a repository: a marketplace file lists the plugins, and each entry points to the package that should be installed. The new workspace flow turns that repository into a governed distribution source instead of requiring an administrator to import each plugin by hand.
OpenAI's plugin-management documentation says the authorizing GitHub account must be able to read the marketplace repository and any other repositories referenced by its entries. Public and private repositories are supported, but an organization's GitHub approval may be required before the import can read a private repository. (OpenAI plugin management documentation)
This is a source-management feature, not an automatic permission grant. New plugins start with Available installation and authentication on install, and admins can then set the installation policy and required apps for each plugin. Importing the marketplace does not connect members' accounts to those apps. (OpenAI plugin management documentation; ChatGPT Business release notes)
How an Admin Sets Up a Marketplace
The labels can vary slightly by workspace surface, but the documented flow is:
- Open the workspace's Admin or Workspace settings area and go to Plugins.
- Select Add and choose Import marketplace.
- Enter the GitHub repository URL. Use the repository URL, not a URL that includes a branch or marketplace filename.
- If the marketplace lives below the repository root, enter its directory in Path.
- Optionally choose a branch, tag, or commit. A branch follows future commits; a fixed commit stays pinned to that revision.
- Select Import marketplace, authorize GitHub when prompted, and review the import results.
- Open each imported plugin to configure its installation policy, roles, required apps, and any other workspace controls.
The initial import can take longer for a very large marketplace. Subsequent daily syncs typically take a few minutes, according to the developer documentation. (OpenAI plugin management documentation)
Daily Sync and “Sync Now”
New marketplaces have automatic daily sync enabled. A sync can add new marketplace entries and update existing plugins, so repository changes become workspace changes on the next successful pass. The administrator should review repository changes before merging because a future sync can import new plugins from the source. (OpenAI plugin management documentation)
When a change needs to arrive sooner, open Admin > Plugins > Marketplaces, select the marketplace, and choose Sync now. The Business release notes describe the equivalent path as Workspace settings > Plugins, then opening the marketplace and selecting Sync now. (OpenAI plugin management documentation; ChatGPT Business release notes)
Sync is designed to fail conservatively. If an existing plugin's new definition is invalid, the last working version is retained and the report records the error. Fix the repository, then request another sync. Removing an entry from the repository does not delete the imported workspace copy; it is marked No longer in source instead. (OpenAI plugin management documentation)
What Workspace Owners Still Control
The GitHub repository supplies the catalog and package references, but workspace governance remains in ChatGPT. Admins configure whether a plugin is available or installed for eligible roles, enable required apps, and manage the related access controls. Syncing a repository does not override those workspace policies. (OpenAI plugin management documentation)
That separation matters for teams with different risk levels. A repository can be the reviewable source of truth for plugin versions, while the workspace decides who can install a plugin, whether it is installed by default, and which connected services are enabled. Members still need access to the connected service, and importing the catalog alone does not provide it. (ChatGPT Business release notes)
When This Is Useful
Standardize a team toolkit
Keep a shared marketplace in a repository and use it to distribute the same set of plugins to a Business or Enterprise workspace. Review changes through the normal repository process before they reach the workspace.
Ship plugin updates without repeated imports
Use a branch or the repository's default branch when the team wants future commits to flow into the workspace. Daily sync handles routine updates; Sync now is available for an urgent, reviewed change.
Separate distribution from permissions
Import a catalog centrally, then give each plugin its own installation policy and required-app configuration. This lets an admin distribute a package without silently authorizing every service it references.
The result is a more maintainable bridge between the repository where agent tooling is reviewed and the workspace where teammates discover and run it. It is especially relevant for teams building shared Codex or Claude-compatible workflows, because the marketplace can be updated centrally while workspace access remains explicit.
Read next
Keep building the workspace playbookCodex for Every Role: Role-Specific Plugins, Codex Sites, and Annotations Beyond Code
OpenAI is pushing Codex past software development with three releases: six role-specific plugins bundling 62 apps and 110 skills, Codex Sites that turn analysis into shareable hosted web apps in preview for business and enterprise, and annotations that now refine documents, spreadsheets, and presentations -- not just code and websites.
OpenAI Resets ChatGPT Work And Codex Limits For Paid Users
OpenAI executive Tibo announced usage resets for paid ChatGPT Work and Codex users on August 8 and August 29, 2026, then said the five-hour limit would return for Plus accounts across both products on August 26. The approved posts do not publish a numeric allowance, a new API billing rule, or details beyond that plan and product scope.
Codex Permission Profiles: Least-Privilege Controls for Local Agent Work
OpenAI shipped Codex permission profiles in beta -- reusable, inheritable policies that replace the coarse sandbox_mode/sandbox_workspace_write combo. A profile binds OS-enforced filesystem read/write/deny rules (down to **/*.env) to per-domain network and Unix-socket rules. Enterprise admins get fail-closed allowlists via requirements.toml. Profiles govern local sandboxed command execution only, not MCP servers, app connectors, browser, or cloud.
Frequently Asked Questions
What changed for ChatGPT workspaces?
Workspace admins and owners can import a plugin marketplace from a public or private GitHub repository and keep it up to date with automatic daily synchronization. The marketplace is a JSON catalog that lists the plugins a team wants to distribute.
Where do admins configure a GitHub marketplace?
Open the workspace plugin-management area, choose Add, and select Import marketplace. Enter the GitHub repository URL, optionally provide a subdirectory and branch, tag, or commit, then authorize GitHub and review the import results.
How often does the marketplace update?
New marketplaces have automatic daily sync enabled. An admin can also open the marketplace in the workspace plugin settings and choose Sync now to request an update before the next scheduled pass.
Does importing a marketplace grant app access to members?
No. Importing a marketplace does not connect members' accounts or grant access to the apps a plugin uses. Admins still configure installation policies, required apps, roles, and permissions for each plugin.
What happens if a plugin update is invalid?
The sync report identifies errors. If an update to an existing plugin is invalid, OpenAI says the last working version is retained; the admin can fix the repository and request another sync.