Adaptive from the first phase
Machine specs are detected before setup so the model recommendation is based on RAM, disk, CPU, and GPU signals.
Windows 11 + WSL2 Ubuntu
TerminalSick OpenClaw makes local OpenClaw and Ollama on Windows and WSL2 feel like a real project, not a fragile script pile.
This project gives you a guided installer, hardware-aware model recommendation, resumable phases, gated security checks, release packaging, and GitHub automation in one supportable repo.
Default posture
Localhost-first
Recommendation flow
Detect hardware before onboarding
Release state
Pages + release workflows included
Why this repo exists
One clear path for beginners, enough control for maintainers.
Security stays ahead of convenience
Hardening and a gateway security gate must pass before the UI is exposed, and localhost-only remains the default.
Publishable as a real project
Release packaging, checksum output, GitHub Actions validation, and Pages deployment are already wired in.
Run paths
Choose the entry point that matches how you work.
Windows-first launcher
Best for people starting in PowerShell and wanting one command that handles WSL handoff cleanly.
./scripts/00_windows_launcher.ps1 -Yes- Runs hardware detection first
- Checks Windows-to-WSL bridge behavior
- Keeps strict bridge mode optional
Remote-WSL direct
Best for developers already living inside the Linux side and wanting the shortest path to completion.
bash scripts/00_run_full_setup.sh --yes- Supports guided and non-interactive modes
- Resumes from saved state automatically
- Includes dry-run prompt testing modes
Security model
The gateway is not allowed to outrun the hardening work.
01
Preflight
Validate WSL, systemd, sudo readiness, and environment assumptions.
02
Harden
Repair OpenClaw state, generate tokens, and run audit plus fix commands.
03
Gate
Explicit security gate checks run before startup and block the gateway if they fail.
04
Expose locally
Only after the gate passes does the setup allow localhost access to the UI.
Release track
Already wired for GitHub Releases and Pages.
Validate
PR and push workflows run syntax checks plus dry-run model-picker guards.
Package
scripts/97_package_release.sh emits tar.gz, zip when available, and checksum manifests.
Publish
Tag pushes like v0.2.1 build release artifacts and publish them through GitHub Actions.
Support path
Questions, bugs, and ideas each have their own lane.
Q&A
Use Discussions > Q&A for setup help, troubleshooting, and validation questions.
Ideas
Use Discussions > Ideas for early concepts that are not ready to become a scoped issue yet.
Issue forms
Use the new issue forms for reproducible bugs and concrete feature requests with enough detail to act on.
Next step