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.

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

lowkey thought it is a genius name

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