First run
After npm install -g harnery, run a freshness check and a tour of the daily-driver commands.
Verify the install
Section titled “Verify the install”harn doctorYou’ll see a ✓ / ⚠ / ✗ checklist of every dep Harnery touches (Node, git, bun, optional restic + rclone + playwright, plus whether .harnery/ is reachable). Warnings about missing optional deps are fine; only node and git are required for the core surface.
JSON output for scripting:
harn doctor --jsonCoord-layer essentials
Section titled “Coord-layer essentials”Inside a project that has a .harnery/ directory (the multi-agent state lives here), the daily-driver commands are:
# Heartbeat + claims for every agent active in this repo right nowharn agents list
# End-of-turn status box for yourselfharn agents status
# Declare what you're working on so peers can see itharn agents set-task "rewriting the deploy command"
# One-screen orientation snapshot (you, the repo, active peers)harn context
# Append a note to your own journal (survives in-session compaction)harn journal add note "looking at this from the email angle next"Web dashboard
Section titled “Web dashboard”The coord layer is read-only-fine but easier to consume in a browser:
harn web upVisit http://localhost:9000. Live updates via Server-Sent Events whenever the coord state changes. See concepts / web UI for the full feature tour.
Portable utilities
Section titled “Portable utilities”Cross-platform CLI bits that aren’t tied to coord state:
# Offline token counting (o200k_base, Claude proxy ~5% delta on markdown)harn tokens README.md src/**/*.ts
# Parse a Gmail .eml export → clean markdown threadharn eml saved-thread.eml -o thread.md
# Monorepo-aware grep with sensible default excludes (node_modules, dist, .next, ...)harn grep "TODO" --lang ts --limit 50
# Cookie-aware HTTP fetch + reader pipelineharn fetch https://example.com | harn read -
# Playwright-driven browser with persistent profile + visibility/overflow checksharn browse https://example.com --check-visible "header nav" --jsonBackup + sync
Section titled “Backup + sync”Insurance for the coord state across machines:
# One-time setup (creates the restic repo + password file)harn backup init
# Take a snapshot of .harnery/ (events.ndjson + .lock excluded by default)harn backup snapshot
# Cross-machine sync of identities + archived journals + councils via rcloneharn sync init # picks the rclone remote configured via `rclone config`harn sync push # local → remoteharn sync pull # remote → localWhere to next
Section titled “Where to next”- Configuration: settings file format + precedence
- CLI reference: the full command tree
- Concepts / coord layer: what the multi-agent state does
- Concepts / web UI: dashboard tour