Repo sync

config/moda/deployment.yaml

@@ -12,8 +12,6 @@ environments:
 
   # 15 staging environments, evergreens only
   # they should all contain the same configs
-  # intentionally pinned to a single cluster via the `name` selector
-
   - name: staging-balsam
     require_pipeline: false
     notify_still_locked: true # Notify last person to lock this after an hour
@@ -24,7 +22,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':balsam: Review at https://docs-internal-staging-balsam.githubapp.com/'
 
   - name: staging-boxwood
@@ -37,7 +34,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':boxwood: Review at https://docs-internal-staging-boxwood.githubapp.com/'
 
   - name: staging-cedar
@@ -50,7 +46,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':cedar: Review at https://docs-internal-staging-cedar.githubapp.com/'
 
   - name: staging-cypress
@@ -63,7 +58,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':cypress: Review at https://docs-internal-staging-cypress.githubapp.com/'
 
   - name: staging-fir
@@ -76,7 +70,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':fir: Review at https://docs-internal-staging-fir.githubapp.com/'
 
   - name: staging-hemlock
@@ -89,7 +82,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':hemlock: Review at https://docs-internal-staging-hemlock.githubapp.com/'
 
   - name: staging-hinoki
@@ -102,7 +94,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':hinoki: Review at https://docs-internal-staging-hinoki.githubapp.com/'
 
   - name: staging-holly
@@ -115,7 +106,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':holly_: Review at https://docs-internal-staging-holly.githubapp.com/'
 
   - name: staging-juniper
@@ -128,7 +118,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':juniper: Review at https://docs-internal-staging-juniper.githubapp.com/'
 
   - name: staging-laurel
@@ -141,7 +130,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':laurel: Review at https://docs-internal-staging-laurel.githubapp.com/'
 
   - name: staging-pine
@@ -154,7 +142,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':pine: Review at https://docs-internal-staging-pine.githubapp.com/'
 
   - name: staging-redwood
@@ -167,7 +154,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':redwood: Review at https://docs-internal-staging-redwood.githubapp.com/'
 
   - name: staging-sequoia
@@ -180,7 +166,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':sequoia: Review at https://docs-internal-staging-sequoia.githubapp.com/'
 
   - name: staging-spruce
@@ -193,7 +178,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':spruce: Review at https://docs-internal-staging-spruce.githubapp.com/'
 
   - name: staging-yew
@@ -206,7 +190,6 @@ environments:
     cluster_selector:
       profile: general
       region: iad
-      name: general-2-ash1-iad
     extra_completed_message: ':yew: Review at https://docs-internal-staging-yew.githubapp.com/'
 
 required_builds:

content/copilot/concepts/agents/about-agent-skills.md

@@ -12,7 +12,7 @@ contentType: concepts
 ---
 
 > [!NOTE]
-> Agent skills work with {% data variables.copilot.copilot_cloud_agent %}, {% data variables.copilot.copilot_code-review_short %}, the {% data variables.copilot.copilot_cli %}, and agent mode in {% data variables.product.prodname_vscode %}.
+> Agent skills work with {% data variables.copilot.copilot_cloud_agent %}, {% data variables.copilot.copilot_code-review_short %}, the {% data variables.copilot.copilot_cli %}, the {% data variables.copilot.github_copilot_app %}, and agent mode in {% data variables.product.prodname_vscode %}.
 
 ## About agent skills
 
@@ -35,4 +35,5 @@ To create or add agent skills, see:
 
 * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/add-skills)
 * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/add-skills)
+* [AUTOTITLE](/copilot/how-tos/github-copilot-app/customize-github-copilot-app)
 * [AUTOTITLE](/copilot/reference/customization-cheat-sheet)

content/copilot/concepts/agents/about-enterprise-plugin-standards.md

@@ -0,0 +1,53 @@
+---
+title: About enterprise-managed plugin standards
+shortTitle: Enterprise plugin standards
+allowTitleToDifferFromFilename: true
+intro: Enterprise administrators can centrally define plugin policies for users, ensuring consistent plugin availability.
+versions:
+  feature: copilot
+contentType: concepts
+category:
+  - Learn about Copilot
+  - Learn about Copilot CLI
+docsTeamMetrics:
+  - copilot-cli
+redirect_from:
+  - /copilot/concepts/agents/copilot-cli/about-enterprise-plugin-standards
+---
+
+> [!NOTE] This feature is in {% data variables.release-phases.public_preview %} and subject to change.
+
+Enterprise-managed plugin standards allow administrators to **define and enforce policies for plugin availability**. By configuring a `settings.json` file in the enterprise's `.github-private` repository, administrators can specify which plugin marketplaces are available to users and which plugins are installed automatically.
+
+## Where plugin standards apply
+
+Plugin standards apply to all users on the enterprise's {% data variables.product.prodname_copilot_short %} plan, across the following clients:
+
+* **{% data variables.copilot.copilot_cli_short %}**: see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-cli-plugins)
+* **{% data variables.product.prodname_vscode_shortname %}** (version 1.122 and later): see [Agent plugins in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/agent-customization/agent-plugins) in the {% data variables.product.prodname_vscode_shortname %} documentation
+
+Users must upgrade to a supported client version for these standards to be applied.
+
+## How plugin standards work
+
+Enterprise plugin standards use a configuration file stored in your enterprise's `.github-private` repository. The configuration is defined in a `settings.json` file at the following path: `.github/copilot/settings.json`.
+
+For plugin standards, the file can define:
+
+* **Known marketplaces**. Plugin marketplaces that are available to users for browsing and installing plugins.
+* **Default-enabled plugins**. Specific plugins that are automatically installed when users authenticate.
+
+When a user authenticates to {% data variables.product.prodname_copilot_short %} in a supported client, the client queries an API endpoint that reads the `settings.json` from the enterprise's `.github-private` repository. The policies defined in the file are then applied to the user's session.
+
+## Why use enterprise-managed plugin standards
+
+Enterprise-managed plugin standards help administrators address several common challenges:
+
+* **Consistency across clients**. Ensure that all developers have access to the same plugins and marketplaces.
+* **Centralized governance**. Manage plugin availability from a single configuration file, rather than relying on individual developers to install the correct plugins.
+* **Version-controlled policies**. Because the configuration lives in a Git repository, all changes to plugin standards are tracked, auditable, and reviewable through pull requests.
+* **Reduced onboarding friction**. New developers automatically receive the enterprise's standard plugins when they authenticate, without any manual setup.
+
+## Next step
+
+To configure enterprise plugin standards, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards).

content/copilot/concepts/agents/copilot-cli/index.md

@@ -12,7 +12,6 @@ children:
   - /about-remote-control
   - /about-custom-agents
   - /about-cli-plugins
-  - /about-enterprise-plugin-standards
   - /autopilot
   - /fleet
   - /research
@@ -24,3 +23,4 @@ contentType: concepts
 docsTeamMetrics:
   - copilot-cli
 ---
+

content/copilot/concepts/agents/github-copilot-app.md

@@ -44,7 +44,7 @@ The {% data variables.copilot.github_copilot_app %} supports the following opera
 * **Parallel workspaces:** Run multiple isolated agent sessions simultaneously, each with a dedicated git worktree and branch. You can also run sessions in cloud sandboxes (public preview) hosted by {% data variables.product.github %}. For more information, see [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes).
 * **Session modes:** Choose how you work with agents: Interactive (collaborative), Plan (agent plans, you approve), or Autopilot (fully autonomous). You can also select from multiple LLMs and adjust reasoning effort for each session.
 * **{% data variables.product.github %} integration:** Browse and find issues, start sessions from them, create and close pull requests, review pull requests, view CI check results, and search across your repositories—all within the app.
-* **Customizations:** Configure MCP servers, skills, extensions, and plugins globally or for each session.
+* **Customizations:** Configure and use global instructions, MCP servers, and agent skills.
 * **Automations:** Save recurring agent tasks and run them on a schedule or on demand.
 * **Quick chats:** Brainstorm in a conversation mode without creating a dedicated branch or workspace.
 * **Session history:** Use `/chronicle` to get insights from previous sessions, including work you started in the app.

