Baixar wmux 3.63.0 per a Windows

### Added

• Remote popover：**Conversation access** (phone Chat view), **Photo & file upload**, and **Dangerous launch** under a closed-by-default **Advanced** section with a warning. While the server runs, these toggles and **Allow input** apply immediately without a restart. The port, pairing token and paired devices stay the same.

• `wmux web --no-allow-input`, `--no-allow-upload`, `--no-allow-transcript`, `--no-allow-dangerous-launch`, `--loopback` and `--no-tls` turn one setting off on a re-run.

• **Decline a terminal dialog from the phone.** `POST /api/approvals/:id/decline`
(capability `terminal-prompt-decline`) sends one Esc, but only when the
daemon can prove the dialog on screen is the one the card was made for. If
it cannot, or the dialog is already gone, the phone gets 409/410 and
nothing is typed.

• **The sidebar says which pane asked for each fan-out task.** A task row now carries a muted line of its own under its name：`by <pane>` with the pane's coordinate first (click to jump to that pane), the pane's name marked `· closed` once it is gone, `Started by you`, `by Orchestrator`, or `Requester unknown`. Before, a workspace with two agent panes grouped all their tasks under one owner and the calling pane was only in a hover tooltip that could lose track of it after a daemon recovery. The requester is now recorded on the task's lineage stamp by stable pane ids, so it survives PTY rebinds and the pane being closed. Each agent row in a workspace's roster shows `N requested` for its own open tasks, and Fleet names the requester on a task's row in every section. (#1575)

