Repo sync

content/apps/using-github-apps/about-using-github-apps.md

@@ -35,8 +35,21 @@ Occasionally, the {% data variables.product.prodname_github_app %} will request
 
 Before you install or authorize a {% data variables.product.prodname_github_app %}, you should make sure that you trust the app developer. If you no longer use the app, you should suspend or uninstall the app and/or revoke your authorization of the app. For more information, see [AUTOTITLE](/apps/using-github-apps/reviewing-and-modifying-installed-github-apps#blocking-access) and [AUTOTITLE](/apps/using-github-apps/reviewing-your-authorized-integrations).
 
-## {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+{% ifversion fpt or ghec %}
+
+## {% data variables.copilot.agent_apps_caps %}
+
+> [!NOTE] {% data reusables.copilot.agent-apps-preview %}
+
+{% data reusables.copilot.agent-apps-intro %} Powered by {% data variables.copilot.copilot_cloud_agent %}, you can trigger these agents from issues, pull requests, and the Agents UI.
 
+When you install an {% data variables.copilot.agent_app %}, you will be asked if you want to enable agent features. For more information, see [AUTOTITLE](/copilot/concepts/agents/agent-apps).
+
+If the app is installed in an organization owned by an enterprise, an administrator must also enable the "{% data variables.copilot.agent_apps %}" {% data variables.product.prodname_copilot_short %} policy before the agent features become available.
+
+{% endif %}
+
+## {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
 {% data variables.product.company_short %} also supports {% data variables.product.prodname_oauth_apps %}. Unlike {% data variables.product.prodname_github_apps %}, you do not install an {% data variables.product.prodname_oauth_app %} or control what repositories it can access.
 
 Both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %} use OAuth 2.0.

content/billing/concepts/billing-cycles.md

@@ -35,6 +35,13 @@ For example, if you started a paid plan or converted from a trial on the 15th of
 > [!NOTE]
 > From **December 1, 2025**, all self-serve, metered {% data variables.product.prodname_ghe_cloud %} accounts that pay by credit card will migrate to a **billing date** of 1st of the month. See [Billing date standardized to the first of the month for self-serve credit card metered Enterprise customers](https://github.blog/changelog/2025-11-17-billing-date-standardized-to-the-first-of-the-month-for-self-serve-credit-card-metered-enterprise-customers-now-generally-available/) in the changelog.
 
+## Billing cycle for {% data variables.copilot.sandbox %} during public preview
+
+During {% data variables.release-phases.public_preview %}, eligible accounts receive a **$10 monthly entitlement** for cloud sandbox usage in **June 2026**. The entitlement applies as follows:
+
+* Usage above the entitlement is metered against your standard billing cycle and billed on your normal billing date.
+* The entitlement is discontinued after June 2026. Pricing and packaging after the preview is subject to change.
+
 ## Billing cycles for volume-based products
 
 Volume-based licenses may follow a different billing cycle. These products are often billed based on the anniversary date of your subscription rather than by calendar month.
@@ -66,5 +73,6 @@ Find product-specific guidance on how usage is calculated and billed.
 * [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)
 * [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-packages/about-billing-for-github-packages)
 * [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-copilot/about-billing-for-github-copilot)
+* [AUTOTITLE](/billing/concepts/product-billing/cloud-and-local-sandboxes)
 * [AUTOTITLE](/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise#about-licenses-for-visual-studio-subscriptions-with-github-enterprise-cloud)
 * [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage)

content/billing/concepts/budgets-and-alerts.md

@@ -17,7 +17,7 @@ By setting a monthly budget, you can monitor your spending and receive notificat
 
 For most license-based products such as {% data variables.product.prodname_copilot %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_enterprise %}, setting a budget does not prevent usage over the budget amount but does provide alerts. {% data variables.product.prodname_GHAS %} SKUs are an exception to this, as they can be set to stop usage when the budget amount is reached. See [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security#hard-budgets-for-github-advanced-security-skus).
 
-For metered products such as {% data variables.product.prodname_actions %} or {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}, you can set budgets to prevent usage once the budget threshold is reached.
+For metered products such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}, or cloud sandboxes, you can set budgets to prevent usage once the budget threshold is reached.
 
 ## Types and scopes
 

content/billing/concepts/product-billing/cloud-and-local-sandboxes.md

@@ -0,0 +1,87 @@
+---
+title: Billing for {% data variables.copilot.sandbox %}
+shortTitle: Cloud and local sandboxes
+intro: 'Learn how usage of {% data variables.copilot.sandbox %} is measured and billed.'
+versions:
+  fpt: '*'
+  ghec: '*'
+contentType: concepts
+category:
+  - Understand product costs
+---
+
+{% data reusables.cli.public-preview-sandbox %}
+
+## How {% data variables.copilot.sandbox %} usage is measured
+
+Billing applies to cloud sandboxing only. Local sandboxing is included in the standard {% data variables.product.prodname_copilot %} seat at no additional cost.
+
+A cloud sandbox session incurs charges across three meters:
+
+* **Compute**: the time a cloud sandbox session is running.
+* **Memory**: the memory allocated to a cloud sandbox session while it is running.
+* **Storage**: snapshot storage for stopped sessions.
+
+Usage is measured from the moment a session starts until it is stopped or deleted. Memory is measured based on the memory allocated to the session, not the memory actively in use.
+
+### Compute
+
+The compute meter tracks the time a cloud sandbox is running. Compute is not metered while a sandbox is stopped.
+
+### Memory
+
+The memory meter tracks the memory allocated to a cloud sandbox while it is running. Memory is not metered while a sandbox is stopped.
+
+### Storage
+
+The storage meter tracks snapshot storage for stopped sessions. When you stop {% data variables.copilot.sandbox_short %}, {% data variables.product.github %} retains a snapshot of the sandbox's state so you can resume it later. Snapshot storage is metered from the time the sandbox is stopped until the sandbox is deleted.
+
+For more information about {% data variables.copilot.sandbox %}, see [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes).
+
+## Free and billed use
+
+During public preview, eligible {% data variables.product.github %} accounts receive a **$10 monthly entitlement** to try cloud sandboxes. This entitlement is available for June 2026. Any usage beyond the monthly entitlement is billed to your account.
+
+After the preview period ends, the entitlement no longer applies and all usage is billed.
+
+## Paying for use
+
+You pay for cloud sandboxes using the payment method set up for your {% data variables.product.github %} account. See [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info).
+
+### Pricing
+
+| Meter | Description | Unit | Price (USD) |
+| --- | --- | --- |------------|
+| Compute | Time that a cloud sandbox session is running. | Compute second | $0.000024 |
+| Memory | Memory allocated to a cloud sandbox session while it is running. | GiB second | $0.000003 |
+| Storage | Snapshot storage for stopped sessions. | GiB month | $0.005  |
+
+## How costs are assigned to a billable account
+
+Cloud sandbox usage is billed to the organization that owns the sandbox. When you create a cloud sandbox session with `copilot --cloud`, you are prompted to select the owning organization. All usage for that session is billed to the selected organization.
+
+## Managing your budget for cloud sandboxes
+
+{% data reusables.billing.default-over-quota-behavior %}
+
+You can set budgets and alerts to monitor and control your cloud sandbox spending. For more information, see [AUTOTITLE](/billing/concepts/budgets-and-alerts) and [AUTOTITLE](/billing/how-tos/set-up-budgets).
+
+When you create a budget for cloud sandboxes, you can choose between two budget types:
+
+* **Product-level budget**: caps spending across all cloud sandbox usage, regardless of SKU.
+* **SKU-level budget**: caps spending for a specific cloud sandbox SKU (for example, "Sandbox Linux"). For a full list of cloud sandbox SKUs, see [AUTOTITLE](/billing/reference/product-and-sku-names).
+
+If you enable **Stop usage when budget limit is reached**, additional cloud sandbox usage is blocked once the budget reaches 100%, and a banner notifies users in the affected scope.
+
+> [!NOTE]
+> {% data variables.copilot.sandbox_caps %} is not part of the "Bundled AI credits" budget type. Bundled AI credits budgets apply only to SKUs that consume AI credits (such as {% data variables.product.prodname_copilot %} AI credits, cloud agent AI credits, and {% data variables.product.prodname_spark %} AI credits). To control cloud sandbox spending, use a product-level or SKU-level budget.
+
+## Viewing your {% data variables.copilot.sandbox %} usage
+
+To view your cloud sandbox usage, billable amounts, and the monthly preview entitlement, see [AUTOTITLE](/billing/how-tos/products/estimate-spending) and [AUTOTITLE](/billing/tutorials/gather-insights).
+
+## Further reading
+
+* [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes)
+* [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli)
+* [AUTOTITLE](/billing/get-started/how-billing-works)

content/billing/concepts/product-billing/index.md

@@ -15,6 +15,7 @@ children:
   - /github-copilot-licenses
   - /github-models
   - /github-packages
+  - /cloud-and-local-sandboxes
   - /git-lfs
   - /github-spark
 contentType: concepts

content/billing/reference/product-and-sku-names.md

@@ -22,6 +22,7 @@ For **ProductPricing** budgets or to query usage by product, use one of the foll
 * `copilot` - {% data variables.product.prodname_copilot %}
 * `ghas` - {% data variables.product.prodname_GH_advanced_security %}
 * `ghec` - {% data variables.product.prodname_ghe_cloud %}
+* `sandbox` - {% data variables.copilot.sandbox_caps %}
 
 ## SKU-level identifiers
 
@@ -93,6 +94,12 @@ For **SkuPricing** budgets or to query usage by SKU, use one of the following va
 * `ghas_licenses` - GHAS licenses
 * `ghas_secret_protection_licenses` - GHAS secret protection licenses
 
+### {% data variables.copilot.sandbox_caps %} SKUs
+
+* `sandbox_linux` - {% data variables.copilot.sandbox_short_caps %} Linux
+* `sandbox_memory` - {% data variables.copilot.sandbox_short_caps %} Memory
+* `sandbox_snapshot` - {% data variables.copilot.sandbox_short_caps %} Snapshot
+
 ### Other SKUs
 
 * `ghec_licenses` - {% data variables.product.prodname_ghe_cloud %} licenses

content/copilot/concepts/about-cloud-and-local-sandboxes.md

@@ -0,0 +1,115 @@
+---
+title: About {% data variables.copilot.sandbox %}
+shortTitle: Cloud and local sandboxes
+allowTitleToDifferFromFilename: true
+intro: '{% data variables.copilot.sandbox_caps %} provide isolated execution environments that let {% data variables.product.prodname_copilot_short %} safely interact with code, tools, filesystem, and network resources securely on your local machine or in fully isolated cloud environments.'
+versions:
+  feature: copilot
+redirect_from:
+  - /copilot/concepts/about-github-sandbox
+contentType: concepts
+category:
+  - Learn about Copilot
+  - Learn about Copilot CLI
+docsTeamMetrics:
+  - copilot-cli
+---
+
+{% data reusables.cli.public-preview-sandbox %}
+
+## Introduction
+
+{% data variables.copilot.sandbox_caps %} are the execution platform powering secure sandboxed experiences for {% data variables.copilot.copilot_cli %}, both locally and in the cloud. As {% data variables.product.prodname_copilot_short %} takes more actions on your behalf—running tools, executing commands, and modifying files—{% data variables.copilot.sandbox_short %} provide the isolation, portability, and policy controls needed to adopt agentic workflows safely. {% data variables.copilot.sandbox_caps %} currently apply to {% data variables.copilot.copilot_cli_short %} sessions, and you can also use cloud sandboxes for sessions in the {% data variables.copilot.github_copilot_app %}.
+
+With {% data variables.copilot.sandbox %}, you can choose where {% data variables.product.prodname_copilot_short %} runs:
+
+* **Local sandboxing**: Run {% data variables.product.prodname_copilot_short %} securely on your own machine, with restricted access to filesystem, network, and system capabilities.
+* **Cloud sandboxing**: Run {% data variables.product.prodname_copilot_short %} inside fully isolated, ephemeral Linux environments hosted by {% data variables.product.github %}.
+
+## Local sandboxing
+
+Local sandboxing lets {% data variables.product.prodname_copilot_short %} run in a sandboxed environment directly on your machine, with restricted access to your filesystem, network connectivity, and system capabilities.
+
+### Enabling local sandboxing
+
+To enable local sandboxing inside a {% data variables.copilot.copilot_cli_short %} session, run:
+
+```shell copy
+/sandbox enable
+```
+
+Once enabled, commands that {% data variables.product.prodname_copilot_short %} executes on your behalf run inside the sandbox, limiting their access to your system.
+
+### Cross-platform support
+
+Local sandboxing is available across macOS, Linux, and Windows, delivering a consistent isolation experience regardless of your operating system.
+
+### Enterprise policy enforcement
+
+For organizations and enterprises, local sandbox policies can be centrally configured and enforced using Microsoft Intune and other MDM (mobile device management) platforms. This gives administrators control over how {% data variables.product.prodname_copilot_short %} interacts with local resources across managed devices.
+
+## Cloud sandboxing
+
+Cloud sandboxing lets you run {% data variables.copilot.copilot_cli_short %} sessions inside fully isolated, ephemeral Linux environments hosted by {% data variables.product.github %}. Each cloud sandbox session is isolated from your local environment and from other sessions.
+
+Cloud sandboxing is built on Azure Container Apps Sandboxes, with {% data variables.product.github %} providing the identity, policy, and billing layer.
+
+### Starting a cloud sandbox session
+
+To start a cloud-backed session, run the following command:
+
+```shell copy
+copilot --cloud
+```
+
+This launches an interactive {% data variables.copilot.copilot_cli_short %} session inside a cloud sandbox. You can prompt {% data variables.product.prodname_copilot_short %} to perform tasks, run shell commands, and iterate on code, the same way you would in a local session. The commands that {% data variables.product.prodname_copilot_short %} runs execute in the cloud environment, not on your local machine.
+
+### Continue sessions across devices
+
+Because cloud sandbox sessions run in {% data variables.product.github %}-hosted infrastructure, you can pick up a {% data variables.product.prodname_copilot_short %} session on any device, regardless of where the session was originally started. This enables more flexible workflows without needing to copy files or reinstall dependencies.
+
+### Offload compute-intensive workflows
+
+You can run multiple {% data variables.product.prodname_copilot_short %} tasks in parallel in the cloud without consuming local resources. This keeps your local environment lightweight and responsive while scaling agent-driven work.
+
+### Unified governance
+
+Cloud sandbox policies share the same configuration as {% data variables.copilot.copilot_cloud_agent %} policies, extending existing security controls to cloud sandboxed execution without additional setup.
+
+### Session lifecycle
+
+A cloud sandbox session has three main states:
+
+* **Active**: The session is running, and you are interacting with it from {% data variables.copilot.copilot_cli_short %}.
+* **Stopped**: The session is not currently running, but its state is saved. When you resume it, your files, environment variables, and in-progress work are restored.
+* **Deleted**: The session and its saved state are removed and cannot be recovered.
+
+When you stop a session, the cloud sandbox creates a snapshot of its state so you can pick up where you left off later. When you delete a session, both the running environment and the snapshot are removed.
+
+## Authentication and access
+
+{% data variables.copilot.sandbox_short_caps %} use your existing {% data variables.copilot.copilot_cli_short %} authentication. If you can sign in to {% data variables.copilot.copilot_cli_short %} and have access to {% data variables.product.prodname_copilot_short %}, you can use {% data variables.copilot.sandbox_short %}. You don't need to configure a separate cloud provider, manage API keys, or set up infrastructure.
+
+An organization or enterprise owner must enable the **Cloud Sandbox access** policy in the organization or enterprise settings before members can use {% data variables.copilot.sandbox_short %}.
+
+For information about signing in to {% data variables.copilot.copilot_cli_short %}, see [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-cli).
+
+## Billing
+
+Local sandboxing is included in the standard {% data variables.product.prodname_copilot %} seat at no additional cost.
+
+Cloud sandboxing is billed based on usage. {% data variables.product.github %} measures cloud sandbox usage across three meters:
+
+| Meter | Description | Unit | Price (USD) |
+| --- | --- | --- |------------|
+| Compute | Time that a cloud sandbox session is running. | Compute second | $0.000024 |
+| Memory | Memory allocated to a cloud sandbox session while it is running. | GiB second | $0.000003 |
+| Storage | Snapshot storage for stopped sessions. | GiB month | $0.005  |
+
+For more information about how cloud sandbox usage is measured and billed, see [AUTOTITLE](/billing/concepts/product-billing/cloud-and-local-sandboxes).
+
+## Further reading
+
+* [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli)
+* [AUTOTITLE](/copilot/how-tos/cloud-and-local-sandboxes/enabling-or-disabling-cloud-and-local-sandboxes-for-your-organization)
+* [AUTOTITLE](/copilot/how-tos/set-up/install-copilot-cli)

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 %}, 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 %}, and agent mode in {% data variables.product.prodname_vscode %}.
 
 ## About agent skills