alt.hn

1/23/2026 at 3:49:35 PM

Show HN: Teemux – Zero-config log multiplexer with built-in MCP server

by gajus

1/23/2026 at 7:57:11 PM

Couldn't coding agents just run `tail -f *`?

by jelder

1/23/2026 at 8:01:11 PM

That would require restarting your services to redirect their output. Fine for one-off scripts, but impractical when you have long-running processes and don't want to restart them every time an agent needs to read logs.

With teemux, a persistent MCP server gives multiple AI agents access to logs as needed—without interrupting your development flow.

by gajus

1/24/2026 at 8:22:03 AM

OK, but it isn't like agents react to flowing logs, they just connect to whatever server and query the past 5 minutes or 2 hours on demand depending on the debugging task at hand without mixing contexts together.

by nurettin

1/24/2026 at 1:45:11 PM

love the utility. I've used hacky stuff in the past to combine logs from different processes.

Can I aggregate logs from processes running on different machines?

by jmulla

1/24/2026 at 5:46:31 PM

Funny you ask. This project started as a very different project almost five years ago. It was called roarr.io, and the primary purpose was exactly that: adhoc collecting logs from remote machines. However, I've not ported this functionality (yet).

by gajus

1/23/2026 at 7:28:33 PM

Cool utility. Horrendous name.

by zareith

1/23/2026 at 7:36:19 PM

lowkey thought it is a genius name

tee (Unix command that splits output) + mux (multiplexer) = teemux

by gajus

1/23/2026 at 7:43:33 PM

Pronounced tmux. That's a thing. A very related thing. A very well-known thing. It's a bad name. I do like the concept though (haven't tried using it yet).

by cap11235

1/23/2026 at 7:44:01 PM

Fair point

by gajus