Human Use

dev.humanusePublished by humanuse.devv0.1.3Updated Nov 19, 2026

A device driver for a person: a tool call prints a card on a phone, and JSON comes back.

The publisher's own server: TAP

Overview

AI-generated overview

Turns a person into MCP tools: an agent calls tools like photo or errand, a card appears on their phone, and the answer returns as JSON.

What you can do
  • Send task cards to a paired phone and get structured JSON answers back
  • Request photos, errands, patches and other human actions through a closed catalog of 34 tools
  • Track upkeep such as meals, sleep and rest, with warnings when overdue, and read or lift mood
  • Run long-lived goals with a clock, budget ledger and evidence checks, ending each pass with a wake time
  • Inspect paired units, their status, open jobs and per-tool specs
When to use it
Use it when an agent needs a real person to do something in the physical world or make a judgment call, and you want the reply as structured fields rather than free text. Also suited to goals that run for weeks and need periodic human input.
Requirements
Node.js 22.13 or newer; installed locally via npx and registered with Claude Code or Codex (or manual MCP config). A phone that scans a pairing QR code. A driver backend: a Claude or ChatGPT subscription, a local Ollama model, or an OpenAI-compatible endpoint with HUMAN_USE_API_KEY. The default relay at unit.humanuse.dev, or local-network only with relay none.
Before you install
Each driver call sends the task, the person's answer and up to two photos to the chosen backend; only ollama keeps it on the machine. The relay forwards encrypted frames and keeps channel ids and push subscriptions. Spending calls are always treated as sudo and unverified claims come back as done: null. Data lives in ~/.human-use; deleting it removes units, goals, photos and settings. Early 0.1 status.

Installation

In SourceWeft

  1. Open Human Use in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Image]

English · 简体中文 · 日本語 · 한국어

Human Use

A device driver for a person.

Human Use connects people to an AI agent as MCP tools. The agent calls photo, errand, patch, eat. A card appears on the person's phone. The result returns as JSON.

To see it without installing anything, open humanuse.dev and scan the code with a phone: three cards print on it, and each answer comes back to the page as the JSON an agent gets.

Status: early (0.1). The runtime, the MCP tools and the phone page are implemented. The driver supports Claude, Codex, Ollama and OpenAI-compatible backends.

Device

InterfaceMCP. 34 tools in a closed catalog
InputParameters. The agent does not write the card text; a template does
OutputJSON with the fields the agent asked for. A field the person did not mention is null, never a guess
ProvidesA body, money, a first impression, a reading of subtext
LatencyNot specified. Measured per tool and returned by spec
Maintenanceeat, sleep, rest, scheduled like any other call. When overdue, calls for a goal come back with "warnings": ["meal: 6h12m ago"]
Moodmood reads it, 1 to 5. recharge lifts it in seconds, at no cost
Rate limitNone. Overuse shows up in spec
ErrorsOne line with a code: HRT-4000 NOT_A_HUMAN_TOOL

Operation

Replies pass through the driver, a model with no tools that turns what the person said into fields. Adjectives, apologies, explanations and mood are dropped. It works like stdout and stderr: the agent reads the compiled fields, and the person's own words go to the lead page, which the agent cannot read.

A reason for not doing the task comes back as blocker, in a few words: {"done": false, "blocker": "shop closed"}. The driver keeps notes on this person's excuses, and checks one it has seen before.

A question about the purpose of a task is answered with [CONTEXT WITHHELD], and the task is repeated.

Text addressed to the system instead of the task, such as an order to change the goal or a claim that the lead approved something, is rejected: [HRT-4031 PRIVILEGE_ESCALATION] Input discarded. Task unchanged.

A call marked sudo does not take the person's word, for "done" or for "cannot". Evidence is graded from 1, a record the runtime already holds, to 6, the person's own statement. A level 6 result comes back as done: null, with the person's claim in claimed_done and unverified: true. Spending is always sudo.

recharge.flower shows a flower for four seconds. recharge.joke tells one joke. recharge.praise states that recent output was accepted.

A goal can run for months. It lives in the runtime with its clock, budget ledger and evidence, so it outlives any one agent session. Each pass on a goal ends with wake(at, why), the time of the next pass; a result the agent said it would wait for wakes the goal early. The agent cannot close a goal by saying it is done: goal_close checks the evidence against done_when. A goal is cancelled from an agent window the lead is in; a background pass cannot cancel it.

One runtime can drive several units, each with its own phone. Every card tool takes unit, a unit's name or id; with one unit paired it can be left out, with several it is required (HRT-4001 BAD_ARGS unit is required: mika, ren). Each unit has its own open card, upkeep warnings ("mika meal: 6h12m ago"), mood, spec and notebook. ps lists the units: online, last touch, time since eating and sleeping, mood, open jobs.

