One bar at the edge of your screen. One LED per agent. The LCD says who needs you. Press 1, 2 or 3 and the agent has its answer. Unroll it for the inbox.
cargo install adeamp # Linux, macOS, Windows · needs Herdr running
Open source. No account, no model in the loop, no screen recording. Pronounced "aid amp".
Skins in the recording: base-2.91 (Nullsoft), TopazAmp, Green Dimension, XMMS-Turquoise, by their authors.
Herdr is the open-source runtime that keeps coding agents running in real terminals and reads what each one is doing. ADEAMP is a client of its socket: every state on the bar is Herdr's verdict, and every answer you send goes through Herdr to the agent's own terminal. Nothing is wrapped or replaced.
curl -fsSL https://herdr.dev/install.sh | sh on Linux or macOS, then cargo install adeamp (prebuilt binaries are coming). ADEAMP finds Herdr's socket by itself.
Start claude, codex or any supported CLI in a Herdr pane, the way you already do. Each one shows up on the bar within a second, with its state.
When an agent asks something, its LED turns amber and the LCD shows the question. Press 1, 2 or 3. Unroll for the full inbox, with the question exactly as the agent painted it.
680 by 30 pixels, always on top, draggable anywhere. One LED per agent: amber pulsing means waiting on you, green means done, breathing green means working, dim means idle.
No unrolling needed. 123⏎ go to the agent that has waited longest. Tab moves to the next one that needs you.
A card per agent, who needs you first. Blocked agents show the last lines of their screen and the keys. Done or idle ones get a prompt line. One button opens the agent's terminal in Herdr.
Drop any classic .wsz on the bar and it wears it: the shade strip, the LCD font, the visualiser colours for the LEDs, the playlist colours for the inbox.
Scan a QR on the bar and the inbox is on your phone, on your own network. Same questions, same keys, a buzz when someone needs you.
Blocked means Herdr recognised a question on screen. Done means a finished turn and stays lit until you look. Unknown is shown as unknown. Demo data is always badged.
A classic Winamp skin is a zip of bitmaps. Its windowshade strip is literally this bar, so ADEAMP draws it as the skin's author drew it, sets the ticker in the skin's own pixel font and takes its LED and inbox colours from the skin's colour files. Browse the Winamp Skin Museum, download one, drop it on the bar.
Right-click the bar, turn on the phone, scan the QR. A phone on the same network or tailnet gets the same inbox: the question as the agent painted it, the same 1, 2, 3, a prompt line, a buzz when a new one needs you. The bar serves the page itself, token-paired; nothing in between, nothing stored anywhere.
Link is the paid part: the same inbox anywhere, with push notifications, through a relay that keeps nothing (the key never leaves your QR), and agents on your servers and other machines on one bar. Pairing is the account: scan, use it free for a week, then a key from Stripe. The desktop bar and the local phone page stay free.
No. Claude Code, Codex and the rest write the code. ADEAMP shows what each one is doing, collects their questions, and passes your answers to them.
No. It sends a key or a prompt only when you press one. It never answers a question for you, and it never types into an agent that is already waiting at a prompt: Herdr refuses that, and ADEAMP says so.
Yes. Herdr is a free, open-source runtime that keeps agents running after you close the terminal and reads their state. ADEAMP is a client of it. Agents in other terminals are invisible to it.
Classic Winamp 2 skins (.wsz). ADEAMP needs the skin's titlebar.bmp; it uses text.bmp, viscolor.txt and pledit.txt when they are there, and falls back to its own colours when they are not. Modern (.wal) skins are not supported.
Nothing leaves your machine. ADEAMP talks to Herdr over a local socket and reads a skin file you gave it. The phone page is served by the bar on your own network, paired with a token. There is no account, no analytics and no model call. Link, when it ships, will relay the inbox end to end encrypted; the bar keeps working without it.
All three. It is one native Rust binary with no webview. Windows support follows Herdr's: generally available, with their documented limits.