Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The canvas development and testing experience is too bad

Open
#4,089 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
github
Domain
desktop, developer-experience, tooling

Research direction

Start by reproducing the workflow in the Copilot app: install a local plugin from the Installed tab, open a new canvas, and observe the disabled-extension behavior. Inspect /Users/zach.zhang/.copilot/settings.json and its extensions.disabledExtensions entry. Done should mean local development and testing require fewer repeated steps and the canvas can be established without manually deleting the plugin entry.

Written by the indexing model from the issue text.

Description

Firstly, I need to say I love the canvas in Github Copilot APP, it is very versatile and powerful, incredibly extend our plugin limitation.

But the development and testing can't fluently promote and terrably bad. When I developed some change, then I need go to installed tab install the plugin locally and check the plugin version updated.

Then I can test it on the canvas tab and open a new canvas. It is not difficult but I must test it every times.

And there is a bug, the plugin is always diabled when I done my development. So the canvas is can't established, I need delete the line when I developed.

/Users/zach.zhang/.copilot/settings.json

  "extensions": {
    "disabledExtensions": [
      "plugin:feature-launchpad:feature-launchpad"
    ]
  }
Dominant language
No language data
Stars
2.1k
Forks
157
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/app

All issues in github/app

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.