What a throwback. Back in 2015 I have started Applaudience, which at the time was the only provider of real-time cinema ticket sales data. I still remember comparing our numbers against TheNumbers.com as part of calibration. I have since moved on to other businesses, but this remains one of my favorite pieces of technology that I have developed. Would love to bring it back one day.
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).
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.
Surprised not to see more people ask about performance profile of v4.
Zod is great in terms of API, but a no-go in terms of performance.
We ended up writing babel plugins (https://github.com/gajus/babel-plugin-zod/) and using it along with zod-accelerator, which improves performance, but breaks in various edge-cases.