Skip to content

Move connecting to the Machines page and pair in one step - #511

Merged
Tryanks merged 1 commit into
mainfrom
ui/remote-connect
Sep 23, 2026
Merged

Tryanks merged 1 commit into
mainfrom
ui/remote-connect

Conversation

@Tryanks

@Tryanks Tryanks commented Sep 23, 2026

Copy link
Copy Markdown
Owner

Why

Settings → Other devices mixed this machine's hosting configuration with the act of connecting, and pairing took three screens: the scanned link landed in a text field, a blank confirmation page showed the machine name, and a second button finally connected. The Chinese locale had also drifted from 主机 to 机器 in a WIP commit.

What

  • Settings → Remote (renamed) only configures: endpoint on/off, accept new devices, machine name, Traverse, paired devices.
  • Machines page is where connections are made in both directions: this machine's invitation (QR, countdown, copy link, new invitation) while hosting accepts devices, with the reason and a link to settings otherwise; the saved machines; adding by scan or pasted link.
  • One-step pairing: a scanned invitation or a pasted link that parses is sent immediately, the page shows "Connecting to ‹name›…", and success saves and switches. Confirmation page and "Connect to ‹name›" removed; the bottom button only retries.
  • Sidebar Machines row shows the name and status light only while connected to a remote machine.
  • 机器 → 主机 throughout; README, docs/remote.md, traverse-server README and headless help text follow the new names and flow.

Verified

cargo fmt --check, workspace clippy -D warnings, all tcode-ui and headless tests, --no-default-features build; desktop Machines/Settings pages and the phone layout checked by screenshot.

Settings → Other devices mixed two things: this machine's hosting
configuration and the act of connecting. It is now Settings → Remote and
only configures: whether the endpoint runs and accepts new devices, the
machine name, Traverse, and the paired devices. The Machines page in the
sidebar is where connections are made in both directions: it shows this
machine's invitation (QR, countdown, copy link, new invitation) while
hosting accepts devices, explains why not and links to the settings
otherwise, and lists the saved machines with adding by scan or pasted link.

Pairing is one step. A scanned invitation, or a pasted link that parses,
is sent at once and the page shows "Connecting to ‹name›…"; the
confirmation page and the "Connect to ‹name›" button are gone, and the
bottom button only retries after a failure. The sidebar's Machines row
shows the machine name and status light only while connected to a remote
machine. The Chinese locale returns to 主机 for Machine, which the rest of
the app already used. README, docs/remote.md, the traverse-server README
and the headless help text follow the new names and flow; the claim that a
paired native device can mint an invitation for a headless machine was
never true and now reads as browser-only.
@Tryanks
Tryanks enabled auto-merge September 23, 2026 04:31
@Tryanks
Tryanks merged commit fc72da7 into main Sep 23, 2026
7 checks passed
@Tryanks
Tryanks deleted the ui/remote-connect branch September 23, 2026 04:48
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.

1 participant