Copilot Studio Extension for Visual Studio Code

The Copilot Studio extension for Visual Studio Code is designed to enhance the development experience of Microsoft Copilot Studio agents. It provides language support, IntelliSense code completion and suggestions, and authoring capabilities for Copilot Studio agent components.

After installation, the extension prompts you to sign in to Copilot Studio. It can then show you a list of the agents associated with your environment. Clone an agent to see its editable components, including knowledge sources, actions, topics, and triggers.

1. Select the Copilot Studio icon in the primary side bar of Visual Studio Code. The extension asks for your permission to sign in.

2. Select Allow, and sign in with the appropriate credentials for your Copilot Studio environment.

1. (Optional) Open the desired agent in Copilot Studio and copy its URL from your browser's address bar.

2. In the Copilot Studio panel of Visual Studio Code, select Clone agent.

3. Select your agent (marked with "from clipboard" if you already copied the URL); otherwise, select the desired environment and then select the desired agent. The extension prompts you to select a folder to hold your agent's files (similar to a local repository).

   

4. Select the desired folder.

To edit any component, open the corresponding file and make the desired changes. Since Visual Studio Code natively supports YAML files, the Copilot Studio extension supports IntelliSense code completion and can provide guided tips.

The Copilot Studio extension keeps your local workspace in sync with your agent. Use the sync commands in the Agent Changes view to manage changes between your local files and your Copilot Studio agent.

• Preview changes — See what's different between your local workspace and the agent in Copilot Studio, without modifying any files.
• Get changes — Download the latest changes from your Copilot Studio agent into your local workspace.
• Apply changes — Upload your local edits to your Copilot Studio agent.

When you apply changes, they are saved directly to your agent's environment. This is a live editing experience—your agent is updated immediately.

src/
  LanguageServers/                        # .NET language server (C#)
    CLaSP/                                # Common Language Server Protocol framework
    PowerPlatformLS/                      # Language server solution (11 projects)
  vscode-extensions/                      # VS Code extension (TypeScript)
    microsoft-powerplatformlang-extension/  # Extension entry point
    shared/                               # Shared TypeScript modules
docs/                                     # Architecture documentation
assets/                                   # Shared assets (BotSchema.json)
build/                                    # Build infrastructure

For architecture details, see the docs/ folder.

See CONTRIBUTING.md for build prerequisites, current build state, and contribution guidelines.

Drives the real extension in a real VS Code window, over the LSP client and server, against a real environment. It creates and deletes cloud agents, so point it at a development environment only.

Setup is one gitignored config file at the extension root:

cd src/vscode-extensions/microsoft-powerplatformlang-extension
cp lspe2e.config.example.json lspe2e.config.json   # use copy on Windows

Fill in environmentId for your development environment — the Power Platform admin center shows it. The suite resolves the environment's Dataverse URL through BAP. Running any command below without the config prints the exact path and the template.

Every agent scenario runs in two agent shapes — classic and cli. The workflow shape is a standalone workflow project.

--group takes smoke, vscode, workflow, interop, all, or a comma-separated list. --no-clean leaves the agents behind for inspection.

msagent must be installed and signed in by running msagent auth login, because deleting the agents a run created goes through msagent agent delete.

Result for each run — full transcript, machine-readable report, per-failure logs and the cloned workspaces — are left in %TEMP%\mcs-lsp-e2e\<run>\, and the path is printed when the run finishes.

Every run uploads three fixtures to the environment — one per authoring shape, plus a standalone cloud flow — and works against those. They live in client/src/tests/ui/fixtures:

To help us resolve problems more efficiently, please use the custom issue reporting command built into this extension. It automatically includes helpful diagnostic information like your session ID.

✅ Recommended: use the custom Help: Copilot Studio: Report Issue command

1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P on macOS)
2. Type and select: Help: Copilot Studio: Report Issue

3. A form will appear with a pre-filled Session ID, fill out the form and submit. This ensures we receive context to investigate your issue quickly.

⚠️ Avoid using the built-in Help: Report Issue...

This project has adopted the Microsoft Open Source Code of Conduct. See CODE_OF_CONDUCT.md for details.

MIT