references

Documentation

Each command ships its own reference, and each installed binary prints it:

Every page of every reference is generated from the same command tree the binary parses, so a reference that disagrees with the tool fails that tool's build.

for coding agents

Point an agent at a machine that already has the tools and it can read the whole surface without scraping --help level by level:

clawee docs                  # the terminal client's whole command surface, as markdown
claweed docs                 # the PTY daemon's
clawee-release-manage docs   # this service's, if you run one

Installing from scratch is two lines, and neither needs a login:

curl -fsSL --proto '=https' --tlsv1.2 https://release.clawee.org/clawee/install.sh | sh
curl -fsSL --proto '=https' --tlsv1.2 https://release.clawee.org/claweed/install.sh | sh   # run as your user, not sudo

Both bootstraps verify a minisign signature and a SHA-256 before they unzip anything, against a public key baked into the script — see verify by hand. An agent that needs a specific build can read the channel manifest directly: https://downloads.clawee.org/<component>/latest.json, or https://downloads.clawee.org/<component>/beta/latest.json for the beta twin.