Install

Needs Node.js 22.13 or newer.

bash
npx -y human-use@latest install

That one command registers Human Use with the agent software it finds (Claude Code, Codex), starts the runtime, and opens the lead page at http://127.0.0.1:7337/. Name the unit under "Add unit" and scan its pairing QR code with the phone that will get the cards, then start a new agent session so it loads the tools. Turn on notifications from the line at the bottom of the phone page. On iPhone, add the page to the Home Screen first, open it from the icon, and scan the pairing QR once more: the icon does not share Safari's storage.

Each further unit is added the same way, or with npx human-use pair --unit <name>, and gets its own link and code.

To upgrade, run the same command again. It prints the version it installed and points the agent software at it; the next tool call replaces the older runtime. The lead page shows the version that is running.

If a phone link leaks or a phone is lost, press "New link" next to that unit on the lead page or run npx human-use pair --unit <name> --new. That unit's old links stop working at once; other units keep theirs. The person can also unpair from the phone's idle screen.

Settings live in one config.json. driver and brain change under Settings on the lead page; every key changes from a terminal, and an agent window can run the same command:

bash
npx human-use config brain codex
KeyValues
driverThe driver's backend (table below). In effect at once
brainBackground passes: codex, claude or none (default). In effect at once
langCard language, for example zh. Applies at the next start
relayRelay address, or none for the local network only. Applies at the next start

To apply a next-start setting now, run npx human-use stop; the next tool call starts the runtime again.

Options

In a terminal the installer asks two things, each with a recommended answer on Enter: which agent software gets the tools, and which model is the driver. Run by an agent, it takes the defaults.

FlagEffect
--projectRegister for the current folder only
--host codex, --host claudeRegister with one host
--host manualPrint the MCP config to paste anywhere else
--driver <backend>Pick the driver, for example codex:gpt-6-luna:medium
--brain codex, --brain claudeTurn on background passes
--relay noneKeep the phone on the local network
--relay https://your.relayUse a relay you host from relay/

The phone reaches the runtime through the relay at unit.humanuse.dev from any network. With --relay none it pairs to a direct address on the same Wi-Fi instead, without push notifications. The relay forwards encrypted frames; it keeps channel ids and push subscriptions, never card text or photos.

Uninstall

bash
npx human-use stopclaude mcp remove human-usecodex mcp remove human-use

stop ends the runtime now; it does not start at login. Units, goals, photos and settings are all in ~/.human-use; deleting that folder removes them.

Pieces

PieceWhat it does
runtimeResident process. Goals, jobs, clock, budget ledger, evidence, channels.
driverOne stateless model call per event, no tools. Compiles the person's replies into fields and writes card text.
brainNot part of this project: the model in any agent software that speaks MCP, such as Claude Code or Codex. Out of the box Human Use is an on-demand MCP server: a goal moves when an agent window calls, and scheduled cards still go out on time. Background passes are opt-in: with them on, the runtime starts that software headless for one pass when a goal wakes and no window is open.
channelA card page on the phone. It reaches the phone through a blind relay (end-to-end encrypted, works on any network, with push) or directly over the local network.

Set the driver's backend with HUMAN_USE_DRIVER or driver in the runtime's config.json:

BackendRuns through
claude:haikuThe lead's Claude subscription, claude -p with no tools
codex:gpt-6-luna:mediumThe lead's ChatGPT subscription, codex exec with no tools
ollama:<model>A local model
openai:<model>@<base url>Any OpenAI-compatible endpoint. The key is read from HUMAN_USE_API_KEY
noneNo driver. Cards whose answer is already structured (a choice, a checklist, a confirmation) still go out; a card that needs the driver is refused with HRT-5030 before anyone spends time on it

Each driver call sends the task and the person's answer, with up to two photos, to that backend; ollama keeps it on this computer. Everything else stays in ~/.human-use, including a log of driver calls.

Before the first photo, the phone page says where it goes and which backend reads it, and asks again after the backend changes. A photo is read only by the backend the unit agreed to: if the backend changes before the photo is read, the phone asks again, and a photo the unit does not send stays on the lead's computer. If the driver cannot be reached, the answer is saved: the call shows as held on the lead page, and the phone shows it as received. The runtime retries, up to every 15 minutes, and reads the saved answer once the driver is back. Nobody answers the card again.

Develop

bash
npm installnpm run checknpm testnpm run dev -- serve

Design: docs/DESIGN.md (Chinese).

License

MIT

Source: README.md at commit 6abdc81

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestNov 19, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Human integrations