content/copilot/concepts/agents/index.md

@@ -12,6 +12,7 @@ children:
   - /code-review
   - /copilot-memory
   - /hooks
+  - /about-enterprise-plugin-standards
   - /about-third-party-coding-agents
   - /agent-apps
   - /openai-codex
@@ -20,3 +21,4 @@ children:
   - /enterprise-management
 contentType: concepts
 ---
+

content/copilot/concepts/context/mcp.md

@@ -36,7 +36,7 @@ category:
 
 The Model Context Protocol (MCP) is an open standard that defines how applications share context with large language models (LLMs). MCP provides a standardized way to connect AI models to different data sources and tools, enabling them to work together more effectively.
 
-You can use MCP to extend the capabilities of {% data variables.product.prodname_copilot %} by integrating it with a wide range of existing tools and services. MCP works across all major {% data variables.product.prodname_copilot_short %} surfaces—whether you're working in an IDE, using {% data variables.copilot.copilot_cli %}, or delegating tasks to an agent on {% data variables.product.prodname_dotcom_the_website %}. You can also use MCP to create new tools and services that work with {% data variables.product.prodname_copilot_short %}, allowing you to customize and enhance your experience.
+You can use MCP to extend the capabilities of {% data variables.product.prodname_copilot %} by integrating it with a wide range of existing tools and services. MCP works across all major {% data variables.product.prodname_copilot_short %} surfaces—whether you're working in an IDE, using {% data variables.copilot.copilot_cli %}, working in the {% data variables.copilot.github_copilot_app %}, or delegating tasks to an agent on {% data variables.product.prodname_dotcom_the_website %}. You can also use MCP to create new tools and services that work with {% data variables.product.prodname_copilot_short %}, allowing you to customize and enhance your experience.
 
 For more information on MCP, see [the official MCP documentation](https://modelcontextprotocol.io/introduction). For a curated list of MCP servers from partners and the community, see the [{% data variables.product.github %} MCP Registry](https://github.com/mcp).
 
@@ -45,7 +45,7 @@ To learn how to configure and use MCP servers, see:
 * [AUTOTITLE](/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp) for {% data variables.copilot.copilot_chat_short %} in your IDE
 * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers) for {% data variables.copilot.copilot_cli_short %}
 * [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers) for repository MCP configuration on {% data variables.product.prodname_dotcom_the_website %}
-
+* [AUTOTITLE](/copilot/how-tos/github-copilot-app/customize-github-copilot-app) for information on MCP server support in the {% data variables.copilot.github_copilot_app %}
 {% data reusables.copilot.mcp.mcp-policy %}
 
 ## Availability
@@ -54,6 +54,7 @@ MCP is supported across the following clients:
 
 * **IDEs**: There is broad support for local MCP servers in clients such as {% data variables.product.prodname_vscode %}, JetBrains IDEs, Xcode, and others. Support for remote MCP servers is growing, with editors like {% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, JetBrains IDEs, Xcode, Eclipse, Cursor, and Windsurf providing this functionality with OAuth or PAT. To find out if your preferred editor supports remote MCP servers, check the documentation for your specific editor.
 * **{% data variables.copilot.copilot_cli_short %}**: {% data variables.copilot.copilot_cli %} supports both local and remote MCP servers. The {% data variables.product.github %} MCP server is built in and available without additional configuration.
+* **{% data variables.copilot.github_copilot_app %}**: The {% data variables.copilot.github_copilot_app %} (in {% data variables.release-phases.technical_preview %}) supports MCP servers configured in your repository or {% data variables.copilot.copilot_cli_short %} and lets you add additional MCP servers in app settings.
 * **{% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_code-review_short %}**: {% data variables.product.prodname_dotcom_the_website %} supports MCP servers configured at the repository level. The configuration applies to both {% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_code-review_short %}. The {% data variables.product.github %} MCP server and Playwright MCP server are configured by default.
 
 ## About the {% data variables.product.github %} MCP server