Skip to content

[Feature] Allow selecting which shells appear in the Explorer context menu #218

Open

Description

@onedotmint

Problem / pain point

Pebrel currently adds Explorer context menu entries automatically, including entries for each installed WSL distribution.

For example, on my system this adds:

  • Open in Pebrel
  • Open in Pebrel (Ubuntu)
  • Open in Pebrel (Debian)

I may want some of these entries, but not all of them. With multiple WSL distributions installed, the Explorer context menu can become quite cluttered.

Currently, the only workaround seems to be manually editing the registry.

Proposed solution

Allow users to choose which Explorer context menu entries Pebrel registers.

For example, either during installation or in Pebrel settings:

  • Open in Pebrel
  • Open in Pebrel (Ubuntu)
  • Open in Pebrel (Debian)

Changing these options later should automatically add or remove the corresponding context menu entries.

It would also be useful to have a master option to disable Explorer context menu integration entirely.

Optionally, WSL entries could also be grouped into a submenu to avoid taking up multiple top-level entries.

Alternatives considered

  • Manually removing or disabling the registry entries.
  • Disabling all Pebrel context menu entries.

Neither is ideal because I still want to keep some entries while hiding others, and manual registry changes may need to be repeated after updates or reinstallations.

Related area

Local terminal / shell

How important is this to you?

Would improve my daily workflow

Before submitting

  • I searched existing issues for similar requests

Activity

  1. WilliamWang1721 commented on Oct 3, 2026

    @WilliamWang1721
    Contributor

    Implementation is available in PR #456 (#456).

    Adds installer selection of Explorer shell/WSL entries, preserves upgrade choices, and protects unknown registry subtrees.

    Current upstream checks at f559d140: all reported checks passed. Maintainer/Code Owner approval and any platform acceptance limitations described in the PR remain outstanding. This update does not close the issue.

  2. Kuddev commented on Nov 12, 2026

    @Kuddev
    Owner

    The installer choice in #456 is worth keeping. The existing selection and WSL subtree checks passed on Windows. The additional registry run found that moving the installation leaves menu entries pointing at the old directory, and a menu conflict can leave some WSL choices applied even though the installer rejects the change.

    I left the two cases and the Windows test evidence in the PR review. The per-entry choices remain open until those upgrade paths are fixed and verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancement新功能或改进 / new feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions