Show HN: Teemux – Zero-config log multiplexer with built-in MCP server (opens in new tab)

(teemux.com)

11 pointsgajus2mo ago9 comments

I started to use AI agents for coding and quickly ran into a frustrating limitation – there is no easy way to share my development environment logs with AI agents. So that's what is Teemux. A simple CLI program that aggregates logs, makes them available to you as a developer (in a pretty UI), and makes them available to your AI coding agents using MCP.

There is one implementation detail that I geek out about:

It is zero config and has built-in leader nomination for running the web server and MCP server. When you start one `teemux` instance, it starts web server, .. when you start second and third instances, they join the first server and start merging logs. If you were to kill the first instance, a new leader is nominated. This design allows to seamless add/remove nodes that share logs (a process that historically would have taken a central log aggregator).

A super quick demo:

npx teemux -- curl -N https://teemux.com/random-logs

9 comments

jelder2mo ago

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

gajusOP2mo ago

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.

nurettin2mo ago

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.

jmulla2mo ago

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?

gajusOP2mo ago

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).

zareith2mo ago

Cool utility. Horrendous name.

gajusOP2mo ago

lowkey thought it is a genius name

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

cap112352mo ago

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).

1 more reply

j / k navigate · click thread line to collapse

Show HN: Teemux – Zero-config log multiplexer with built-in MCP server (opens in new tab)

(teemux.com)

11 pointsgajus2mo ago9 comments

There is one implementation detail that I geek out about:

A super quick demo:

npx teemux -- curl -N https://teemux.com/random-logs

9 comments

jelder2mo ago

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

gajusOP2mo ago

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

nurettin2mo ago

jmulla2mo ago

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?

gajusOP2mo ago

zareith2mo ago

Cool utility. Horrendous name.

gajusOP2mo ago

lowkey thought it is a genius name

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

cap112352mo ago

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).

1 more reply

j / k navigate · click thread line to collapse