You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for testing this @sathiraumesh! You're right — the DOCKER_MODEL_RUNNER_HOST env var was only being honored by llmfit's TUI mode; the CLI recommend subcommand wasn't probing any local provider at all.
Just cut a release that fixes this: v0.9.1. The recommend command now queries Ollama, MLX, llama.cpp, Docker Model Runner, and LM Studio — same as the TUI — so DMR will receive a request (and the installed status shows up in both text and JSON output).
Try the same command again with the new image and you should see the request land in Docker model logs.
@AlexsJones i will try to test. I think we probably need to change the existing implementation a bit to run interactively from DMR side. But I will test and see if there are any other changes that we might need
hi @AlexsJones i created a issue request here for the llmfit project to finalize the implementation here based on my findings and comments for this feature here. Can you have a look on this when you have time
Activity
ericcurtin commentedon Mar 14, 2026
Tagging @AlexsJones and @three-foxes-in-a-trenchcoat for awareness. Probably want to point at Docker Model Runner rather than Ollama also.
[-]docker model fit[/-][+]docker model launch llmfit[/+]sathiraumesh commentedon Apr 5, 2026
hi @ericcurtin can I look into this? I saw that
llmfithas already included dmr as a provider. Maybe I can try to integrate itsathiraumesh commentedon Apr 5, 2026
Hi @ericcurtin @AlexsJones i was testing this localy. When
I set DOCKER_MODEL_RUNNER_HOST=http://model-runner.docker.internal and watched Docker model logs for incoming requests which means it uses the DMR backend.
In the default cli mode, it doesn't call the dmr backend, probably pointing to Ollama
Should we wait for this to be available in default CLI mode in llmfit?
fix: query local providers in `recommend` CLI command
AlexsJones commentedon Apr 5, 2026
Thanks for testing this @sathiraumesh! You're right — the
DOCKER_MODEL_RUNNER_HOSTenv var was only being honored by llmfit's TUI mode; the CLIrecommendsubcommand wasn't probing any local provider at all.Just cut a release that fixes this: v0.9.1. The
recommendcommand now queries Ollama, MLX, llama.cpp, Docker Model Runner, and LM Studio — same as the TUI — so DMR will receive a request (and theinstalledstatus shows up in both text and JSON output).Try the same command again with the new image and you should see the request land in Docker model logs.
sathiraumesh commentedon Apr 5, 2026
Thanks @AlexsJones Ill test it
sathiraumesh commentedon Apr 6, 2026
#837 @AlexsJones @ericcurtin you can review. I was thinking, should we allow interactive, maybe as another pr refrencing another issue
AlexsJones commentedon Apr 6, 2026
Would
docker run --rm -it ghcr.io/alexsjones/llmfit ""work to get the TUI going for now?I am reluctant to create another image just for a custom
CMDsathiraumesh commentedon Apr 7, 2026
@AlexsJones i will try to test. I think we probably need to change the existing implementation a bit to run interactively from DMR side. But I will test and see if there are any other changes that we might need
sathiraumesh commentedon May 20, 2026
hi @AlexsJones i created a issue request here for the llmfit project to finalize the implementation here based on my findings and comments for this feature here. Can you have a look on this when you have time