Support
Something not working?
ThreadKnot is a small project and support goes to a real person. Write to us and describe what happened, what you expected, and which platform you are on. That is usually enough to sort it.
Contact
support@smithnetworksolutions.com
We read every message and aim to reply within two business days. Requests about your data are answered within 30 days, and deletions complete within 24 hours.
Try this first
The five things that go wrong most
The mobile app cannot reach my computer
Both devices have to be on the same network or tailnet. Check that the desktop app is running, that the phone is on the same Wi-Fi rather than cellular, and that your router does not have client isolation or AP isolation enabled, which stops devices on the same Wi-Fi from seeing each other.
Notifications stopped arriving
Confirm notifications are still allowed for ThreadKnot in your phone's system settings, then unpair and re-pair the device from the desktop app's Settings. Re-pairing issues a fresh credential, which fixes most delivery problems.
An agent will not start
ThreadKnot launches the claude, codex and kimi command line tools already installed on your machine. Open a terminal and run the tool by name. If it is not installed or not signed in there, it cannot start from ThreadKnot either, and fixing it in the terminal fixes it here.
I want to rotate my access token
Delete server.json in the ThreadKnot data directory and restart the app. It mints a new token on next start and invalidates every paired client, which you then re-pair.
I want my data deleted
Notification pairing can be removed from Settings, Account and data, inside the mobile app. If you subscribe to the hosted relay, a machine and everything recorded against it can be deleted from the console; closing the account entirely is done by writing to us and we will confirm when it is done. Anything on your own machines is yours to delete directly, because we never receive it.
I subscribed to the relay and my machine is not reachable
Check the console first: a machine has to be switched on there, and the subscription has to be active for new sessions to be accepted. Then check remote access is still enabled in the desktop app's Settings. Sessions already running are never cut off by a lapsed subscription, so an installation that works for you and not for a colleague is usually a device that has not been approved yet.
Do I need the paid relay?
Only to reach a machine from outside your own network. On a LAN or a tailnet, the desktop app, the web UI, the mobile app and the machine-to-machine mesh are free, complete, and need no account at all.
Elsewhere
Bug reports move to public issue tracking when the repository opens with the first release. Until then, email is the fastest route and reaches the same people.