Re:Show HN: Amux – A tmux-based multiplexer for running para...
by Beefin on Friday March 06, 2026 @03:48PM
(#47280872)
One thing we’ve been thinking about with Amux is that the unit of compute shouldn’t just be the terminal session—it should be the agent itself. That means each pane/session can expose things like:
* tokens in / tokens out * cumulative run cost * model + pricing tier * runtime duration * optional budget caps
So when you spin up 5–10 agents, you can immediately see which one is burning tokens or looping.
Longer term I’d love for Amux to treat agents a bit like processes in `htop` where you can see resource usage across all agents in one place and kill/restart the expensive ones quickly.
Curious how you're currently surfacing cost in your setups — logs, dashboards, or something inline with the agent runtime?
One thing I'd add: make cost-per-agent visibility mandatory from day one. When you've got 5-10 agents running, token burn compounds fast. Each agent needs its own cost dashboard.
We bake this into every agent setup now—cost awareness prevents expensive mistakes.