Best current path for Windows users
Automatic setup
install.batChecks Python, prepares the runtime prerequisites, and keeps the first-run experience more guided than raw manual setup.
Installation
A polished setup path for serious local development.
LordCoder already ships with multiple installation paths. The native core is cross-platform in direction, while the current smoothest onboarding path is still tuned for Windows developers who want a cleaner on-ramp into private local AI coding.
For developers who want explicit control
Manual uv flow
pip install uv
python -m uv tool install --force --python python3.12 aider-chat
ollama pull qwen2.5-coder:14bMatches the repo's preferred compatibility path for developers who want a cleaner manual setup on Windows.
Conservative Python setup
Virtual environment fallback
python -m venv .venv
.venv\Scripts\activate
pip install aider-chat==0.13.0 psutil pytest pytest-covA useful fallback when you prefer a traditional environment or need to step around toolchain friction.
Recommended sequence
Install the runtime, pull the model, launch with configuration.
The docs now position setup as a guided workflow: prepare the toolchain, choose a realistic model, and launch with the generated effective config instead of manually stitching every step together.
1. Python ready
Use Python 3.8+ with the documented preference for Python 3.12 in the `uv` installation path.
2. Ollama installed
Install Ollama locally and keep it available before pulling the coding model you want to run.
3. Model selected
Start with `qwen2.5-coder:14b` for the balanced path described in the project docs.
4. Launch LordCoder
Run the generated workflow config to start LordCoder with the project's current local defaults and saved model choice.
Need the source docs?