Repository navigation
feat: one Connections page, and pairing connects both ways - #69
Merged
Merged
Conversation
…link Add a device replaces Create link: it makes a one-time code at once and shows a QR and a link that carries this machine's reachable address, plus two switches (use chats there, let its agents run work here) that ride in the link. Label and permissions move behind More options. Add a machine takes that link (or a code plus address), names this machine to the host, and with the agents switch on also links this machine's agents to the new one by minting the second code over the new connection, so nobody types a second code. The section is now Who can use this Mac, devices show Signed in or Signs out <date>, and the idle limit is a 30 or 90 day toggle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Environments is now Other machines. Each row says what the machine is used for with two labeled switches: Show its chats and projects here (the old unlabeled switch) and Agents here can run work there, which links or unlinks this machine's agents without a second code. Machines linked only for agents sit in the same list, so Linked environments no longer has its own section for this machine. Routes and Permissions moved into the row's menu. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sharing & access now opens on This Mac with a How other devices reach this Mac group: Tailscale (marked Working with its address) and Local network (formerly Network access, which says plainly when Wi-Fi devices cannot reach it), then T3 Connect. Display name, version, WSL and permissions follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Minting the agents' link code waited for nothing, so right after Add a machine it failed with the machine still connecting. It now waits up to 15 seconds for the connection. The agents switch only shows when Linked environments is on, since the server refuses links otherwise. Another machine's own empty Linked environments section is hidden. The settings page is called Other machines. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ect with no pairing code Ports pingdotgg#26757 (head 23b1188) onto Ctrl. Ctrl-specific choices: - The auth_tailnet_device_blocks table is Ctrl migration 9, not upstream's 078, since 78 is taken in Ctrl's copy of upstream's ledger. CREATE TABLE IF NOT EXISTS keeps upstream's migration a no-op when it lands. - Link-paired sessions keep Ctrl's sliding renewal; Tailscale DPoP sessions follow upstream (1 hour, renewed by rerunning the checks). - Upstream's Tailscale Serve switch, route status and sign-in switch live in Ctrl's "How other devices reach this Mac" card. The Tailscale row says Working whenever Serve answers as this machine, however it was set up. - Learned routes keep upstream pingdotgg#29432's live config stream, without the better-route switching pingdotgg#26757 removes. Co-authored-by: maria-rcks <maria@kuuro.net> Co-authored-by: Tin Zeljar <35663757+Zheruel@users.noreply.github.com> Co-authored-by: Julius Marminge <julius0216@outlook.com> Co-authored-by: Victor <263261067+only21mil@users.noreply.github.com> Co-authored-by: tiliakoos <73005126+tiliakoos@users.noreply.github.com> Co-authored-by: Srivishal Sivasubramanian <47695678+root-daemon@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tailscale sign-in and tailnet discovery look for a server on one fixed port. With T3 Code and Ctrl on the same machine, T3 Code holds 3773, so Ctrl would have found and added T3 Code servers as Ctrl machines, and which app got 3773 depended on which started first. Ctrl's server, desktop app, Tailscale sign-in, discovery probe and SSH default now use 3774. Add a machine on desktop lists the T3 machines on your tailnet that are not saved yet; picking one fills its address, and with no code it signs in through Tailscale when that machine allows it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sharing & access and Other machines were two pages for one idea. Connections is now one page, top to bottom: this machine and how other devices reach it, who can use it (open by default), then the other machines this app uses. The old /settings/access address and its anchors land on Connections, and every message and doc that said Sharing & access now says Connections. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A machine linked only for agents fills Other machines too, so the empty state no longer shows under it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ch computer once Add a machine now leaves the other machine a pairing link back (Connect both ways, on by default). The link carries this machine's reachable address and a code valid for a day; the other machine keeps it in memory and its app takes it within a minute of opening and connects back, so neither side types a second code. New RPCs connectionOffers.offer and .take need access:write; pairing codes can now ask for a lifetime of up to a day. Other machines is now Connected machines. A computer that is also signed in to this machine shows that sign-in on its row, with Sign out, and leaves the device list, which keeps phones, browsers and other devices. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After scanning a computer's QR in the phone app, Add environment lists the computers the phone is connected to under Or connect one of your computers to it. Picking one leaves it the scanned link as a connection offer that asks to connect back; its app connects to the scanned computer within a minute and then offers it the connection back, so nothing is typed on either computer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Connect both ways waits for the new machine's connection before leaving its link back - Only this machine's own app takes connection offers; saved machines stay as they are unless a phone relay asks - Tailnet discovery skips this app's own machine; phone relay only for scanned codes, with a timeout - Stale "Sharing & access" and "Environments" wording now says Connections; route-upgrade docs match the port Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Connections was split across two pages, and connecting two computers meant reading a code off one and typing it into the other, and then doing it again the other way. This builds the simpler flow from the Connections design.
What changed
Review
Local reviewloop: 5/5 after 3 reviews, with all findings fixed.
Not tested live yet
These need two real Macs and the phone on a release build:
vp run check:changedpasses apart from two failures that also fail on main: the push-relay workers-types typecheck and theServerEnvironment/private/vartest.Done by Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code