.nrepl-port sometimes not honored

Open Beginner friendly
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
clojure
Domain
cli

Research direction

Start with the clj-nrepl-eval --discover-ports entry point and locate where the No nREPL servers found. output is produced. Update the message to mention checking the current working directory, then run the discovery command in a case with no discovered servers to verify the wording.

Written by the indexing model from the issue text.

Description

Hi @bhauman !

I'm using a vanilla installation following the provided instructions faitfhully, over Claude Code.

I found that sometimes --discover-ports, as invoked by CC, sometimes finds nothing, despite .nrepl-port existing and referring to an active port.

Perhaps the cwd may be incorrectly set at times?

This is how it can look in CC:

⏺ Bash(clj-nrepl-eval --discover-ports)
  ⎿  No nREPL servers found.

What about this change?

-No nREPL servers found.
+No nREPL servers found. Are you running this command in the right cwd?

The extended message may nudge the models into doing the right thing - else, they can skip instructions in Skills/etc.

Thanks - V

Dominant language
Clojure
Stars
188
Forks
25
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bhauman/clojure-mcp-light

All issues in bhauman/clojure-mcp-light

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.