Baixar wmux 3.29.0 per a Windows

Fixed
- Typing stays responsive — and Hangul/CJK composition no longer truncates — while an agent floods a visible pane. A TUI redraw is a burst of tiny cursor-move writes, and handing each one to the terminal separately made the GPU re-rasterize the whole grid dozens of times a second; while a frame was held for paint, keystrokes and IME composition events queued behind it, so fast typing dropped characters and "했습니다" could land as "했". wmux now honors the terminal's own frame markers (DEC mode 2026 synchronized output, which Claude Code and Codex emit): it holds a frame's intermediate writes out of the renderer and releases them in one shot when the frame closes, so the GPU paints once per redraw instead of once per fragment. A frame that opened right after a keystroke is treated as latency-sensitive and released within a frame or two, so your own echo always paints ahead of an agent's autonomous output. Windows ConPTY only for now.
- Switching workspaces no longer stutters when a hidden pane piled up a large scrollback. A pane that streamed output while hidden handed its whole backlog to the renderer in one parse on reveal, spiking the GPU across several frames. A large backlog from a daemon-backed pane is now re-synchronized from the daemon as a bounded screen snapshot instead of replayed in full, and a backlog that can't be re-synchronized is drained over frames rather than in one burst — so a switch stays smooth without ever dropping or losing output.
Added
- Notifications can be muted per category instead of all-or-nothing. Every notification now carries the kind of event that produced it — agent turn finished, subagent finished, awaiting approval, terminal (OSC 9/99/777), system/external — and Settings → Notifications has a switch per category. Before, the only knobs were global sound/toast/ring toggles, so quieting subagent chatter during parallel work also silenced the "awaiting approval" signal that actually needs you. Muted categories still land in the notification panel; only toast, sound, pane ring, and taskbar flash are suppressed, the same contract a muted workspace already had. Nothing is muted by default, and a notification whose source can't classify it is never suppressed by a category mute. The mute is honored even when wmux has no live window — the muted set is mirrored to the main process, so a category you turned off can't come back as a desktop banner while the app sits in the tray. Subagent-vs-main-agent classification comes from the Claude Code hook bridge; the text detector can only distinguish approval prompts from turn ends, and the Settings copy says so. (#516)
Fixed
- A single failing installer step no longer discards the platform's whole release. Forge builds makers in sequence and stops at the first failure, so when the macOS DMG step hit a transient hdiutil detach error during v3.28.1, the upload step never ran — and the runner was thrown away with a perfectly good .zip still on it. That zip is what backs the auto-update feed, so one flaky maker silently took out both the download and auto-update for macOS until the job was re-run. Both the macOS and Linux upload steps now run regardless of whether the build step failed, publishing whatever artifacts did get made.
- macOS: panes get the shell environment you actually have. zsh was started interactive but not as a login shell, and on macOS the standard PATH is assembled by /etc/zprofile — a login file that runs path_helper. So a pane inherited whatever PATH the app was launched with (launchd's minimal one for a GUI launch) and lost /opt/homebrew/bin, /usr/sbin, /sbin, /Library/Apple/usr/bin and every /etc/paths.d entry. .zshrc still ran, which is why the shell looked fine right up until an unqualified Homebrew command failed. Panes now start a login shell on macOS, matching Terminal.app, iTerm2 and VS Code. The .zprofile/.zlogin stubs that delegate to your real files already existed — they were simply never read. (#519, reported by u/DauntingPrawn)
- New and respawned terminal panes now honor the workspace's startup directory instead of landing in your home folder. When a pane's shell had to be re-created (a recovered session, a rebind failure, or a dead-session respawn), it ignored the workspace's configured startup directory and fell back to home — and once a pane lived in home, every split off it inherited home too, so the corruption spread and never healed. A respawn now resolves its directory as profile.startupCwd → the pane's own tracked directory → the global startup-directory setting, with the workspace default taking priority so a pane that drifted to home is corrected the moment it respawns. New tabs (Ctrl+T, command palette), MCP-created surfaces, and Git-tab "Open worktree"/"Open conflict" now all adopt the directory the shell actually started in, and a workspace opened with a startup directory attaches it before its first pane spawns. A [pty:create] log line records each pane's resolved directory and why, so future reports are diagnosable from the logs. (#515)
- ~/… works wherever you can pass a directory. Tilde expansion is a shell feature, so a working directory arriving through the CLI, an MCP tool or the RPC layer was never expanded by anything — ~/projects/foo stayed literal — so the pane either opened silently in your home directory (where the code checks the path first) or came up dead and blank with no error at all (where it doesn't: the shell exits 1 immediately on an unreadable cwd). It now resolves at both spawn paths. ~otheruser is left alone rather than silently mapped to your own home. (#520, reported by u/DauntingPrawn)
What's Changed
- ci: publish artifacts even when a maker fails; raise the peer cap-loop timeout by @openwong2kim in #518
- fix: start a login shell on macOS and expand ~ in caller-supplied cwds by @openwong2kim in #521
- fix: new/respawned panes honor startupCwd instead of falling back to home by @openwong2kim in #523
- feat(notifications): per-category mute (#516) by @openwong2kim in #522
- feat(sidebar): add folder picker for workspace creation and workspace search by @rayss868 in #524
- perf(terminal): coalesce DEC 2026 synchronized output and bound reveal catch-up by @openwong2kim in #525
- chore(release): 3.29.0 by @openwong2kim in #527
New Contributors
- @rayss868 made their first contribution in #524
Full Changelog: v3.28.1...v3.29.0