docs(ollama): Ollama launcher + setup docs + fix README misdirection (closes #118) - #119
Open
MoonlightByte wants to merge 8 commits into
Open
MoonlightByte wants to merge 8 commits into
MoonlightByte wants to merge 8 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
README.mdlines 458-459 which misdirected users to configure a non-existent endpoint setting inconfig.py(issue [DOCUMENTATION] Ollama support #118).README.mdmirroring the existing LM Studio section.run_with_ollama_direct.batandrun_with_ollama_direct.sh— self-contained launchers that handle Ollama alias setup inline on first run. Both of the game's internal model tiers are aliased to a single user-chosen Ollama model (matches LM Studio's single-model behavior; avoids VRAM thrashing).OLLAMA_SETUP.mdandOLLAMA_QUICKSTART.txt.UX parity with LM Studio
On first run, the launcher auto-creates two aliases (`gpt-4.1-2025-04-14` and `gpt-4.1-mini-2025-04-14`) both pointing at the user's single pulled model. No separate setup script, no manual `ollama cp` calls. Setting `OLLAMA_MODEL=` before launch forces re-aliasing to a different model.
Out of scope
Test plan
End-to-end testing with a live Ollama server was not performed on the author's machine (local Ollama is 0.1.29, below the documented 0.4+ floor, and the daemon wasn't running). Static verification was done instead:
Closes #118.