Show HN: Teemux – Zero-config log multiplexer with built-in MCP server(teemux.com)
teemux.com
Show HN: Teemux – Zero-config log multiplexer with built-in MCP server
https://teemux.com/
10 comments
Couldn't coding agents just run `tail -f *`?
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.
With teemux, a persistent MCP server gives multiple AI agents access to logs as needed—without interrupting your development flow.
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.
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?
Can I aggregate logs from processes running on different machines?
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).
Cool utility. Horrendous name.
[deleted]
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