Copilot Managed Runtime: clone and update an app

Key insights

• The demonstration starts with a Risk Matrix app and uses the Microsoft 365 CLI to clone it locally.
• After cloning, the app is run and edited in VS Code, then changes are pushed back to the live app.
• The source says apps have a Git repository behind them, whether created through Copilot Studio, Cowork or the CLI.
• The material does not specify required roles, licenses, runtime availability or exact CLI commands.

Copilot Managed Runtime apps can be cloned to a local development environment, edited in VS Code and updated by pushing changes back to the live app. This workflow matters to makers and developers who want to move from an AI-generated or low-code starting point into hands-on code changes. Andrew Hess - MySPQuestions demonstrates the process using a Risk Matrix app and the Microsoft 365 CLI.

What it does

The key idea is that an app created through a supported entry point does not have to remain solely in its original creation experience. The source describes a Git repository behind each Copilot Managed Runtime app, including apps that began in Copilot Studio, Copilot Cowork or the CLI. That repository connection gives developers a way to work on the app locally and send changes back to its live version.

This is a handoff between maker-oriented creation and developer-oriented editing, rather than a separate app-building feature. A maker can start without writing code, while a developer can continue in VS Code. The demonstration’s example is a Risk Matrix app; the supplied material does not describe its business logic or provide enough detail to assess the app itself.

Who it is for and what you need

The workflow is relevant to makers who want a developer to extend an app, and developers who need a local editing loop for a Managed Runtime app. The named tools are the Microsoft 365 CLI (referred to as the ms CLI in the source) and VS Code. The supplied material does not state which user role or permissions are required to clone or publish an app.

It also does not specify a Microsoft 365 or Copilot license, a particular tenant configuration, or regional availability. The linked Microsoft documentation covers a Managed Apps CLI quickstart, a development inner loop, and CLI commands, but the source material provided here does not establish the specific prerequisites or rollout status. Check those docs and your organization’s configuration before treating the example as a supported production workflow for your environment.

How it works

The practical sequence is to retrieve the existing app, make local changes, and publish those changes back. In the example, the developer starts with an app already built as a Risk Matrix, rather than creating a new app from scratch during the local development steps. The source names the CLI as the means of cloning and pushing.

1. Start with an existing Copilot Managed Runtime app. The demonstration uses a Risk Matrix app.
2. Use the Microsoft 365 CLI to clone the app to a local working environment. The source does not provide the exact command or flags in its description.
3. Open and run the local app in VS Code, then make the desired changes. The supplied material does not identify particular files or code edits.
4. Use the CLI workflow to push changes back to the live app. Confirm the current command syntax and any required permissions in Microsoft’s CLI documentation.

The important operational distinction is that local work and the live app are separate stages in this example. Cloning provides a local copy to work on; pushing is the step that sends changes back to the live app. Teams should verify what will be published and follow their own review process before updating an app used by others.

The description also names several ways to build apps: Copilot Studio, Copilot Cowork, Copilot Code, GitHub Copilot, Claude Code and Lovable. It does not provide a feature-by-feature comparison or say that all those tools use identical workflows. The specific local clone-and-push demonstration uses the CLI and VS Code.

Limitations and open questions

The available material is brief and does not include a transcript of the demonstration, exact CLI commands, screenshots, app structure, authentication steps or troubleshooting guidance. It therefore supports the broad sequence—clone, work locally, push—but not a copy-and-paste procedure. Use the linked quickstart and command reference for current syntax.

It is also unclear from this material which app types, runtime configurations or account permissions are eligible for the same workflow. The source says apps have a Git repository behind them, but does not explain repository access, branching, conflict handling, rollback or how changes are reviewed before they reach the live app. Those details should not be assumed from the general description.

The material does not compare this method with an older publishing process, nor does it state a preview or general availability status. It demonstrates a development technique, not a complete governance or release policy. Admins and developers should confirm the applicable Microsoft documentation and their tenant’s rules before adopting it for production changes.

Sources

• Microsoft Managed Apps CLI quickstart
• Microsoft Managed Apps development inner loop
• Microsoft 365 CLI command reference for Managed Apps
• Andrew Hess - MySPQuestions demonstration

Frequently asked questions

How do I edit a Copilot Managed Runtime app in VS Code?

The demonstrated workflow uses the Microsoft 365 CLI to clone the app locally, then opens and runs it in VS Code. Use Microsoft’s CLI quickstart and command reference for the exact commands.

Can I push local changes back to a live Copilot Managed Runtime app?

The demonstration describes using the CLI to push changes from a local app back to the live app. The supplied material does not give command syntax or explain review, rollback or conflict handling.

What license or permissions are required to clone a Managed Runtime app?

The supplied material does not state required licenses, roles or permissions. Check the Microsoft Managed Apps documentation and your organization’s configuration.