You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Re-add "Open in external editor" to the new TUI #30135
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Feature: Re-add "Open in external editor" / "Open in..." to the new TUI
After the TUI rewrite (Go+Bubbletea → OpenTUI/Zig+SolidJS), the context menu option "Open in..." / "Open in external editor" was removed.
This feature was very useful on Windows for quickly opening files from the session list in external editors (VS Code, Notepad++, etc.). The old TUI had it as a right-click context menu option.
Would be great to have it back, ideally configurable to list which editors to show (e.g., "Open in VS Code", "Open in Notepad++").
🔍 Relation to Existing Issues
Note for maintainers: I reviewed the automated duplicate suggestions. While this is closely related to #29930, that issue specifically focuses on macOS desktop v2 restoration. This request focuses on the Windows environment and proposes a specific enhancement: making the external editors fully configurable via settings (allowing multiple options like VS Code and Notepad++ to appear in the menu), which is not explicitly covered in #29930.
The issue title is incomplete — it reads [FEATURE]: with no actual title text. Please add a descriptive title (e.g. [FEATURE]: Re-add "Open in external editor" to the new TUI).
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
The issue title is incomplete — it reads [FEATURE]: with no actual title text. Please update the title to something descriptive, for example: [FEATURE]: Re-add "Open in external editor" to the new TUI.
Thanks for updating the issue description — the content looks good. However, there is still one thing that needs to be fixed:
The issue title is still incomplete. It currently reads [FEATURE]: with no descriptive text after the colon. Please update the title to something like:
[FEATURE]: Re-add "Open in external editor" to the new TUI
Once you update the title, this issue will be marked as compliant.
Thanks for updating the issue — it now looks great! The title is descriptive, the feature request template is properly filled out, and the description clearly explains the problem and what you'd like to see. The needs:compliance label has been removed.
Activity
github-actions commentedon May 31, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:with no actual title text. Please add a descriptive title (e.g.[FEATURE]: Re-add "Open in external editor" to the new TUI).Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
@mention popup.If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon May 31, 2026
This issue still doesn't fully meet our contributing guidelines.
What still needs to be fixed:
[FEATURE]:with no actual title text. Please update the title to something descriptive, for example:[FEATURE]: Re-add "Open in external editor" to the new TUI.Please edit the issue title to address this.
github-actions commentedon May 31, 2026
Thanks for updating the issue description — the content looks good. However, there is still one thing that needs to be fixed:
The issue title is still incomplete. It currently reads
[FEATURE]:with no descriptive text after the colon. Please update the title to something like:Once you update the title, this issue will be marked as compliant.
[-][FEATURE]:[/-][+][FEATURE]: Re-add "Open in external editor" to the new TUI [/+]github-actions commentedon May 31, 2026
Thanks for updating the issue — it now looks great! The title is descriptive, the feature request template is properly filled out, and the description clearly explains the problem and what you'd like to see. The
needs:compliancelabel has been removed.simonklee commentedon Jun 24, 2026
This specifically isn't on our roadmap AFAIK, but i think you can implement this with a plugin now if I'm not mistaken.
kazuyabr commentedon Jun 24, 2026
Which plugin?