Title: Option to open "Reveal in System Explorer" as tab in existing Explorer window
Disclaimer; Lumo AI Chat helped me write this feature request. I read through it manually and afaik every info is correct.
**Description**
When using the right-click context menu option "Reveal in system explorer" (or "Open in Explorer") on a file or folder within Obsidian, a new File Explorer window is launched instead of opening the folder as a tab in an already-open Explorer instance. This creates multiple separate windows that clutter the taskbar and make navigation inefficient.
---
**Troubleshooting Already Attempted**
I have verified that the Windows File Explorer setting "Open each folder in its own process" is already disabled in my system (Folder Options → View tab), which means I'm relying on Windows 11's native tabbed Explorer functionality. Despite this configuration, Obsidian's "Reveal in system explorer" command still spawns a new window instead of using the existing tab-enabled instance.
**Steps to Reproduce**
1. Have an existing File Explorer window already open (Windows 11 with tabs enabled)
2. In Obsidian, right-click on a file or folder in the file explorer pane
3. Select "Reveal in system explorer" from the context menu
4. Observe that a NEW Explorer window opens instead of the folder appearing as a tab in the existing window
---
**Expected Behavior**
When "Reveal in system explorer" is invoked, if a File Explorer window is already running, the target folder should open as a **new tab** in that existing window, rather than spawning a separate window.
---
**Actual Behavior**
A completely new File Explorer process/window is launched every time, regardless of whether an Explorer instance is already running. This results in dozens of orphaned windows during active work sessions.
---
**Use Case**
I use Obsidian extensively throughout my workday alongside Windows File Explorer. When I need to locate a file's exact path in the system (to copy it elsewhere, check properties, etc.), I regularly use "Reveal in system explorer". Currently, each invocation creates a new window that accumulates in my taskbar, requiring manual cleanup. On Windows 11, native tabbed Explorer exists, but Obsidian bypasses this capability.
---
**Requested Solution**
Add an optional setting (or adopt as default behavior) that forces "Reveal in system explorer" to:
- Detect if an Explorer window is already active
- Open the revealed folder as a **tab** in that window
- Bring the existing window to the foreground
If Windows APIs don't natively support this, consider integrating a workaround similar to what PowerToys Run aims to implement (but for Obsidian specifically).
**Windows/PowerToys Roadmap Context**
Interestingly, Microsoft's PowerToys team has this functionality listed in their 2025-2026 roadmap under "File Explorer (Revamped)". According to their public project tracking, the goal is to make Explorer a single-instance application where any folder opened from external programs is redirected into a new tab. However, this remains in the planning phase with no concrete delivery date assigned yet, and it appears to focus on Windows-native implementation rather than application-level interceptors like what Obsidian would need.
Reference: PowerToys GitHub project board (search for "File Explorer Revamped" or issue #31827)
---
**Important Distinction from Existing Requests**
This is different from:
- Obsidian Forum #76345 ("Show in system explorer does not focus explorer sometimes") — that issue focuses on **window focus problems**, not the fundamental window-vs-tab behavior
- PowerToys GitHub #36120, #21549 — these are **PowerToys Run specific**, unrelated to Obsidian's built-in context menu
- Obsidian Forum #41963 (pop-out windows sidebar limitation) — deals with secondary Obsidian windows lacking sidebars
My issue is specifically about the **right-click context menu action** within Obsidian's file explorer pane creating new Windows Explorer processes, bypassing Windows 11's native tab support entirely.
---
**Additional Context**
- This is a known limitation on Windows overall; even PowerToys has open issues requesting this behavior
- However, since Obsidian controls how it invokes `Shell.Execute()`, there may be opportunities to intercept or modify this call
- Alternatives like AutoHotkey scripts are cumbersome and not user-friendly solutions
---
**Related Feature Requests**
- "Show in system explorer does not focus explorer sometimes" — Forum thread #76345
- PowerToys GitHub issues #36120, #21549, #4528 (similar single-instance Explorer behavior requested)
---
Thank you for considering this improvement. It would significantly streamline workflows for users who frequently navigate between Obsidian and the system file explorer.