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

Install Plugin from Source reveals plugins in the legacy details UI

Open Beginner friendly
#339,900 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start with the implementation of the “Chat: Install Plugin from Source” Command Palette command and trace the flow after an agent plugin is installed and revealed. Compare the reveal target with the current Chat Customizations → Plugins details view. Done means the installed plugin opens in the current Plugins view rather than the legacy Extensions-based details modal; verify using the listed reproduction steps.

Written by the indexing model from the issue text.

Description

chat-customizations

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: Code - OSS Dev 1.142.0
  • OS Version: macOS arm64

Description

Running Chat: Install Plugin from Source from the Command Palette reveals the installed plugin in the legacy Extensions-based Agent Plugins view.

The plugin should instead open in the current Chat Customizations Plugins view, which provides the current plugin details experience.

Steps to reproduce

  1. Run Chat: Install Plugin from Source from the Command Palette.
  2. Install an agent plugin from a repository.
  3. Select the installed plugin after VS Code reveals it.

Expected

VS Code opens the installed plugin in Chat Customizations → Plugins.

Current Chat Customizations plugin details

Actual

VS Code opens the installed plugin in the legacy Extensions-based details modal.

Legacy Extensions-based plugin details modal

Found while verifying #328856 for https://github.com/microsoft/vscode-internalbacklog/issues/9915.

Dominant language
TypeScript
Stars
193k
Forks
44.1k
Avg merge
7h 43m
Merged PRs (30d)
649

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.