README: Enterprise section covers the requirements.toml managed-hook rollout - #3
Merged
Conversation
…ok rollout, not just the MCP allowlist
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Enterprise section said admins could allowlist ACP's MCP server via
requirements.toml. That undersold it:requirements.tomlcan carry the hook itself as a managedPreToolUse/PostToolUsehook users can't remove, delivered from a system file, an MDM profile, or the ChatGPT Enterprise workspace's managed configuration.Rewrites the section to say that, names the
ACP_REQUIRE_ENROLLMENT=1wrapper variable (agentic-control-plane/claude-code-acp-plugin#23) and the per-person enrollment step, and links the full recipe at agenticcontrolplane.com/docs/enterprise/codex (marketing PR pending).Scoped in davidcrowe/gatewaystack-connect#943.