Baixar wmux 3.38.4 per a Windows

Added
- The multiview grid can be stacked vertically. Settings → Layout now has a
Multiview arrangement control with three choices. Auto keeps the old
behavior — two workspaces side by side, four in a 2×2 grid, five or more in
three columns. Columns puts every workspace in one row, and Rows stacks
them in a single column, which is what you want on a tall display or when the
tiles are agent transcripts that read better narrow. Before this, four
workspaces were always 2×2 and there was no way to say otherwise. Arrow-key
navigation between tiles follows the arrangement you picked, and the choice
survives a restart. (#748)
Changed
- Critical-action notifications now show the matched terminal line. The
critical attention event carries matchedLine — the printed terminal
output that tripped the pattern, sanitized and capped — so a heads-up can
say git push --force origin main instead of just "git push --force". (This
is the text the terminal displayed, which may quote a command rather than run
one; it is not proof the command executed.)
- Documented that the critical signal is notify-only: it fires on printed
output, not on a pending action, and is not something a remote surface can
answer. Approvals remain the only answerable signal.
Fixed
- Scoped MCP browser fallbacks to their calling workspace. Browser tools no
longer let automation leases, CDP discovery, or RPC fallbacks select another
workspace's webview when the intended target is missing or ambiguous. (#749)
- Closing a workspace no longer leaves multiview in a broken state. Closing
members of a multiview group from the sidebar could leave the app showing a
single tile still wrapped in multiview chrome, with no way back except
Ctrl+Shift+G. The closed workspace is now dropped from the group, and the
group disbands once fewer than two members remain. (#753)
- Ctrl+click on the workspace you are looking at no longer closes the whole
grid. Removing the active workspace from a multiview group took every other
tile with it. Focus now moves to a neighbouring tile first, the way the tile's
own ✕ button already behaved. (#753)
- Resizing while text is selected no longer leaves the terminal at the wrong
size. If you selected some output and then resized — dragging a split
separator, toggling the sidebar, resizing the window — the terminal and the
shell behind it stayed at the old dimensions even after you cleared the
selection. Output wrapped at the wrong column and full-screen programs drew
against stale dimensions until something else happened to resize the pane. The
deferred resize now runs as soon as the selection goes away. (#754)
- LanLink halved the disk writes a received message costs. Each inbound record used
to force two full rewrites of the peer file, and on Windows every rewrite shelled out
to whoami.exe and powershell.exe to re-apply the owner-only file permissions — a
step measured at seconds per call on machines running antivirus, and one that blocked
the whole daemon while it ran, so a peer sending a burst of messages could stall wmux.
The "last seen" timestamp now rides along with the write the record already needed,
instead of forcing one of its own. The remaining write is the replay guard, which has
to be durable; making that one cheap on Windows is still open. (#755)
- Panes no longer flicker and settle black after a WebGL teardown. When
xterm's WebGL addon was disposed (pane hidden, tab switch, font reload) and
an internal step threw mid-dispose, the addon's own "hand back to the DOM
renderer" step was silently skipped — leaving the pane with no renderer at
all. Every render tick after that (cursor blink, scroll, resize) threw, so
the pane flickered and then stayed black until relaunch. Teardown now
verifies a renderer survived and restores the DOM renderer itself when it
did not. (#759)
- Browser navigation no longer reports a transport timeout for a DNS
failure. The navigation guard's DNS lookup was unbounded, so a slow or
unresolvable hostname outlived the caller's RPC deadline and surfaced as
RPC timeout: browser.navigate — naming the pipe instead of the actual
problem. The lookup is now bounded and reports the DNS failure itself.
(#756)
- browser_navigate returns once the page commits, rather than after every
subresource has finished loading, so a slow page no longer keeps the call (and
the automation lease) open past the caller's deadline. A navigation that
genuinely fails is now reported instead of being retried through the renderer
bridge and answered as a success. (#756)
- Browser tools say which kind of "no target" they hit. BROWSER_NOT_OWNED
(the surface belongs to another workspace — never retry) and
BROWSER_NO_TARGET (this workspace has no browser open — open one) replace a
single message that covered both. (#756)
- Dead panes now reopen in their original working directory. Renderer-
created replacements inherit the dead session's validated spawn directory,
fall back to its last live directory and then home, and retain any surviving
agent resume offer. (#762)
What's Changed
- Let the multiview grid be arranged vertically by @openwong2kim in #748
- Keep multiviewIds consistent when members go away by @openwong2kim in #753
- Settle a fit deferred by the selection guard by @openwong2kim in #754
- fix(lanlink): coalesce lastSeenAt writes off the receive path by @openwong2kim in #755
- fix(mcp): scope browser RPC fallbacks by workspace by @snowyukitty in #749
- Bound the navigation DNS guard so a slow host is not a transport timeout by @openwong2kim in #760
- fix(push): 잠금화면 승인 버튼이 실제로 뜨게 한다 by @openwong2kim in #761
- fix(renderer): restore the DOM renderer when WebGL teardown skips xterm's own restore by @openwong2kim in #759
- Say which command tripped the critical signal, and write down that it is notify-only by @openwong2kim in #757
- Recover dead panes in their original working directory by @snowyukitty in #762
- chore(release): 3.38.4 by @openwong2kim in #763
Full Changelog: v3.38.3...v3.38.4