tThreadrun Download

Phone access

Phone access lets you follow a thread or factory run from your phone, and reply to it, while this computer sleeps. Your server serves the phone pages, so you turn phone access on for a server first.

Before you turn it on

  • A server runner. Phone access isn't available on This computer.
  • Ports 80 and 443 reachable from the internet. Threadrun opens them on the server. If your provider has a firewall, it must allow them too.
  • A name for the server's certificate. Without a domain name, Threadrun uses your server's IP address with dashes and nip.io, for example 203-0-113-10.nip.io. If you connected with a domain name, that name must already point at your server.

Turn it on

  1. Go to Settings → Runners and click Turn on phone access on your server's card. You can also click Phone on a thread while connected to that server, then Turn on phone access in the dialog.
  2. Wait while Threadrun opens ports 80 and 443, adds firewall rules if ufw is active, starts the HTTPS proxy and gets a free certificate from Let's Encrypt.
  3. When it's ready, the card shows the address under Phone access.
If the address doesn't answer, check that your provider's firewall allows ports 80 and 443. Then click Turn on phone access again.

Open a thread or run on your phone

  1. Open a thread, or a factory run, on your computer.
  2. Click Phone. The Open on your phone dialog shows a QR code and a six-digit PIN.
  3. Scan the QR code with your phone's camera.
  4. Enter the PIN on the phone, next to the code shown in the app, and tap Open.

The PIN appears in two groups of three, such as 123 456. In the dialog you can also click Copy link, Open in browser, or New link and PIN for a fresh link and PIN.

What you can do on the phone

  • Follow along. The Chat tab shows messages, tool calls and plans as they happen, formatted as on your computer: lists, tables, links, and code blocks with a Copy button. The Activity tab lists each tool call with its input and output; type in Search activity to filter it.
  • Reply in the box at the bottom, and tap Send. A long paste is attached as Pasted text, as on your computer.
  • Stop the agent while it works.
  • Answer permission requests with the buttons the agent offers. Each request names the command or file the agent wants. A request answered on your computer or by your policy shows who answered it, and requests close when the agent's turn ends.
  • Open what the agent made. The Files tab lists the files the agent created or changed, newest first. Tap one to open it in your phone's browser: web pages, PDFs, images and text. On a factory run, open a stage to see its files.
  • Change the model, effort and session mode from the bar at the top.
  • Follow a factory run's stages. A run lists its stages on the phone. Open one to follow that stage's agent, and reply or stop it there.

Approval requests are answered in the Threadrun app, not on the phone.

Security

  • The link is signed for one thread. For a factory run, it also covers that run's stages. It can't open any other thread.
  • The link alone isn't enough. The phone also needs the PIN. The PIN isn't part of the link, and only your Threadrun app shows it.
  • Links expire after 7 days. Open a new one from the app.
  • Five wrong PINs lock the link. Open a new one from the app.
  • Only the phone pages are served to the internet, over HTTPS. The rest of the runner stays reachable only through SSH.
  • Don't share the PIN or the link.

Turn it off

On the server's card, click Turn off phone access. The HTTPS proxy stops, the firewall rules that Threadrun added are removed, and the phone link stops working. Uninstalling the runner also turns phone access off.

To learn more about servers, see Runners and Your own server. For help with a phone address that doesn't answer, see Troubleshooting.