👋:skin-tone-2: New to looking at the internals of nREPL, and I'm trying to understand what's going on here. We launch a REPL within our application using the standard CIDER set of middleware. This works fine for my colleagues who use CIDER, they connect to it on a host and port and get all the output back that they expect. However it doesn't seem to work for those of us using Cursive. stderr messages are printed to the tty the REPL server is running in (a docker container, remote process on a K8s node, etc), but don't appear on my Cursive REPL session. Likewise, stdout from external applications that have been triggered from within our app (e.g. by using conch to shell out to something) appear in the remote tty but not my session. If I launch the REPL directly from Cursive using it's lein integration, I get the expected output, but of course that only works for a local REPL. Everything contained within Clojure/Java seems OK, but not anything going directly to the default *out*. The nREPL docs says that ls-middleware is a core operation (https://nrepl.org/nrepl/ops.html#ls-middleware), but I'm failing to find it in the API docs to know what namespace to load to run it from, to at least verify that the expected middleware (`cider.nrepl/wrap-out` in this case, I believe) is even loaded. Can anyone point me in a good starting direction?

Is it possible to dynamically load middleware from the client these days? Thinking about this issue: https://clojurians.slack.com/archives/C17JYSA3H/p1659976888613829, it would be nice to be able to load the middleware from the client.