Skip to content
Discussion options

You must be logged in to vote

Hi @imavroukakis — you're not doing anything wrong; it's how the detection probe works that's biting you.

On macOS, llmfit marks MLX as available if either of these is true (llmfit-core/src/providers.rs):

  1. A running MLX server responds — it probes MLX_LM_HOST if set, then http://localhost:8080 (the mlx_lm.server default), then http://127.0.0.1:8000 for oMLX identity.
  2. python3 -c "import mlx_lm" succeeds — i.e. the mlx_lm package is importable by whatever python3 is first on your PATH.

Both of your install routes fail check 2 by design:

  • pipx installs mlx-lm into its own isolated venv — that's the whole point of pipx — so the system python3 can't import mlx_lm, even though the mlx_lm.server

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@imavroukakis
Comment options

Answer selected by imavroukakis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants