Baixar wmux 4.3.0 per a Windows

### Added

• **Point an agent at a pane by its name：`#w1-2` or `#backend`.** Every pane already shows a unique name in its header (`w1-2`, plus the agent running in it) or the name you gave it. Type that name with a `#` to an agent and it can pass it straight to the wmux tools — `terminal_send`, `terminal_read`, the `pane_*` tools and `send_message` (as `to`, `pane_id` or `surface_id`) all accept it where they used to need a long pane, surface or terminal id. Before, targeting a pane meant pasting a block of ids from the pane header. `pane_list`, `a2a_discover` and `a2a_whoami` now report each pane's `paneName` and `paneTag`, and a name only reaches what its ids could, with the same checks. (#1954)

• **Dragging a pane header into a wmux terminal types just its tag.** Drop the pane header on a terminal and it inserts `#w1-2 ` instead of the full block of ids, ready for the prompt you are writing to an agent. Dropping it on another app still gives the full description, which now also lists the pane tag (and the pane's name when you named it). (#1954)

• **Dismiss a question that needs no answer.** When an agent ends its turn on a question you don't need to answer, right-click its workspace in the sidebar or open the row's menu in Fleet and choose **Dismiss question**：it stops counting as Needs you, and stays dismissed after a restart. Approval and permission prompts still wait for you. (#1957)

• **Connect a PC… on the Remote page.** One dialog covers both ends. On "Invite this PC" it turns cross-PC A2A on if needed, then creates and copies the invite, marking the tailnet address. As soon as the other PC joins, it asks what that PC may see. On "Paste an invite" it accepts an A2A invite, a pairing link, a `wmux web` address with its token, or an address and a code. Opening the dialog changes nothing, and the clipboard is read only when you press Paste. Before this you had to pair PCs from Settings › LAN.

• **Kitty keyboard protocol in terminal panes (macOS and Linux).** wmux now answers the kitty keyboard query, so Claude Code switches to the protocol inside wmux. Codex's request for the protocol now takes effect too. Once an app has asked for it, Shift+Enter, Escape and Ctrl+letters reach the app exactly as it expects instead of through wmux's workarounds. Before, an app either never asked or got a mix of encodings. Korean and other IME input is unaffected：the key that picks an IME candidate no longer leaks into the app next to the committed text, a known xterm.js issue that wmux works around here. An app that exits without switching the protocol back off no longer leaves the shell receiving encoded keys. Windows keeps the previous behaviour for now. (#1963)

• **Pane names now work in channel mentions and Moa hand-offs too.** A channel post's mention can pin a pane with `#w1-2` or `#backend` instead of its pane id, and Moa can hand work to `#backend` instead of looking up the terminal id first. These were the last two places that still needed the raw id after pane names became addresses.

• Connect a PC's invite can also let the other PC see this PC's workspaces. Tick the new box, and the copy holds the invite plus a view-only pairing link on a second line. The box is off by default and offered only while Share & pair is on over HTTPS. The other PC pastes once and both connect.

• **Groundwork for pushing, opening PRs and merging from the phone.** `wmux web`
gains `--allow-git-write` (off by default) and `--git-write-login <login>`, the
host-side switch and GitHub account for upcoming phone push, PR creation and
squash merge. The gate needs an input grant that was set explicitly for the
device, push and merge need a fresh preview and a single-use confirmation,
and every request leaves a receipt kept for 72 hours so a resent request never
runs twice. No action is served yet, and the phone is not offered any of them
until it is.

• **Scheduled runs can use Claude's auto mode, and new schedules run unattended by default.** A new Claude schedule now starts in Auto, where Claude approves routine actions itself and stops risky ones; a new Codex schedule starts in Scoped (its workspace sandbox). Before, every new schedule started in Approval and could sit on a Claude safety prompt with nobody at the desk. Saving an Auto schedule asks you to confirm in a native dialog, as Bypass already did. Unattended runs (Claude Auto and Bypass, Codex Scoped and Bypass) start without wmux's own MCP tools.

• **The phone can open and squash-merge pull requests.** With
`wmux web --allow-git-write`, the daemon now serves `pr.create` and
`pr.merge`. Opening a PR checks that the branch is pushed and has no open PR
yet. Merging shows the facts first (head, mergeability, checks, and which
required checks fail or are pending when GitHub reports them), then merges
exactly the head that was shown, one merge per PR at a time. A merge whose
outcome cannot be read back is reported as uncertain and is never retried on
its own. Before this, these routes answered 501.

• **Push from the phone.** With `wmux web --allow-git-write` on, a phone with an
explicit input grant can push a session's branch to its upstream on GitHub.
It first shows a preview of the target, the commits and whether the push is a
fast-forward. The push sends exactly the commit that was shown and never
forces. It refuses the repository's default branch and any remote that is not
HTTPS github.com. Before, pushing meant typing `git push` into a terminal.

• **Groundwork for a column of paired computers.** The shapes, rules and translated strings a later release uses to list every web-paired computer beside the page rail, with its own workspaces and attention badge. Nothing changes on screen yet. (#1989)

• **Live feeds for paired computers.** wmux can now keep every web-paired computer's workspace list and attention counts current：each one is checked every 10 seconds on its own, and a computer that stops answering is retried less often. An approval that starts waiting on another computer shows up at once. A muted computer still updates its badge but shows no notifications. Nothing changes on screen yet; the sidebar's computer switcher that shows this comes in a later release. (#1992)

• **The Git page's All repos list says whose turn each item is.** The flat list across repos is now split into Needs you, Ready to merge, Agents on it and Waiting on others, newest first within each, with a count on every section and a summary line under the title that jumps to a section. Needs you and Ready to merge start open; the other two start folded and remember how you left them. The turn comes from wmux's own signals (the PR's checks, conflicts and review, and whether an agent pane is working on it), because agents open PRs under your own GitHub account. Another author's PR, or an issue nobody has picked up, counts as yours to act on only in repos you can write to, so an upstream project you do not maintain no longer floods Needs you, and a mergeable PR in a repo with no CI shows as ready to merge. (#1995)

• **Keep memory and CPU in the titlebar.** A new setting, "Always show memory and CPU", keeps both chips visible at every reading. Before, they appeared only once memory use grew large, so on an ordinary session you never saw them. It is off by default. (#2000)

• **Bookmark workspaces and filter the sidebar to them.** Right-click a
workspace and choose Bookmark (or use "Toggle bookmark for this workspace"
in the command palette) to mark it with a small ribbon. Then turn on
Bookmarked only in the sidebar filter to see just those workspaces, along
with their fan-out tasks. Until now the only way to keep a few workspaces in
reach was Pin to top, which also changes their order. Bookmarks never move a
row and are kept with your session. (#2002)

• **The Git page's Worktrees tab says what each worktree needs.** Worktrees are sorted into In use, Uncommitted changes (no workspace, but changes on disk), No open PR, Cleanup candidates (now including a worktree whose PR is merged, once its tree is clean and no agent is working there) and No workspace. A summary line under the title jumps to a section. Before, the tab only said whether a workspace sat on a worktree. A row that asks something of you can be snoozed for an hour, a day or a week, or until it changes. It waits in a folded Snoozed group and comes back early if it gets a new commit or new edits. Snoozes are remembered across restarts. The tab makes no extra GitHub calls：it uses the PR lists the page has already read. (#2006)

• **Pairing says what a paired device can reach.** Share & pair, Paired
devices and Connect a PC now state that a paired device can read and
search every workspace, including later ones; that view only can still
answer single-key prompts on screen; and that typing also covers opening
and closing sessions and answering approvals. (#2009)

• **Pages say when they show this computer only.** With another computer
selected in the sidebar's computer switcher, Fleet, Schedules and Git show one muted
line, "This computer · office-mac isn't shown here yet"; what they list is
unchanged. Git's This repo and the file tree say "Files on office-mac aren't
shown yet" instead of reading that computer's folders from this disk, and a
pane's new-browser action reads "Browser (this computer)". (#2011)

• **Browser actions wait for the page to catch up.** After a click, typing,
a form fill, a key press or a select, the agent's next snapshot now shows
what the action did. If the action starts page requests (documents,
scripts, styles, XHR or fetch), wmux waits for them, or for the new page to
load when it navigated, for at most 5 seconds. An action that starts none
within 100 ms returns as before, and images, beacons and background polling
never add a wait. Before, a snapshot taken right after a click that loaded
data often still showed the old page.

-