Clojurians Log v2

im also wondering this, since the "Remote" Clojure REPL run config allows specifying a "custom port file"

really the best way to do this is not hook up the repl when you start clojure-mcp

the llm can find the repl and use different repls depending on the context

I'll check, but I think the name of the port file comes from nREPL itself, I'm not sure it allows customising it.

it has just occurred to me to use UNIX socket files instead of TCP ports, because files would be scoped to work trees naturally, making discovery more trivial. AI agents could even use their built-in file-finding tools to look for nREPL UNIX socket files. it's a simpler choice IF we don't need more than one REPL server per clojure project directory. BUT Cursive doesn't support socket REPLs atm 😞 and nREPL doesn't support sockets and ports at the same time 😞 ( https://github.com/nrepl/nrepl/blob/cc6b88f39e6e81333f5a87767e36885bb2937fe3/src/clojure/nrepl/server.clj#L213 )

Cursive does support socket REPLs. It creates a structured protocol over the socket so it's not a pure streaming REPL, but I can't see why it wouldn't work for that use case.

At least, it does for remote REPLs, but not for starting one up. So you'd have to start the REPL and then connect to it.

Hmm

i meant nREPL via UNIX socket file

$ mkdir -m go-rwx nrepl-test
$ clj -M:nREPL -m nrepl.cmdline --socket nrepl-test/socket

the regular socket REPL we do use as a health check mechanism, because if something goes wrong during nrepl initialization, we can still can peek into the process simply with echo ... | ssh datomic-cloud-ion nc ...

Oh I see. That seems like a nice feature actually, could you file an issue and I'll add that?

https://github.com/cursive-ide/cursive/issues/3090