DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to watch agents and CPU load across several SSH hosts with Herdr Gpui

See each remote machine's agents, status dots, and CPU and memory in one client.

Who it is forA developer or small team running Herdr and coding agents on several machines, including remote ones over SSH.

The problemChecking which agent needs input and whether a remote machine is overloaded means logging into each host separately.

The outcomeOne window shows each host's agents with status dots and each host's CPU and memory, and it alerts you when an agent needs you.

What you need first

  • A Herdr daemon installed on your machine first, since this app is only its client
  • macOS 14.2 Sonoma or newer with Homebrew, or a supported Linux distribution with glibc 2.39 or newer, or Windows with PowerShell
  • For building from source: Rust via rustup, plus the Xcode command-line tools on macOS or the Visual Studio C++ build tools and Windows SDK on Windows

Steps

  1. Save each remote machine as an SSH host in the app.
  2. Check that each sidebar host row shows its own CPU and memory.
  3. Watch the status dots for idle, working, or waiting on you.
  4. Turn on system notifications so the Dock badge or taskbar badge alerts you when an agent needs you.

Prompt for your agent

Using the penso/herdr-gpui README, configure saved SSH hosts for <host-1> and <host-2> in the app and list the CPU, memory, and agent status shown for each host row. Verify that the status bar follows the host you selected.

Caveat. Remote CPU and memory are read over SSH, so the remote machines must be reachable that way and the README does not specify other requirements.

Share: 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