Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Copilot Preview JumpNew to Visual Studio Code? Get it now.
Copilot Preview Jump

Copilot Preview Jump

Preview

luokevin

|
4 installs
| (0) | Free
Adds an editor title action to open the actual file for GitHub Copilot previews.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Copilot Preview Jump

Open the actual workspace file behind GitHub Copilot change previews.

When a supported Copilot preview is active, use Copilot Preview: Open Actual File for Preview from the command palette, editor title, or editor context menu to jump from the preview model back to the actual file on disk.

Features

  • Opens the actual file behind supported GitHub Copilot preview resources.
  • Adds an editor title action when a supported preview is active.
  • Adds an editor context menu action for supported previews.
  • Includes English and Simplified Chinese UI strings.
  • Includes a diagnostic command, Copilot Preview: Show Current Preview URI, for reporting unsupported preview URI shapes.

Supported Preview Resources

This extension currently recognizes these URI schemes:

  • copilot-cli-readonly
  • chat-editing-snapshot-text-model
  • chat-editing-text-model

Limitations

This is an unofficial extension and is not affiliated with GitHub or Microsoft.

The extension relies on URI schemes exposed by GitHub Copilot Chat preview editors. If GitHub Copilot Chat changes those internal preview URI schemes, this extension may need an update.

Requirements

  • Visual Studio Code 1.120.0 or later
  • GitHub Copilot Chat

Commands

  • Copilot Preview: Open Actual File for Preview
  • Copilot Preview: Show Current Preview URI

Development

npm install
npm run compile
npm run package

Open this folder in VS Code and press F5 to launch an Extension Development Host.

GitHub Releases

The repository includes a GitHub Actions workflow that builds a VSIX package and publishes it as a GitHub Release when a semantic version tag is pushed.

Before creating a release, make sure the tag version matches package.json:

git tag v0.2.0
git push origin v0.2.0

The workflow will:

  • run npm ci
  • verify v0.2.0 matches package.json version 0.2.0
  • run npm run compile
  • run npm run package
  • create a GitHub Release
  • upload the generated .vsix file

The workflow can also be run manually from the GitHub Actions tab.

Publishing Checklist

Before publishing, replace these placeholders in package.json:

  • your-publisher-id
  • YOUR_GITHUB_USER

Also replace the placeholder copyright holder in LICENSE.txt.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft