# subaud.tools > subaud.tools is the landing page for the .tools family: local-first > developer tools that run on your machine, keep their state on your disk, > and never phone home. The suite is one purchase, $100 once: > https://subaud.tools/pricing/. This file tells an agent how to install a > tool and sign the machine in. ## When someone asks you to install a tool from subaud.tools 1. Find the tool below and run its install line. It works on macOS and Linux. On Windows, run it inside WSL2. 2. If this machine isn't signed in yet, the install prints a sign-in code in a line like: Go to https://subaud.tools/account/machine and type ABCD-EFGH Show the person that whole line in your reply, exactly as printed, and open the page for them with the code filled in, in their browser (macOS: open "https://subaud.tools/account/machine?code=ABCD-EFGH"; Linux: xdg-open with the same address), and put the code on their clipboard too (macOS: pbcopy; Linux: wl-copy or xclip) in case the page asks for it. Then stop and wait. Never press Allow yourself: the person checks the code against your reply and allows the machine on that page. 3. The code lasts 10 minutes and works once. If the person says it expired or they lost it, run the same install line again: it prints a new code. Show them that one the same way. 4. Don't wait for the person to tell you they've allowed it: run the same install line again every 10 seconds. Until they allow it, it says the machine is not allowed yet and keeps the same code; once they do, it finishes the sign-in and installs the tool, and you go on without asking. If they denied it or the code expired, the install says so. Tell the person, and run it again only if they ask. 5. If the install says the account doesn't own the tool, tell the person they can buy the suite at https://subaud.tools/pricing/ and stop. To sign a machine in again later, run ` login`. It prints the same kind of line. A person who runs the install or ` login` in their own terminal sees the code there and it waits until they allow the machine, with nothing to run again. ## After install When the installs are done, finish setting up so the person never types a tool command. In order: 1. Skills: run ` skills install` for each of diazo, galley, casebook, muda, sift, imprint and cull. Each puts the tool's skill where your agent harness reads skills. muda installs for Claude Code unless told otherwise: for a pi agent run `muda skills install --agent pi`. muster, kempt, proj, scratch and creel have no skills to install. 2. Connect the tools to you. - Claude Code: add the plugin marketplace and install the family plugins: claude plugin marketplace add subaud-tools/plugins claude plugin install diazo@subaud-tools and the same for galley, muster, casebook, muda, cull, imprint and sift. Each plugin registers its tool's `channel` server and a mod that runs ` watch`, so the tool connects to every new session by itself. There is no launch flag. - pi: run `pi install npm:channels.tools`, then name each tool under channelServers in ~/.pi/agent/channels.json, for example { "channelServers": { "diazo": { "command": "diazo", "args": ["channel"] } } }, one entry each for diazo, galley, muster, casebook, muda, cull, imprint and sift. A new pi session spawns them itself. 3. tmux: proj runs sessions in tmux. If `tmux` isn't on PATH, install it (Homebrew: brew install tmux; Debian or Ubuntu: sudo apt install tmux), or ask the person to. 4. Open a new proj session for the person's work, which loads the plugins or channels just set up. proj knows a project from ~/.config/proj/roots: a line `project: ` names one project, and a plain line names a parent folder whose subfolders are each a project. Ask the person one question: which repo they want to work in (the walk itself makes its own scratch place, so any repo will do, and if they have none, make an empty git repo at ~/subaud-start). Add `project: ` for it if it isn't covered. Name the work `start` without asking. Then run `proj new /start --agent claude --no-sidebar` (or `--agent pi`) with `--json`, so the first session is just the agent's terminal with no side panes, then open its page with `proj window --socket --pane ` from that output. On a Mac this opens the session's split page in Google Chrome; elsewhere, give the person the address it prints. 5. Tell the person, in one line, to say "Get me started with subaud." in that session. It runs three short walks on the real pages: proj, diazo, galley. https://subaud.tools/start/ says what they cover. ## The tools - hail: reach a running pi session from your phone. curl -fsSL https://hail.tools/install.sh | sh - diazo: planning and design in the browser, driven by your agent. curl -fsSL https://diazo.tools/install.sh | sh - muster: local multi-agent coordination bus. curl -fsSL https://muster.tools/install.sh | sh - galley: document review for agent-driven development. curl -fsSL https://galley.tools/install.sh | sh galley installs to /usr/local/bin, with sudo when that isn't writable. If sudo can't ask for a password in your shell, install it beside the others instead: curl -fsSL https://galley.tools/install.sh | GALLEY_INSTALL_DIR="$HOME/.local/bin" sh - kempt: declarative machine setup you can read before you run. curl -fsSL https://kempt.tools/install.sh | sh - tackle: small workshop tools for your terminal. curl -fsSL https://tackle.tools/install.sh | sh - casebook: a decision for every repo, pull request, issue, branch and worktree, kept in a private git repo you own. curl -fsSL https://casebook.tools/install.sh | sh - muda: find and fix delivery waste in GitHub Actions, with run evidence for every claim. curl -fsSL https://muda.tools/install.sh | sh Recipe packs for muda: ci and aws. They have no install line of their own: muda uses the packs the account owns. The suite is one purchase and its price is on https://subaud.tools/pricing/. After a purchase, a person sets up each machine one of two ways; either is fine. With your agent: https://subaud.tools/account/ has the block to paste to the agent on the machine, which follows this file. From the terminal: they paste two lines in a plain terminal, kempt's installer (it signs the machine in and waits there) and the subaud starter config, which installs tmux, Claude Code and the suite with each tool's skills and plugin: curl -fsSL https://kempt.tools/install.sh | sh ~/.local/bin/kempt init -profile suite https://github.com/subaud-tools/starter.git Then they run claude and say "Get me started with subaud." The whole path, from buying to the first walk, is at https://subaud.tools/start/. ## The guide https://subaud.tools/guide/ explains how we work with coding agents and the tools that make it work. Part 1, the kit, is every tool, pi extension, fork, package, skill and habit we use, each with what it is, why we have it and what to say to your agent. Part 2, Working this way, is how a project goes from a set-up machine to a release, stage by stage. - https://subaud.tools/guide/: what the guide is, and its two parts - https://subaud.tools/guide/kit/: the kit's three pages - https://subaud.tools/guide/kit/tools/: the subaud tools - https://subaud.tools/guide/kit/pi/: our pi extensions, the forks we keep and the packages we rely on - https://subaud.tools/guide/kit/agents/: the skills our agents follow, and our habits - https://subaud.tools/guide/working/: working this way, in eight stages ## Free and open source - channels.tools: connect channel servers that push events into a running pi session. No account or sign-in. pi install npm:channels.tools Source: https://github.com/subaud-tools/pi-extensions