Connect to your PC from a phone

Take your PC conversations with you#

The Android PWA connects directly over HTTPS to Kyalulu on your own PC or server. That server owns the characters, history, and memories and runs model inference; the phone provides the interface. One person manages one Runtime and accesses the same data from their own devices. Pairing does not isolate multiple users.

This does not provide managed Cloud, phone-only LLM execution, automatic synchronization between servers, or Google Play distribution. Even with an external cloud model, the PC holding your conversations must remain awake and online. For relay access without inbound port forwarding, see the Remote guide.

Pair over HTTPS#

1. Build the Web app on the PC and prepare a certificate Android trusts and the exact HTTPS Origin. Keep the private key outside the served Web directory.
2. Start the home server. To continue existing conversations, select the Desktop data directory and avoid running another Runtime against it concurrently. Use one worker without auto-reload.
3. Issue an eight-digit code on the PC with home_server.py code.
4. Open the HTTPS address in Android Chrome and enter a device name and the code.
5. Open a conversation and add the app to the home screen through app information or Chrome's menu.

pnpm --filter web build
# Replace certificate paths and hostname with your own values
.venv/Scripts/python.exe scripts/home_server.py serve --origin https://home.example:8000 --cert C:/certs/home.pem --key C:/certs/home-key.pem
.venv/Scripts/python.exe scripts/home_server.py code --tls-name home.example --ca C:/certs/ca.pem

The code lasts 120 seconds, permits one use, and locks after five failed attempts. Issuing a new code invalidates the previous one. Do not routinely use LAN HTTP or bypass certificate warnings. TLS, network, and firewall setup are not automatic.

Servers, disconnections, and updates#

Save servers under the conversation portability settings. Switching opens that server's interface without forwarding credentials. Switching servers does not migrate data, and card import/export alone does not move a whole conversation with its memories.

After a disconnect, generation IDs are checked against durable history. Disconnection does not trigger automatic resubmission; do not manually send the same message again before checking its result. The Service Worker caches only public build assets such as the interface, never APIs, conversation history, or user images. Offline history reading and reply generation are unavailable. Apply an update after generation or editing has finished and the result is confirmed; updates wait while another Kyalulu tab is open.

Device management and limits#

Paired devices can edit characters, import files/text, and correct memories. LE management, model deletion/download, comparison experiments, and external Hub search/URL retrieval remain PC operations. For a lost device, find its ID with devices and revoke it on the PC. A server restart also invalidates all registrations, although work accepted before revocation may finish.

Drafts use device-local storage, not an encrypted vault, and remain after revocation. Use OS locking and delete site data on shared devices. Public documentation describes implementation and browser checks; physical Android installation, Gboard input, network switching, and real-model quality and latency remain formal release checks. Preparation is not formal acceptance. Continue to the import guide to migrate cards.