Yeah, I think that's about the shape of it. And I think it's something we don't currently have a good, well established pattern for. It calls for something mo

Yeah, I think that's about the shape of it. And I think it's something we don't currently have a good, well established pattern for. It calls for something more localized than a daemon, but longer lived than a utility. We see something similar with language servers. In that case (IIUC, and I may not) they're typically tied to specific places in the directory structure (eg. listening on a unix socket created in the root of the relevant source tree). For the chat client I mentioned above, I tied things together with shell and environment variables. The script to start the long-running process read its initial output and set things up so that future commands would know which process to talk to. The code is at https://github.com/dlthomas/genies https://github.com/dlthomas/genies