You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
idea: all the owner's devices reach each other (Tailscale everywhere, one roster, always-on laptop) #891
idea: all the owner's devices reach each other, without thinking about it.
What the owner asked: every device they link (the agent machine, a desktop PC, a laptop, an always-on laptop, the phone) can reach the others, only through proper means, only while online, secure and limited to the owner's own devices. "I don't want to have to think about it, I just want it to work." No per-device lists.
Direction (not designed yet):
A private tailnet is the boundary: the owner's devices only, device approval, ACLs; T3 only through tailscale serve, never public.
One roster on the anchor machine: pair a device once and every other device learns it; remove it once and it is gone everywhere; per-device credentials, never shared secrets.
Offline devices are shown, never chosen for new work, and reconnect by themselves.
Adding a device always needs the owner's approval on a device they already trust; agents can never add one.
Every T3 machine moves to Tailscale HTTPS. T3 Connect stays on beside it until every machine has a tested Tailscale route; turning Connect off is a step the owner confirms.
A 24/7 headless Linux laptop joins as a T3 server and agent worker (no CI runners there: agents hold the owner's logins).
A spare laptop is the test bed before the live T3 moves to a new host layout.
Check what upstream already offers for Tailscale and moving threads between machines before building anything.
Design the roster (one list, pair once), then split it into PRs.
Done when: a new device is paired once with the owner's approval and every other device can reach it, with no per-device setup.
changed the title [-]idea: all the owner's devices reach each other (Tailscale everywhere, one roster, 24/7 laptop)[/-][+]idea: all the owner's devices reach each other (Tailscale everywhere, one roster, always-on laptop)[/+]on Nov 22, 2026
Activity
scuttletoby commentedon Nov 22, 2026
Open owner question on whether to build a fork roster at all, or rely on Tailscale and upstream for now: #903
🤖 Generated with Claude Code
[-]idea: all the owner's devices reach each other (Tailscale everywhere, one roster, 24/7 laptop)[/-][+]idea: all the owner's devices reach each other (Tailscale everywhere, one roster, always-on laptop)[/+]