What kelpie sends

One request, when a board starts and every six hours after: https://update.kelpie.sh/v1/check. It answers with the newest version, which is what puts “kelpie X is out” on the board, and it counts the asker while it answers - which is the only way anyone knows kelpie is being run at all.

What goes with it is the version, the platform (darwin-arm64), whether this copy is the app or a checkout, and a random id written once to ~/.cache/kelpie/update.json. No paths, no repo names, no branches, nothing about a session, and nothing that identifies the machine or you. A check that fails leaves the board exactly as it was, so this is never something the board waits on.

Turn it off with "updateCheck": false in the config, or KELPIE_NO_UPDATE_CHECK=1 in the environment.

It is the only request kelpie makes to anything of ours. The rest of what reaches the network is gh asking GitHub about your own pull requests, and, only when you turn them on, Tailscale and the ssh connections to your machines. Kelpie makes no model calls of its own.