• jelder 2 days ago

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

    • gajus 2 days 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.

      • nurettin a day 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.

    • jmulla a day 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?

      • gajus 18 hours 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).

      • zareith 2 days ago

        Cool utility. Horrendous name.

        • gajus 2 days ago

          lowkey thought it is a genius name

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

          • cap11235 2 days 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).

            • gajus 2 days ago

              Fair point