i typically run many coding agents side by side and i noticed i never read the wall of tool calls and text and tasks they do, i just want to know if 1) it’s still going 2) what is it currently doing and 3) what was its last message if it stopped. i built a lightweight cli tool for that.
while the agent works, you get a row of ‘instruments’ (model, mode, nb of messages …) and one that shows the current action. you can always prompt your agent directly from HUD, no need to open it in full. its also possible to jump back and forth between HUD and the main coding agent with /hud
on how it works: it uses the official CLIs headless through JSON event streams and the /hud handback for claude code consumes 0 tokens (UserPromptSubmit hook, ~150ms), 0 runtime dependencies.
Comments
i typically run many coding agents side by side and i noticed i never read the wall of tool calls and text and tasks they do, i just want to know if 1) it’s still going 2) what is it currently doing and 3) what was its last message if it stopped. i built a lightweight cli tool for that.
while the agent works, you get a row of ‘instruments’ (model, mode, nb of messages …) and one that shows the current action. you can always prompt your agent directly from HUD, no need to open it in full. its also possible to jump back and forth between HUD and the main coding agent with /hud
on how it works: it uses the official CLIs headless through JSON event streams and the /hud handback for claude code consumes 0 tokens (UserPromptSubmit hook, ~150ms), 0 runtime dependencies.