Remote control for the AI agent on your own computer

Three ways to reach your C5

Away from your desk, you still want to see what the agents did and answer what is waiting. Your agents, files and history stay on a local AI agent; Remote Control only gives you a way back to it. Pick the path that suits where you are and who you are happy to have in it.

The first two need nothing from Growther.si and keep working without it. If you already reach the machine over SSH, growther connect user@host opens C5 in your browser over that connection, with nothing published and no pairing needed.

Pairing a phone

1. Open Remote Control on the machineIn C5 on the computer itself, go to Settings › Remote Control. A device that reaches C5 remotely cannot change this tab.
2. Turn it on and accept the termsFlip Publish this machine's address. The first time, the Remote Control section of the Terms opens; read it, tick the box and press Agree.
3. Set the sign-in leaseChoose how long each sign-in from a paired device lasts, from one hour to seven days. It is 24 hours unless you change it.
4. Show the pairing codePress Show pairing code. The code works once and expires after three minutes.
5. Scan it with your phoneOpen the phone's camera, scan the code, open the link and follow the pairing screen. The phone creates its own key, which never leaves the device.

Pairing against the issued address lets the phone reach the machine from anywhere. You can pair over your own Wi-Fi instead; the phone then works only on that network and warns once about the machine's self-signed certificate.

Who can see what

Who sits between your phone and your machine depends on the path, and every path is encrypted on every hop. C5 also signs ordinary requests and responses, so a change made on the way is detected.

Through the address Growther.si issues, the connection runs through a Cloudflare tunnel, where it is decrypted for routing, so that path is not end to end. Your own network and growther connect keep every third party out.

• Growther.si does not see your sessions. Session content never passes through its servers, on any path.
• What it does receive, only while Remote Control is on: your machine's name and up to four addresses it can be reached at, shown only to you at rc.growther.si and deleted when you turn it off.
• Streams are not signed. Chat replies as they arrive, file downloads and live feeds are encrypted but not signed.
• Your model providers are unchanged. They receive what you send them, on your own account, with or without Remote Control.

The full trust statement is in the docs: Remote Control privacy. For running everything on hardware you control, see a self-hosted AI agent and what a private AI agent means.

Turning it off means off

• Off signs everyone out. Turning Remote Control off revokes every pairing, gives back the issued address and deletes its tunnel, and withdraws your addresses from your account.
• Revoke one device at once. Revoke closes that device's connection and signs it out on the spot, without waiting for its lease to run out.
• Disconnect everything signs out every device, deletes the address and tunnel, ends your portal sign-ins and turns Remote Control off, in one button.
• Some things never work from a phone. A paired device cannot pair another device, change leases, or change Remote Control, voice or security settings — the install refuses it.

If you want a service someone else hosts and keeps reachable for you, C5 is the wrong fit: the machine running it has to be on and awake, and Remote Control only reaches back to it.

Remote Control pairs well with a scheduled AI agent: let the morning jobs run at home, then check the results from your phone.