• **Connect another computer from the Remote popover.** The sidebar Remote
popover's "Share this computer" section now has two cards："Connect a
phone" (the QR and code, unchanged) and "Connect another computer", which
names the device, asks whether it may type, and shows one pairing link with
Copy and a live expiry countdown. The link only works in the wmux app:
opened in a browser it pairs nothing and says where to paste it. It is
offered only over HTTPS that another machine can reach; otherwise the card
says what to turn on. Before, pairing a second computer meant reading an
address and a code across two fields. (#1579)

• **Paired-device status at a glance.** The Remote popover reads "N paired ·
M active now" with phone and computer glyphs, and Paired devices shows each
device's kind and an Active now dot. Before, the roster showed only names
and a last-seen time. (#1579)

• **Other computers in the Remote popover.** The sidebar Remote popover now
lists every computer this one has paired with, each with a status：Connected,
Reachable, Unreachable or Needs re-pairing. The list appears at once and the
statuses fill in as each computer answers, so one that is off never holds the
others up, and an unreachable computer is never sent back to pairing. Click
one to see and attach its workspaces. (#1580)

• **Pair a computer by pasting one link.** "+" in Other computers takes the
pairing link from the other computer's Remote popover (or a phone pairing
link, an address and a code, or a `wmux web` link) in a single field, with a
Paste link button. A computer that needs re-pairing is paired again in place,
keeping its attached workspaces. Before, pairing meant copying an address and
a code into two fields of a separate dialog. (#1580)

• **The phone API can draw fan-out tasks under the pane that asked for them.** `GET /api/sessions` rows and `GET /api/workspaces` pane entries now carry the desktop `paneId`, so a phone can group tabs into panes. A nested fan-out task row carries `nestedUnder` (`pane` or `closedPane`), plus `requesterPaneId` for `pane`. This matches the desktop sidebar's workspace › requesting pane › tasks tree. Before, the phone could only nest tasks under the workspace. Clients that ignore the new fields keep drawing the workspace-level nesting from `nested`. (#1583)

• **`/turns` says why an OpenCode pane is unavailable.** An unavailable body
can carry `cause` — `opencode-plugin-missing` or
`opencode-plugin-unreachable` — beside the unchanged `reason`.

• **Groundwork for answering more agent prompts from the phone.** The phone API gains an optional "decision forms" layer that a phone app turns on with a new capability：a structured answer route with retry-safe receipts, so a retried or queued answer cannot be applied twice. No prompt uses it yet. Phone apps that do not ask for it see exactly the same data as before. (#1604)

• **The receiver can drop a task with `a2a_task_update` status `canceled`.** For a superseded or informational task, the receiver now cancels it from any open state with a short reason in `evidence.summary`, as for `failed`. A background worker running the task is stopped. (#1612)

• **Phone chat can name the running turn.** A phone that declares the
`chat-cancel` or `chat-queue` capability now gets `chat.turn` on `/turns`:
an opaque id for the current running episode, whether it is running or idle,
and when it started. The id stays the same through tool calls, approval
answers and prompts typed into a running turn, and changes only when a new
turn starts. Other clients see exactly what they saw before.

• **Stop a running Claude or Codex turn from the phone.** A new
`POST /api/sessions/<id>/chat/cancel` presses Esc once in the pane's running
turn. It only presses when the agent visibly shows it is working (its
"working" row on screen, or its spinner in the window title while it is
writing out an answer), only once per turn, and never within 2 seconds of another Esc, so a late or
repeated tap cannot clear your input line or open rewind. Retrying with the
same request id replays the first answer instead of pressing again. Phones
that declare the `chat-cancel` capability now see `cancel：true` on a live
Claude or Codex chat. Other clients see exactly what they saw before.

• **Queue phone chat messages while the agent is working.** A phone that
declares the `chat-queue` capability can now send while a Claude, Codex or
OpenCode turn is running：the daemon holds the message and types it after
the turn ends, one message per turn, in order. Before, only Claude could take
a message mid-turn (into its own composer), and Codex and OpenCode refused
it as busy. Queued messages show on the chat with their state, can be taken
back with `DELETE /api/sessions/<id>/chat/queue/<clientMessageId>`, and
report each change live as a `chat.queue` event. The message text is never
written to disk, so a daemon restart cancels what was waiting instead of
typing it later. Each message is re-checked right before it is typed:
unpairing the phone, taking away its input permission, restarting the pane
or starting a new conversation cancels it rather than typing it. Phones
without the capability see exactly what they saw before.

• **Stop a running OpenCode turn from the phone.** The chat cancel route now
works for OpenCode chats：it asks the wmux plugin inside OpenCode to abort
the current session, but only while that session is actually working and
only for the conversation the phone is looking at. If a permission or
question dialog is open, or the turn has already ended, nothing is aborted
and the phone is told why. Phones that declare the `chat-cancel` capability
see `cancel：true` on an OpenCode chat once OpenCode has loaded the updated
plugin. An older plugin keeps Stop off.

• **Scheduled runs.** Pick a folder, an agent (Claude Code or Codex), an
account, days and a time, and wmux launches that agent with your prompt in
the background — no window, no OS scheduler, no scripts. Runs keep going if
the window closes; when one needs you, a desktop notification and the new
Schedules row in the sidebar take you straight to its terminal to answer.
Each schedule has its own permission mode (Approval, Scoped, or Bypass after
a confirmation), which resets to Approval whenever you change what it runs.
Finished runs keep a plain-text output snapshot and a resume command, and
their processes are cleaned up. Runs happen only while wmux is running.
(#1628)

• **Agents can draft a schedule for you to review.** An agent connected to
wmux over MCP can now propose a scheduled run — folder, agent, prompt, days
and time. The draft arrives turned off, in Approval mode, with a desktop
notification and a Proposed badge in the Schedules view; nothing runs until
you review it and turn it on. Agents can also read schedule and run states,
without prompts, folders or accounts. (#1630)

• **Answer Claude's plan dialog from the phone.** When Claude Code asks
"Would you like to proceed?" with a plan (ExitPlanMode), a phone that speaks
the decision-v2 wire can approve it (manual edit approval) or send feedback
that makes Claude plan again, with the whole plan readable first. Before,
the card only said the pane was waiting, and the only remote option was to
cancel. Feedback is typed into the dialog's own field, checked on screen
and submitted. If someone types at the terminal meanwhile, the phone is
told the answer was only partly typed and nothing more is sent. Rows that
would switch Claude to auto or bypass mode are never offered. The shipped
iOS app keeps showing the plain card.

• **Answer OpenCode permissions and questions from the phone.** Each pending
OpenCode permission and question is now its own phone card. That includes a
sub-agent's request, which the desktop TUI draws on the session you are
viewing. The answer goes through OpenCode's own server, so the prompt closes
in the terminal and nothing is typed into the pane. A phone app that has not
been updated answers a permission with its usual Yes/No. An updated app can
also answer multi-question and multi-select questions, including a typed
answer. "Allow always" is never offered from the phone. Before this, an
OpenCode