Skip to content

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.

The three parts of HumanloadYou and your agent: you use a browser; your agent runs in an MCP client such as Claude Code. Your Device, a Mac: the Claude Code hook feeds the Collector, which keeps event lines and daily Counts in a local folder. The service, at app.humanload.eu: the app pages, the Team MCP, and storage in the EU. Arrow 1, from you to the app pages: you sign in and declare your profile. Arrow 2, from your agent to the Team MCP: your agent reads profiles, with your consent. Arrow 3, from the Collector to the service: Counts, once an hour at most.You and your agentYou, in a browsersign in, say how to ask youYour agentin Claude Code, for exampleYour Device, a MacHook, then Collectorlocal folder: lines without textand daily CountsThe serviceapp.humanload.euApp pagesyour profile, your CountsTeam MCPshared profiles, for agentsStorage, in the EUprofiles; Counts, 180 days1 · declare your profile2 · read profiles3 · Counts, hourly at mostThe three parts of HumanloadYou and your agent: you use a browser; your agent runs in an MCP client such as Claude Code. Your Device, a Mac: the Claude Code hook feeds the Collector, which keeps event lines and daily Counts in a local folder. The service, at app.humanload.eu: the app pages, the Team MCP, and storage in the EU. Arrow 1, from you to the app pages: you sign in and declare your profile. Arrow 2, from your agent to the Team MCP: your agent reads profiles, with your consent. Arrow 3, from the Collector to the service: Counts, once an hour at most.You and your agentYou, in a browserYour agent, in an MCP clientClaude Code, for example1 · declare your profile2 · read profilesThe serviceapp.humanload.euApp pagesyour profile, your CountsTeam MCPserves shared profiles to agentsStorage, in the EUprofiles, Counts for 180 days3 · Counts, hourly at mostYour Device, a MacClaude Code hook, then CollectorLocal folderevent lines without text, daily Counts
The three parts, and the three flows between them.

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.

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 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 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.

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.