Repository navigation
[Feature]: Add remote support #8
Description
Activity
Cross-linking PR #38 because it may address one important part of this request.
#38 does not implement a
--remotemode, tunneling, NAT traversal, or a tailcat-style transport. What it does add is a supported opt-in way for a non-loopback client to reach a PAIR compatibility endpoint with an API key, plus an optional source CIDR allowlist.That means a remote/tunnel layer such as llmbeam could treat PAIR as a backend without needing to run a loopback relay beside PAIR. In other words, #38 covers the “PAIR can be safely used from outside the node” piece, while the actual remote transport remains separate work.
I am going to close this as a duplicate. We have a number of other requests asking for tailscale which we plan to include when we can. ex. #85
Area
Discovery or pairing
User problem
I developed a somewhat similar product here https://github.com/llmbeam/llmbeam
I used tailcat to connect my server to my phone/laptop. I wonder if Personal-AI-Router can support the remote connection feature. If not, one thing I can do is to treat Personal-AI-Router as one backend of llmbeam
Desired outcome
support something like
--remoteAlternatives considered
No response
Compatibility and security implications
No response
Validation approach
No response
Confirmations