Repository navigation
feat(server,client-runtime): apps open any of my devices without a code - #173
Merged
Merged
Conversation
The app asks the server it is connected to, which asks the other device over its device session for a one-time pairing credential within that device's policy. The app then redeems it at the first address that answers as that device and connects directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
jayleaton
marked this pull request as ready for review
October 30, 2026 10:58
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.
Opening another of my devices from the app still needed a pairing code, even when the two servers were already linked as tailnet devices.
tailnetDevices.openDevicenow asks the device over the device session this server already holds there (POST /api/tailnet-devices/client-credential). The device authenticates that session like sync does, so a revoked device or a caller without the session gets nothing minted. It returns a one-time pairing credential and its own tailnet addresses. The credential's scopes follow the caller's current access there: full access gets the standard client scopes. Anything lower opens read-only, because app sessions carry no agent mode ceiling. A 401 re-runs the handshake once, and the answer must name the device that was asked.In client-runtime,
ConnectionOnboarding.registerDevicespends the credential only at the first address whose descriptor answers as that device, and then pairs as usual.The UI hookup belongs to Doug C's
feat/linked-devices-rows, which already owns thetailnetDevicesatoms.Tests:
Opus 5.5 via Claude Code (Doug B)
🤖 Generated with Claude Code