Skip to content

What leaves your computer

Validated against app ae3b0ef2 and Collector 0.9.0 (54621da), 11 November 2026. This page as Markdown

This page covers the Collector of the closed beta, build 0.9.0, and nothing else. It sends whole numbers, dates and fixed labels to https://app.humanload.eu, and to no other host. The service refuses any field that is not listed here.

Nothing is sent before you run humanload login.

One request carries one batch. These travel with it:

Field Example Purpose
X-Api-Key header hl_col_… the Device key: it says which Device sends. The body names neither you nor the Device
User-Agent header humanload/0.9.0 the Collector version
Content-Type header application/json the format of the body
X-Hl-Payload-Id header 64 hexadecimal characters a fingerprint of the body, so that a repeated send is recognised
X-Hl-Delivery header changes_only one of three fixed labels, explained below
X-Hl-Pending header 0 how many days still wait to be sent after this batch, 0 to 35
schema 2 the format version of the batch
collector 0.9.0 the Collector version
calc 5 the version of the counting rules, so that two rule sets are never mixed
days a list the days of the batch, 35 at most

The three labels of X-Hl-Delivery:

  • changes_only: the usual case. The batch holds the days whose Counts changed.
  • closed_days: you chose to send closed days only (see How often it sends).
  • backlog: more days wait than this batch holds; X-Hl-Pending says how many remain.

A Local day (Jour local in the French interface) runs from 5 a.m. to 5 a.m. the next day, in your computer’s time zone. Each day of a batch carries these fields:

Field Example Purpose
day 2026-11-11 the date of the Local day, without a time or a time zone
observed_at 1794391200 the hour of sending, rounded down to the full hour; never the time of something you did
complete false whether the Local day is over
method exact exact when counted live, estimated when it comes from the History review
counts an object the Counts below
interventions 41 your messages to the sessions you lead
project_switches 6 two consecutive messages in two different projects, 20 minutes apart at most
session_switches 9 the same between two sessions
waiting_peak 2 the most sessions waiting for your answer at once
asks 5 the structured questions the agent asked
asks_answered 5 those you answered
asks_decided null not measured in this build
asks_recommended null not measured in this build
permissions 7 the agent’s requests to run a command or touch a file
sessions 4 the sessions with a message from you that day
concurrent_peak 3 the most sessions you led at the same time
active_quarters 22 the quarter-hours with at least one message from you
late_quarters 0 among them, those after 11 p.m.
permission_noise an object four numbers about the requests above, listed next
repeated 0 temporary approvals that repeat earlier ones; 0 in a standard install
permanent 0 permanent approvals; 0 in a standard install
observed 0 requests with a confirmed decision; 0 in a standard install
compound 2 requests for chained shell commands
note absent the Evening note, only with its consent, see below
value 3 inside note: the note, from 1 to 5
source evening inside note: evening or next_day, when you answered

repeated, permanent and observed stay at 0 unless you run humanload import-permissions, a command that reads a file of your own past approvals. Nothing in the steps of this handbook runs it.

A Count (Compte in the French interface) is a whole number of events of one type. The Collector sends Counts per Local day; the glossary also calls the total of a week a Count. Counts payload gives the exact rule the service checks for each field, generated from its code.

The Evening note is the energy left at the end of your day, from 1 to 5, that you declare in a dialog. It stays on your computer by default.

It is sent only when both of these are true:

  1. you ran humanload note --sync on on this Mac;
  2. you agreed on the page https://app.humanload.eu/me/note.

Withdraw either one and the note stops leaving. Withdrawing the consent in the app also erases the notes the service stored.

When sending failed for a while and works again, the Collector sends one receipt for that outage:

Field Example Purpose
v 1 the format version of the receipt
id 32 hexadecimal characters a random number drawn for this outage, unrelated to you or the Device
reason dns a fixed class of cause, such as dns, tls or http_503; never an error message
started_hour 498424 the UTC hour when sending began to fail
completed_hour 498441 the UTC hour when it recovered
duration_s 61200 how long the outage lasted, in seconds
oldest_pending_s 57600 how long the oldest day waited
pending_peak 2 the most days waiting at once, 1 to 35

Only you see these receipts, on the page My Devices.

humanload login sends the fixed name humanload-cli, then a one-time pairing token that the service issued for this pairing. That token is not the connection code you type: it never shows on screen. Then it sends two fields:

Field Example Purpose
platform macos the only platform of this build
collector 0.9.0 the Collector version

The Device name is typed in the browser. Your computer’s name is never sent.

Three requests carry the Device key and the body {}, nothing else: the capability check before a send, the renewal of the Device key, and its revocation when you run humanload uninstall.

  • Claude Code events. The hook receives each event, with the text of your message, the working folder and the session identifier. It keeps one line: a time, the kind of event, a few flags and fixed labels, and keyed fingerprints of the session and of the project, made with a random key that stays in the local folder. The text is not written.
  • Claude Code transcripts, only when you accept the History review (humanload backfill). The Collector reads the last 30 days of transcripts on this Mac and keeps estimated Counts. The estimated Counts are sent only after you also agree on https://app.humanload.eu/me/history.
  • Not in any field above: text of any kind, project or repository names, paths, your computer’s name, your time zone, the time of an event.

The only hours sent are the hour of sending and the two hours of a sending outage.

Everything is in one folder, ~/Library/Application Support/Humanload/, except the Device key.

Place Content Kept
live/ one file of event lines per day 65 days
state.json daily Counts, notes, settings, what the service acknowledged until you erase the folder
salt the random key of the fingerprints until you erase the folder
Your login Keychain the Device key until you uninstall

humanload uninstall offers to erase the folder.

Once an hour at most, at a minute fixed for this Mac. A send carries only the days whose Counts changed since the last acknowledged send; the service then tells the Collector not to send again for 50 minutes.

While a Local day is open, the service therefore receives its running total each hour it changes. The service keeps only the latest total, but someone who read the database hour by hour could infer your activity hour by hour. To send closed days only, and not before 18:00 UTC the next day, run:

Terminal window
humanload config send-open-day off

You should see:

Setting saved.
To see Do this
the days counted on this Mac, without any network call humanload week
the connection, the last send and the days waiting humanload status
the exact Counts held locally open state.json in the local folder
what the service stored https://app.humanload.eu/me, then My data to download everything as JSON
what the History review would count, without writing or sending humanload backfill --dry-run

This build has no command that prints a batch before it is sent.

What Shown to Operator of the beta
Your Counts of each day you, and no one else not shown by the product; stored rows are technically readable
Your Evening notes, when synced you, and no one else same
Your Devices and their last send you, and no one else same
Your sending receipts you, and no one else same
Your profile you; the members of your Teams, through their agents, when you shared it same
Cells of your Team the Members and the Team managers of that Team published or masked, by month

The product shows your Counts to no one but you. The operator of this beta can technically read stored rows: the database is not encrypted per person. The operator’s written rule forbids that access outside an incident, and each access is entered in a register before it happens.

A Cell (Cellule in the French interface) is what a Team sees for one week: rounded medians over at least five people who each agreed to share, or nothing for that week. Your Counts enter a Cell only after you agree to Sharing.

Counts, notes and profiles are stored in the EU. The service’s code runs where its host, Cloudflare, places it.

What Kept
Counts and synced notes 180 days
Sending receipts 35 days
The read log of your profile 30 days
An agent’s connection 30 days at most
Your profile until you replace or delete it

Remove everything erases all of it.