How it works
Validated against app ae3b0ef2 and Collector 0.9.0 (54621da), 11 November 2026. This page as Markdown
Humanload has three parts: you and your agent, your Device with the Collector, and the service with the Team MCP. The first two are yours. The third is the only place where anything is stored outside your computer.
You declare a profile
Section titled “You declare a profile”You say how you want to be asked, in the app or through your own agent. The result is one HUMANS.md profile, made of closed values, stored on the service. You choose whether your Teams read it. How to ask me gives the steps.
Agents read profiles through the Team MCP
Section titled “Agents read profiles through the Team MCP”The Team MCP is the server an agent connects to, at https://app.humanload.eu/api/humans/mcp. Each person connects
their own agent and approves it in a browser; the server knows who asks from that approval, never from what the agent
says. Before an agent asks a colleague for something, it is told to read that colleague’s profile and to shape the
request as the profile says. Each read is logged, and the owner of the profile sees the log.
The Collector counts on your Device
Section titled “The Collector counts on your Device”The Collector is optional. On a Mac, a Claude Code hook hands it each event of your sessions. It keeps a line without text in a local folder, and reduces those lines to Counts: one whole number per type of event and per Local day, such as your messages, your project switches and the sessions waiting for you.
The Collector sends Counts to the service
Section titled “The Collector sends Counts to the service”The Collector of the closed beta sends the days whose Counts changed once an hour at most, under a Device key that only your Keychain holds. The service checks every field it sends against a closed contract and refuses anything else. What leaves your computer lists every field.
Each reader sees one thing
Section titled “Each reader sees one thing”You see your own Counts. Your teammates’ agents see your profile, when you shared it. A Team sees a Cell: one weekly summary over at least five people who agreed to share, never a person. No AI model runs on the service: Counts follow fixed rules, and the sentences of a profile are fixed text.