Skip to content

feat: show shell-specific labels for terminal tabs#3

Merged
amirlehmam merged 1 commit into
amirlehmam:masterfrom
Optuber01:pr/shell-tab-labels
Apr 15, 2026
Merged

feat: show shell-specific labels for terminal tabs#3
amirlehmam merged 1 commit into
amirlehmam:masterfrom
Optuber01:pr/shell-tab-labels

Conversation

@Optuber01

@Optuber01 Optuber01 commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • return the resolved shell from PTY creation
  • store the resolved shell on terminal surfaces
  • show a shell-specific tab label instead of the generic Terminal label

Why

When multiple terminals are open, shell-specific labels make it much easier to understand which tab is PowerShell, Command Prompt, Bash, WSL, or another shell.

Testing

  • npm run build:main
  • npm run build:renderer

@amirlehmam amirlehmam merged commit c005a86 into amirlehmam:master Apr 15, 2026
@amirlehmam

Copy link
Copy Markdown
Owner

Great PR! Clean implementation, well-structured across all the layers (pty-manager → ipc → preload → renderer).

The getShellLabel() mapping is a nice touch — much better UX than seeing "Terminal" everywhere when you have multiple shells open.

Merged into v0.6.8. Thanks for the contribution @Optuber01!

amirlehmam added a commit that referenced this pull request Jun 15, 2026
…ick-launch profiles, winget) + bump 0.8.6

#1 Notification sounds: ship a default chime and play it on every notification
   fire, gated on notificationPrefs.sound. Main signals notification:play-sound;
   a single renderer listener (initNotificationSound) plays the bundled WAV.

#3 wmux browser new-instance bug: add app.requestSingleInstanceLock() with a
   second-instance focus handler so a stray `wmux ...` launch focuses the running
   window instead of spawning a new one (named WMUX_INSTANCE isolates userData so
   dev/prod still coexist). Rebuild resources/cli/wmux.js so the shipped CLI honors
   WMUX_PIPE again.

#4 Quick-launch profiles in the + caret dropdown: {name,icon,type,shell,cwd,
   startupCommands,url} model, global profiles in settings (with a Profiles panel
   + Windows Terminal profile import) and project-level .wmux.json. PTY startup
   commands run once on fresh creation; relative cwd resolves against the workspace.

#2 Winget: manifest set + auto-publish workflow (portable-zip install, no signing).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants