GitHub Adds Enterprise Managed Settings to Copilot for JetBrains

GitHub has added enterprise managed settings to GitHub Copilot for JetBrains, giving administrators centralized control over how the plugin operates across an organization's developer base.

The update, announced on GitHub's changelog on August 18, 2026, allows enterprise admins to apply consistent policy controls across four areas: plugin governance, MCP (Model Context Protocol) server access, OpenTelemetry configuration, and permission modes. According to GitHub, these controls apply uniformly to everyone within an enterprise, removing the need for individual developers to configure these settings on a per-machine basis.

Plugin governance controls let administrators manage which versions or configurations of the Copilot plugin are permitted within JetBrains IDEs. MCP server access settings determine which Model Context Protocol servers developers can connect to from within Copilot, a control point that matters as MCP has become a common mechanism for connecting AI coding assistants to external tools and data sources. OpenTelemetry settings give enterprises visibility into Copilot usage and performance through standardized observability data. Permission modes govern what actions the Copilot agent is allowed to take autonomously within a developer's environment.

GitHub did not disclose specific pricing changes associated with this feature, and the change applies to enterprise-tier Copilot customers using JetBrains IDEs such as IntelliJ IDEA, PyCharm, and WebStorm.

This release follows a broader pattern of GitHub extending enterprise governance features that originally shipped for Copilot in VS Code or as general policy controls, now bringing parity to the JetBrains plugin. As AI coding agents gain more autonomy to execute commands, modify files, and connect to external MCP servers, enterprises have pushed for administrative guardrails that prevent ungoverned use of these capabilities across large engineering organizations.

What this means

This is not a new model or a new capability for Copilot's underlying AI—it's an administrative control layer. For enterprises running JetBrains IDEs at scale, the update addresses a real governance gap: previously, permission modes and MCP server access in JetBrains may have lacked the same centralized enforcement available elsewhere. The practical effect is that IT and security teams can now lock down what Copilot's agent is permitted to do—and which external servers it can reach—without relying on individual developers to configure it correctly. It signals that GitHub views MCP server access and agent permission modes as security-relevant surface area requiring policy enforcement, not just developer preference, as AI coding tools take on more autonomous, file-modifying, and network-connected behavior inside IDEs.