Cursor 3.9 Ships a Unified Customize Page
On 22 June 2026, Cursor released version 3.9, the most substantial Customize-layer update in the Cursor 3.x series. The centrepiece is a new Customize tab that consolidates every extension point in a Cursor workspace — plugins, skills, MCP servers, subagents, rules, commands, and hooks — into a single management interface. Before 3.9, configuring a Cursor environment involved visiting multiple parts of the settings interface to add each category of extension separately, and keeping team configurations consistent across developers was a documentation and onboarding problem rather than a platform feature. The Customize page makes consistent team configuration a first-class product capability rather than a process teams enforce manually.
One Tab for Plugins, MCPs, Subagents and Hooks
The Customize tab manages extensions at three scopes: user, team, and workspace. User-level configuration applies to all of a developer's workspaces. Team-level configuration applies to all members of a team and is controlled by team administrators. Workspace-level configuration applies only within a specific project directory and takes precedence over user and team settings for that project context.
The three-level scoping model addresses a real operational problem for teams managing multiple client projects with different compliance or security requirements. A team can set approved MCP server lists and compliance hooks at the team scope, ensuring that every developer's environment meets baseline requirements without relying on each developer to remember setup steps. Individual projects with specific data infrastructure requirements can define workspace-level configurations that override the team baseline within that directory. New developers joining a team inherit the correct configuration automatically rather than following a setup guide that may be outdated.
Marketplace Leaderboard and Plugin Canvases
Two companion features ship alongside the Customize page. The marketplace leaderboard shows which plugins, skills, and MCP servers are most actively used across the team — a usage signal that helps developers discover extensions that are genuinely improving team productivity rather than evaluating a large catalogue with no performance data. Any extension visible in the leaderboard can be added to a developer's Customize setup with a single click.
Plugin canvases are prebuilt layout templates that ship with specific plugins. Cursor 3.9 launches with two: the Hex Canvas, which provides a preconfigured environment for data visualisation work, and the Atlassian Canvas, which gives teams a realtime view of active Jira issues, Confluence documents, and project status within the Cursor window. For teams that lose time context-switching between their editor and project management tools, the Atlassian Canvas reduces a persistent source of workflow interruption. Team workspaces can distribute canvases through the team marketplace, giving teams shared layout templates they can open and reuse across projects.
Team Marketplace Expands to GitLab, Bitbucket and Azure DevOps
Team marketplace support in earlier Cursor releases required plugin and extension repositories to be hosted on GitHub. Cursor 3.9 adds GitLab, Bitbucket, and Azure DevOps as supported import sources for team marketplace content. Engineering teams whose code infrastructure lives on GitLab or Azure DevOps can now build and distribute private Cursor plugins to their team without maintaining a separate GitHub repository solely for Cursor tooling.
Cloud subagent execution also improves meaningfully in 3.9. A cloud subagent can now run in the background without blocking the parent agent session — developers can dispatch a subagent to handle a time-consuming task such as running a full test suite, migrating a database schema, or processing a large log file, and continue working in the primary session while the background agent runs. Session mobility improves as well: agent sessions can be moved more reliably between a local machine and a cloud environment mid-task, reducing the dependency on a single machine remaining online for a long-running task to complete. Cursor removes the previous cap on parallel cloud agent instances, allowing teams to run as many background agents simultaneously as their account tier permits.
What Indian Engineering Teams Can Do With These Features
For Indian software product companies and IT services firms that have deployed Cursor at team or enterprise scale, the Customize page's three-level scoping model addresses a concrete operational gap. Platform teams can enforce approved MCP server lists and compliance hooks at the team scope, reducing the risk of developers connecting unsanctioned data sources in regulated client engagements. Individual projects can define workspace-level configurations without affecting other team members' environments or other client projects.
Azure DevOps team marketplace support is particularly significant for Indian IT services firms whose enterprise clients operate on the Microsoft stack — a common configuration in large Indian IT services accounts. Building and distributing client-specific Cursor plugins via an Azure DevOps-backed team marketplace is now a supported first-class workflow rather than a workaround requiring a parallel GitHub repository. The cloud background agent capability also changes the economics of long-running agentic tasks: work that previously occupied a developer's local machine — and blocked interactive use during execution — can be offloaded to cloud agents running in parallel, improving throughput on high-volume codebases.
The Bottom Line
Cursor 3.9, released 22 June 2026, ships a Customize page that unifies plugins, skills, MCP servers, subagents, rules, commands, and hooks into a single, three-level-scoped management interface operating at user, team, and workspace levels. The marketplace leaderboard surfaces the most-used team extensions with one-click adoption; plugin canvases ship prebuilt layout templates for data visualisation (Hex Canvas) and Atlassian project tracking; team marketplace support extends to GitLab, Bitbucket, and Azure DevOps; and cloud subagents can now execute in the background without blocking the parent session, with no cap on parallel cloud instances. For Indian engineering teams managing Cursor at scale across multiple projects and client accounts, 3.9 is the first release that provides a coherent, scalable answer to environment configuration and governance.
Frequently Asked Questions
What is the Cursor 3.9 Customize page and what does it manage?+
Released on 22 June 2026, the Cursor 3.9 Customize page is a unified management interface that consolidates every extension point in a Cursor workspace — plugins, skills, MCP servers, subagents, rules, commands, and hooks — into a single tab. Configuration can be scoped at three levels: user (applies to all workspaces), team (applies to all team members, controlled by administrators), and workspace (applies only within a specific project directory, taking precedence over user and team settings). This eliminates the need to visit multiple settings surfaces and ensures new team members inherit the correct configuration automatically.
What are the Cursor 3.9 Plugin Canvases and the Marketplace Leaderboard?+
Plugin canvases are prebuilt layout templates that ship with specific plugins. Cursor 3.9 launches with two: the Hex Canvas for data visualisation work, and the Atlassian Canvas for a realtime view of Jira issues, Confluence documents, and project status within the editor. The Marketplace Leaderboard shows which plugins, skills, and MCP servers are most actively used across the team, providing a usage-based signal for extension discovery. Any leaderboard entry can be added to a developer's Customize setup with a single click, and teams can distribute canvases through the team marketplace for shared reuse.
Which Git platforms now support Cursor team marketplaces in version 3.9?+
Cursor 3.9 expands team marketplace support beyond GitHub to include GitLab, Bitbucket, and Azure DevOps as plugin and extension repository sources. Previously, teams whose code infrastructure ran on GitLab or Azure DevOps had to maintain a separate GitHub repository to distribute Cursor plugins. With 3.9, teams can import plugin repositories directly from their existing Git platform, build private Cursor extensions, and distribute them to team members without any cross-platform workaround.
How do cloud subagents change in Cursor 3.9?+
In Cursor 3.9, cloud subagents can run in the background without blocking the parent agent session — a developer can dispatch a subagent to handle a long-running task such as running a test suite or migrating a schema, and continue working in the primary session while the background agent runs. Session mobility also improves: agent sessions can be moved more reliably between local machines and cloud environments mid-task. Cursor removes the previous cap on parallel cloud agent instances, allowing teams to run as many background agents simultaneously as their account tier permits.
Written by
TechPillow Team
Sharing insights on technology, product development, and the Indian tech ecosystem.