microsoft / microsoft/PowerToys

DevLaunch — Open In... for Windows File Explorer

Open
#45,792 1 comment 1 reaction 0 assignees View on GitHub
Idea-New PowerToy Needs-Triage Product-File Explorer
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Description of the new feature/enhancement

Add a PowerToys feature that shows a compact bottom toolbar for Windows File Explorer. The toolbar displays user-configured buttons (VS Code, Windows Terminal, Rider, etc.) and launches them using PATH-resolved CLI commands with the current Explorer folder as the working directory.

### Expected behavior

- A PowerToys module that can be enabled/disabled.
- A bottom toolbar appears for File Explorer windows without injecting into Explorer.
- Users can choose which actions are visible (toggle on/off per tool).
- Actions are defined with a display name, command, args, and enabled toggle.
- `{path}` in args is replaced with the active Explorer folder.
- The toolbar respects DPI and Windows 11 styling.

### Scenario when this would be used?

As a developer, I often jump between File Explorer and tools like VS Code, Windows Terminal, Rider, or Git clients. This toolbar removes the constant right-click and navigation friction. It mirrors the productivity of VS Code's bottom status actions but for Explorer.

### Why it matters

Power users spend a lot of time in Explorer. A built-in, configurable toolbar saves time, reduces repetitive actions, and makes tool switching feel native. It also fits PowerToys' goal of making Windows more productive without requiring custom shell extensions.

### Supporting information

- ExplorerHere (standalone prototype): a lightweight WPF toolbar that follows the active Explorer folder and launches PATH-resolved commands.
- The approach avoids unsupported Explorer UI injection while still delivering quick access.
- This can be implemented as a PowerToys module with a settings page and per-action toggles.

Contributor guide

Open the contributing guide

Research direction

No implementation files or tests are named. Start by reviewing the ExplorerHere prototype and the PowerToys module and settings approach described in the issue; done means a configurable, DPI-aware bottom toolbar appears in File Explorer, resolves commands from PATH, substitutes {path}, and launches them in the active folder.

Written by the indexing model from the issue text.

Assessment

Domain
cli, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.