DevToolsAImacOSProductivity

AgentBell Multi-Machine Agent Inbox

Bring every waiting coding agent across machines into one window

Problem
Developers run Claude Code, Codex, and other coding agents on a Mac, a build machine, and a server at the same time; each agent stops for a yes before deploy, delete, or install. The yes takes two seconds, but figuring out which machine is waiting can eat the whole evening—switching windows, scrolling back, judging if it's stuck or just quiet, then SSHing in. With more machines, you become the router.
Solution
A single-window desktop console that aggregates coding agent sessions across machines, automatically identifying who is working, who is waiting for confirmation, who finished, and who is idle—highlighting waiting sessions and letting you jump in and confirm or type with a few keys.
Users
Developers running multiple coding agents across machines, remote teams, and engineers managing build machines and server clusters.
MVP
Collect tmux/session status and output from each machine via SSH or a lightweight agent; detect and highlight confirmation prompts; single-window list with keyboard navigation; send confirmations or input directly to the session; local-first with no cloud dependency.
Revenue
One-time desktop app purchase ($14.99–$24.99); team plan per seat adds shared machine lists and alerts.
Why now
Coding agents are moving from single-machine to multi-machine, multi-session use, making wait-for-confirmation a high-frequency friction point; existing tools solve single-machine visibility or generic tmux management, lacking a focused cross-machine 'who is waiting for me' view.

Source discussions · 2

  1. Hacker NewsShow HN: TAW, herdr for tmux: see which coding agent needs you1↑ 0
  2. V2EX[分享创造] 所有 agent 收进一个窗口,在等你的那个变成琥珀色
← Back to list