Kaimon stopped working

General Usage
, ,
1

I cannot use Kaimon any longer. Claudes says:

The server is up, but the REPL eval bridge is not actually executing code.

ping succeeds — the MCP server is healthy and one session is connected (ea21299c, V3Kite.jl).
But every ex() call returns “completed with no output,” even q=false returning a plain string, even a deliberate error(…).
I confirmed code is genuinely not running: I had ex() write a probe file to disk, and the file was never created.
Restarting the REPL didn’t fix it.
So: kaimon is reachable but not usable for running Julia right now — evals are silently no-op’ing. Per your CLAUDE.md I’m supposed to route all Julia through these tools rather than the julia CLI, so I’m currently blocked from running/inspecting code.

A couple of things that might get it working, which are on your side to try:

Check the Julia gate/REPL process — the session shows as connected but the eval channel may have wedged (the log has one MCP handler error: SystemError: write: Broken pipe around session init).
A full shutdown + fresh start_session (rather than restart) may re-establish the eval channel cleanly.

I rebooted my computer, but it did not help:

  • :white_check_mark: Code search/intelligence works — grep_code, search_code, ping, etc. all respond correctly.
  • :cross_mark: Running Julia does not — ex() (and by extension run_tests) silently no-ops. I verified this concretely: an ex() call told to write a file to disk produced no file, on both the old and a freshly-restarted session.
2

First off, sorry you are running into an issue here, I’ll connect with you to sort it out ASAP. I’m not certain which version this is against so let’s figure that out so I can look in the right area and figure out what’s causing the problem.

3

I updated to the latest versions of Kaimon and KaimonGate, and now it is working again. Thank you so much!

4

Good to hear, there have been some changes lately to support the KaimonSlate.jl release in the near future, as well as fixing a few reported bugs. It’s possible you caught a version that had an issue somewhere in the middle of this. Hoping things will be stable for you but if not, don’t hesitate to let me know.