From af9dcf4976bf4e721e77bb3f3e4a8df0dc83c361 Mon Sep 17 00:00:00 2001 From: hugocasa Date: Tue, 18 Aug 2026 16:09:32 +0200 Subject: [PATCH] docs: point at the herdr plugin setup Naming the repo left the reader to work out what to do with it. The plugins do nothing until they are installed and their actions are bound, and Herdr has no action palette to discover them through. Co-Authored-By: Claude Opus 5 (1M context) --- AGENTS.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 36bb240eea..550c934bce 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -64,8 +64,9 @@ they set disjoint environment variables, so check which one you are in: See `backend/AGENTS.md` to restart the backend with different cargo features. Under herdr, `herdr --skill` prints a full reference for inspecting and driving panes and agents, and the plugins that -provision worktrees live in `windmill-labs/windmill-herdr`. The commands below are for a plain -checkout with nothing running. +provision worktrees live in `windmill-labs/windmill-herdr` — clone it and run `./setup.sh` to +install them and the keybindings they need. The commands below are for a plain checkout with +nothing running. - **Backend**: `cargo run` from `backend/` (API at http://localhost:8000) - **Frontend**: `REMOTE=http://localhost:8000 npm run dev` from `frontend/` (port 3000+)