Who it is forA developer in a Pi session who needs a codebase question answered (for example how authentication works) without stopping their current work.
The problemReading through unfamiliar code blocks the main conversation, and a single agent session handles one thread at a time.
The outcomeA scout Agent runs asynchronously, the Lead conversation stays usable, and the developer can check the Agent status in the /agents surface.
What you need first
- Linux or macOS for the released install script
- Pi and herdr installed, or the install script to set them up
- A Git project to work in
Steps
- Run
curl -fsSL https://raw.githubusercontent.com/boadij/pi-herdsman/main/install.sh | sh - Run
herdrin your project folder - Run
piinside the herdr pane - Type: Use scout to inspect the authentication flow.
- Type
/agentsto see the running Agent and its status
Prompt for your agent
Using the pi-herdsman repo, install the stack and ask a scout Agent to inspect <feature area> in <project path>. Expected output: a written summary of the flow from the scout Agent while the Lead session accepts other prompts. Verify that /agents lists the scout Agent while it runs.
Caveat. The README gives the scout example as a natural language request, so the exact Agent names and behavior depend on the Agent definitions you have configured.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page