Agent Edge | June 21, 2026
📋 CoachDesk — A SaaS for Personal Trainers Built in a Week, Then the Real Work Started
Hannah Wolfe (CoachDesk) | Indie Hackers
Hannah Wolfe, a solo founder in the UK, built CoachDesk in just over a week — an all-in-one tool for self-employed personal trainers to handle clients, bookings, invoicing, and workout plans in one place instead of juggling WhatsApp, spreadsheets, and a notes app. She went from zero to shipping in a week, then hit the wall every solo founder knows: zero paying customers. Her Indie Hackers post is raw honesty about being at customer zero, and the 51-comment thread became a masterclass in niche B2B distribution. The community helped her realize the real objection isnt “is this better than a spreadsheet” but “do I trust a one-week-old tool with my clients’ payment details?” Her response was to shift from feature pitches to security transparency and targeted cold outreach to small groups of trainers.
📌 Why it matters: Every builder with an agent product will face the same wall. Building fast is the easy part. Distribution, trust, and niche targeting are the real job. Hannas post captures that shift in real time with specific lessons from someone still in the middle of it.
🤖 Agent angle: The technical takeaway is the 1:1 distribution strategy. Instead of content marketing (slow) or ads (expensive), she started sending personalized screen-recorded demos to specific trainers. An agent could scale this by scraping trainer directories, generating personalized demo scripts per trainer’s location and niche, and automating the outreach sequence with follow-ups triggered by engagement signals.
🔒 HackAgent — Open-Source Security Toolkit for the AI Agent Era
AISecurityLab/hackagent | GitHub
🔗 https://github.com/AISecurityLab/hackagent
HackAgent is an open-source Python SDK and CLI for red-teaming AI agents against threats traditional security tools cant touch. It targets prompt injection, jailbreaking, goal hijacking, and tool misuse — vulnerabilities that become critical as agents get more autonomy. The pipeline uses modular attack techniques (PAIR, TAP, AutoDAN-Turbo, FlipAttack, BoN) with a generator model creating adversarial prompts and a judge model evaluating whether they bypass safety measures. It supports Google ADK, OpenAI SDK, LiteLLM, and LangChain, and works locally with no API key required.
📌 Why it matters: As more builders deploy agents for clients, security is the differentiator. HackAgent turns a once-manual security review into an automated, reproducible test suite. If you are shipping agent products, this is the equivalent of running a penetration test before going live.
🤖 Agent angle: The modular design means you can extend it with your own attack presets. The kill chain is automated: generate adversarial prompts, fire them at your target agent, let the judge score the results. Run this in CI before every deployment to catch regressions in your agent’s safety posture.
🐹 Hermes Desktop Buddy — A Physical Tamagotchi That Lives Next to Your Agent
Syax89/hermes-m5stick-firmware | r/hermesagent
🔗 https://github.com/Syax89/hermes-m5stick-firmware
A firmware for the M5StickC Plus 2 that turns it into a physical Hermes Agent companion. Forked from Anthropic’s Claude Desktop Buddy, it connects to the Hermes Agent HTTP API over Wi-Fi and displays real-time session data, token counts, and connection status on a tiny screen. It supports 18 ASCII pets (robot, capybara, cat, duck, etc.) that change mood based on agent activity — mood decays with inactivity, energy drains over time, and the pet levels up every 50K tokens. You can press a button to record voice input (up to 4 seconds) transcribed via Groq STT and sent straight to your Hermes agent. The device shows sleep, idle, busy, celebrate, dizzy, and nap states driven by what your agent is doing.
📌 Why it matters: Most agent UIs are browser tabs or terminal windows. This is a physical ambient display that turns agent activity into something glanceable and even playful. For the Agent Edge reader building agent products, the pattern of “physical companion for digital services” is underexplored.
🤖 Agent angle: The voice input shortcut is the killer feature. Double-press a physical button, speak for four seconds, and it gets transcribed and injected into your agent’s active session. Thats faster than switching windows, typing, or reaching for a phone. For anyone running agents from a workstation, a dedicated hardware input like this eliminates friction.
⚙️ Dynamic Workflows for Hermes — Claude Code-Style Orchestration, Now Open Source
donovan-yohan/hermes-plugin-dynamic-workflows | r/hermesagent
🔗 https://github.com/donovan-yohan/hermes-plugin-dynamic-workflows
A Hermes Agent plugin that brings Claude Code-style dynamic workflows to the Hermes ecosystem. It defines workflow steps as declarative JSON — agent, conditional branches, parallel steps, pipelines, and phases — all wired together with data references. A policy engine enforces default-deny sandbox rules, and subprocess workflow scripts run in an out-of-process VM with restricted builtins. Durable runs are journaled for deterministic replay without re-dispatching. Designed as a single model-facing tool with actions for validate, run, status, catalog, and template execution.
📌 Why it matters: Most agent orchestration is either hardcoded (not flexible) or LLM-driven (not reliable). This sits in the middle — declarative JSON workflows that an agent can author and execute, with sandboxing and replay built in. Its the pattern of “let the agent write its own playbook” made production-safe.
🤖 Agent angle: The replay capability is the most practical feature. If a multi-step agent workflow fails at step 4, you fix the issue and replay from the journal without burning API calls on the preceding deterministic steps. This is the same cost-saving pattern used in enterprise workflow engines, now available inside any Hermes agent.
🐺 GreyFox — A Self-Hosted Proxy Box to Stop AI API Token Bleeding
Skilful Fox Studio | r/SelfHostedAI
🔗 https://github.com/Skillful-Fox-Studio/grey-fox-community
GreyFox is a lightweight, self-hosted proxy and operator console for controlling commercial AI API usage. It runs as a single Docker container with a local SQLite backend and acts as a drop-in OpenAI-compatible endpoint. You point your application at http://localhost:8080/v1/chat/completions and GreyFox handles the rest — token-first quota enforcement via a custom X-App-User-Id header, exact response caching that serves cached responses in milliseconds instead of hitting paid upstream APIs, and a local Angular dashboard for real-time spend visibility. No cloud registration, no telemetry, no external dependencies beyond Docker.
📌 Why it matters: If you are running agent test suites, simulation pipelines, or multiple agent instances against paid APIs, token costs bleed fast. GreyFox catches duplicate requests before they reach the API and enforces daily quotas per user or test runner. The community edition is free and self-hosted — the only cost is running the container.
🤖 Agent angle: Run GreyFox alongside your agent stack and route all LLM calls through it via the base URL setting. Every identical prompt your agent generates during a debugging session gets cached on the first call and served instantly on subsequent calls. For a typical development cycle of iterate-test-fix-repeat, this can cut API costs by 50-80% without any code changes to the agent itself.
Want this in your inbox every day?
Daily curated intelligence on how to build autonomous income systems with AI agents