Contact hey@jaack.me for setup help, bug reports or privacy questions. Include your device model, operating system version, app version and the steps that produced the issue. Do not send pairing JSON, tokens, private keys or sensitive job contents.

Connect a device

1. Download the broker and follow the CLI and MCP guide. Use Python 3.10 or later and OpenSSL.
2. For mobile devices, initialize the broker with your computer’s reachable LAN address. Explicitly start its LAN listener and allow the connection through your firewall.
3. Run the broker’s pair command. Verify the address and certificate fingerprint, then paste its JSON, import a pairing JSON file or scan its QR representation in the app. Keep this credential private.
4. Tap Start sharing. Discover the device from your harness before submitting a supported job.
5. Retrieve the result with artifact or companion_artifact. The broker checks the artifact fingerprint.

If the connection fails

Check that the broker is running, the address and port are correct, and both devices can reach each other. Grant local network permission if prompted. A loopback address such as 127.0.0.1 points to the device itself, not another computer.

A changed certificate requires a new pairing. Never bypass pin verification. If a worker was revoked, create a new pairing and use Forget connection before reconnecting.

If work stops

On iPhone and iPad, keep the app visible. Backgrounding, Stop sharing, loss of connectivity or critical thermal pressure can interrupt the session. Return to the app and start sharing again. An interrupted job may be retried when its lease expires; interruption is not proof of completion.

Only text analysis, text chunking and image OCR are supported. Check input limits in the protocol. OCR can make recognition errors; review its output before relying on it.

Remove data or access

Clear Activity deletes the local activity history. Forget connection removes the local Keychain pairing credential and rotates the registration identifier. Revoke the device in the broker to invalidate its remote access. These actions do not erase the broker’s stored jobs or results.

The broker operator manages server retention. To erase a broker you operate, stop it and delete its private configuration directory. This also deletes its identity and invalidates existing pairings. Keep any records you need before deletion.

Harness Companion · Privacy policy