yoru-cli

The Claude Code hook installer for Yoru. One command installs a PostToolUse hook that forwards every tool call, file edit, and red-flag event to a Yoru backend. Your next session shows up in the dashboard automatically.

Install

pipx install yoru-cli                       # or: uv tool install yoru-cli
yoru init --server https://yoru.acme.com

Use pipx/uv — a bare pip install yoru-cli fails on Homebrew/Debian Python with error: externally-managed-environment (PEP 668). No pipx? A venv works too: python3 -m venv .venv && .venv/bin/pip install yoru-cli.

Yoru is self-hosted — point the CLI at your own backend with --server. yoru init opens a pairing URL in your browser, writes ~/.claude/hooks/yoru.sh, and registers the hook in ~/.claude/settings.json. Don't have a server yet? Stand one up — docker-compose up.

Requires Python 3.10+. One runtime dep: httpx.

Usage

yoru init --server https://yoru.acme.com       # pair against your server (--server required)
yoru init --server https://yoru.acme.com --token yoru_xxx --force   # non-interactive (CI / scripted rotation)

yoru tail < events.jsonl                # post a batch of events (debug)

yoru --version
yoru --help

Exit codes: 0 ok · 1 already installed (use --force) · 2 auth failed · 3 4xx · 4 5xx/network.

How the hook works

The installed script is ~20 lines of Bash that POSTs one JSON event per Claude Code tool call:

{"session_id": "…", "user": "…", "kind": "tool_use", "tool": "Bash", "content": "…"}

It uses curl --max-time 2 || true so a Yoru outage never stalls your terminal — Claude Code doesn't notice the hook is even there.

Multiple devs, multiple identities

Each paired identity (server + token) gets its own local slot under ~/.config/yoru/identities/. The shared tailer and every hook event attribute to whichever identity is active — there is no per-process attribution.

• One dev per machine (the normal case): no ambiguity — one OS user, one identity, all activity is unambiguously yours.
• Same OS login, multiple identities paired (e.g. you re-paired against a second org, or a shared machine): only one identity is active at a time. Concurrent work under that same login attributes to whichever identity is active regardless of who actually ran it — this is an explicit, documented limit, not a bug. Switch identities first with yoru use <label>.

Run yoru doctor any time to see the active identity and get warned if other paired identities exist unused on this machine.

Self-host the server

The CLI is MIT. The server (backend + dashboard) is AGPL-3.0 and lives at github.com/TsukumoHQ/yoru. docker-compose up, then yoru init --server https://your-host — done. There is no hosted Yoru; you run it.

License

MIT · Copyright (c) 2026 Yoru authors. Issues and PRs welcome at github.com/TsukumoHQ/cli-yoru.