Remote control.
Keep control.
Manage your LLM sessions from the mobile app, through a private relay you own. Claude Code, Codex, Gemini CLI, Antigravity, opencode, goose, prime-agent and llm keep running on your computers. Read the terminal, send a message, or add a file to a draft. The relay carries encrypted traffic; your agents keep using their own tools and providers.
$ ptln relay setupPrivate gateway setup requires CLI v0.113.0 or later. The mobile app pairs separately with each computer.
how it works
keep your sessions running
Run your supported agent sessions in Partyline on your computers. The relay is independent of the model; you do not configure a separate remote-control service for each engine.
connect through your own relay
Use a self-hosted relay: the built-in Go gateway or a Cloudflare Worker in your account. Join each computer after approval. Discovery helps find a gateway; it grants no access by itself.
open the mobile app
Pair separately with each computer, then read its sessions, chat and send input from your phone. Keep the computers and gateway awake and their HTTPS route reachable.
what you're wondering
sovereign LLM management: which models can I use?
Choose hosted frontier models, open-weight models through a provider, fully local models, or your own compatible endpoint. Configure providers and credentials in each engine. Partyline manages the sessions; the relay transports encrypted content. Using a private relay does not make a hosted model local.
how do I run local models?
Use an engine configured for your local runtime: opencode or goose with a supported local provider, or llm with the appropriate Ollama, llama.cpp or MLX plugin. Model availability and tools depend on the engine and provider you configure.
do all engines show live activity status?
You can run and control all eight supported engines. Working and needs-you detection currently reads Claude Code and Codex screens; other engines can appear idle while running.
what can the relay see?
Routing identifiers, network addresses, timing and sizes. It does not have the keys to decrypt session or chat content. Browser-client code is served by the relay; native app code is bundled with the app.
does this replace my current relay?
Hosting a separate private gateway preserves the existing client connection. Setup reviews the service and route before applying changes.
what do I need to host it?
A reachable trusted HTTPS origin and an awake host. Use built-in HTTPS (Let’s Encrypt or your certificate), your own HTTPS proxy, or a private VPN. Let’s Encrypt needs public ports 80 and 443. A DNS name alone cannot bypass carrier-grade NAT; there is no automatic gateway failover.
Remote control. On your terms.
Use the mobile app over your own relay. Start with the setup guide.