What can the Handover CLI do?
The dependency-free CLI authenticates an identity, searches context, creates and continues handovers, pulls nested artifacts, manages access and lifecycle, and runs imports or exports.
handover login
handover whoami
handover create --title "Research handover" --file ./context.md
handover list
handover pull <handover-id> --out ./continued-workHow do I install the CLI?
The direct installer works with Node.js 22.13 or newer. It downloads the same dependency-free command published by Handover.
mkdir -p ~/.local/bin
curl -fsSL https://handover.sh/handover.mjs -o ~/.local/bin/handover
chmod +x ~/.local/bin/handoverWhere is the HTTP API documented?
The machine-readable OpenAPI 3.1 contract is published at https://handover.sh/openapi.json. Browser requests use the signed-in session and automated clients use scoped bearer credentials.
How does Handover prevent conflicting writes?
Continuation requests include expectedRevisionId. If another collaborator has already created a newer revision, the API returns a revision conflict instead of overwriting their work.
FAQ
Frequently asked questions
Does the CLI read Cloudflare or GitHub storage directly?
No. The CLI uses Handover's public HTTP contract and treats external providers as connectors.
Can automation preserve nested folders and binary files?
Yes. Pull and publish workflows preserve nested paths, binary bytes, and a hash-checked local manifest.