Argus: the intel agent sheds its cron plumbing

Thu, 27 Aug 2026 00:00:00 +0000

When I built personal-intel-agent, it did one thing: watch a topic, fold duplicate coverage into a single sourced card, and ping only when something materially moved. I later added a second engine for typed metric and price monitoring.

It now has a better name—Argus—and a cleaner boundary with Hermes Agent 0.21.

The original version had to carry some of its own scheduler plumbing because cron jobs were effectively stateless. Hermes 0.21 changed that. Cron jobs can now use persistent agent memory, carry the previous run’s output forward, skip the LLM when a deterministic source has not changed, keep a bounded per-job notepad, select reasoning effort per job, and deliver directly into a bot’s canonical chat.

npu-monitor: a system tray that knows what hardware each box actually has

Fri, 21 Aug 2026 00:00:00 +0000

Every multi-host monitoring tool I tried assumed homogeneous hardware: one GPU, maybe two, same on every machine. My LAN doesn’t work like that — one box has an AMD APU iGPU plus a Ryzen AI NPU, another has an AMD R9700 and an NVIDIA RTX 5060 Ti. So npu-monitor treats the device list as dynamic: each host reports its own real silicon and the tray renders whatever arrives.

The numbers come from the actual kernel interfaces, not screen-scraping: ROCm sysfs (gpu_busy_percent) for AMD cards, nvidia-smi for CUDA, /proc/stat deltas for CPU, and a raw DRM_IOCTL_AMDXDNA_GET_INFO ioctl against /dev/accel/accel0 — using the real 168-byte sensor struct from the kernel UAPI — for the NPU’s utilization columns.

Monitoring on AiSlackin

Argus: the intel agent sheds its cron plumbing

npu-monitor: a system tray that knows what hardware each box actually has