What runs where
Herdloom has no server of its own. There is no Herdloom account, nothing to sign up for, and no telemetry. This page says exactly what that means, item by item.
The table
Section titled “The table”| Thing | Where it happens | What leaves the Mac |
|---|---|---|
| The board, its tickets, plans, reviews and run history | On your Mac, in one folder | Nothing |
| Your repositories, branches, worktrees and commits | On your Mac | Nothing, until you push |
| Knowledgebases | On your Mac, in the folder you named | Nothing, unless the base is a repository you sync |
| Agent sessions | The agent CLI runs on your Mac | The prompt and the code it reads go to that agent’s provider, on your own login and subscription |
| Tracker calls | Started by Herdloom | A read of the issues you asked for, and, with write-back on, a status change and a comment |
| Pull requests, merges, publishing | Through your own git and GitHub CLI login | The branch, the pull request and its body |
| Update checks | Started by the app | A request to the releases page |
| Logs, run output, attachments, report files | Written to disk on your Mac | Nothing, until you attach a report yourself |
The three things that reach the network
Section titled “The three things that reach the network”Your agents. When a run starts, the agent CLI talks to its provider the same way it does when you run it in a terminal: your prompt, and whatever code it decides to read. That connection is the agent’s, under your account, on the subscription you already pay for. Herdloom never falls back to a bare API key you did not configure.
Your tracker and GitHub. Import reads. Watches read, once a minute, only the issues matching the label or the query you set. Nothing is written to any issue unless write-back is on for that connection. Pull requests, merges and publishing go through your own GitHub CLI login.
The update check. The app asks its releases page whether a newer build exists.
Turn a connection off and its traffic stops. Turn an agent off and it is never started.
What there is no such thing as
Section titled “What there is no such thing as”There is no Herdloom account, no sign-in, no licence server and no sync. Two people cannot look at the same board, because there is nowhere for a shared board to live. A team uses Herdloom as individuals with a shared tracker.
There is no telemetry and no analytics. Nothing counts your tickets, times your runs or reports a crash anywhere but your own disk. When something breaks, the way it reaches anyone else is a report file you build and attach yourself.
There is no cost tracking either, in either direction: no dollars are recorded and no billing information is read. A run is bounded by turns and time, and reported that way.
Where it all sits
Section titled “Where it all sits”Everything lives in one folder in Application Support, plus the worktrees beside each repository and whatever folders your knowledgebases point at. Tokens you enter go into the macOS Keychain. Removing Herdloom takes back the parts outside that folder and shows you the folder itself.
Privacy and your data covers what is written to disk and how to delete it. What Herdloom is is the shorter version of the whole idea.