Repository navigation
ThinkWatch Lite 2026.10.7
Upgrade notes:
- The bundled core is now 0.64.0, which speaks control-plane protocol 40. A remote server has to run core 0.64.0 too: this version does not connect to 0.63.0, and 2026.10.6 and earlier do not connect to 0.64.0.
- Request history is kept.
- Clients that list the gateway's models in their own configuration (opencode, Pi, oh-my-pi, Qwen Code, Grok Build) are flagged on the Clients page for an update once, because the configuration now also carries each model's specs.
Clients:
- Taking over opencode, Pi, oh-my-pi, Qwen Code or Grok Build now writes each model's specs next to its name, from the price table or the specs set on the Upstreams page: the context window, and where the client uses them, the output limit, whether the model reasons, and whether it takes images. Before, only names were written and the clients used their own defaults, for example 128K context and no reasoning levels for every model in Pi, and no automatic compaction in opencode.
- Only what is known is written; a client uses its own default for the rest. Qwen Code and Grok Build get no output limit, because both send it with every request. Qwen Code gets no reasoning setting, because its reasoning settings change what every request sends.
- When a model's specs change, for example after setting them by hand, the Clients page asks to update the client's configuration, as it already did when the model list changed.
Upstreams:
- Under "Specs…" in an upstream's model list, a model can also be marked as reasoning or not, and as taking images or not, or left to the price table.
Downloads
| Platform | File |
|---|---|
| macOS, Apple silicon | ThinkWatch-Lite-2026.10.7-darwin-arm64.dmg |
| Windows, x64, installer | ThinkWatch-Lite-2026.10.7-windows-x64-setup.exe |
| Windows, x64, portable | ThinkWatch-Lite-2026.10.7-windows-x64-portable.zip |
| Windows, ARM64, installer | ThinkWatch-Lite-2026.10.7-windows-arm64-setup.exe |
| Windows, ARM64, portable | ThinkWatch-Lite-2026.10.7-windows-arm64-portable.zip |
| Linux, x86_64 | ThinkWatch-Lite-2026.10.7-linux-x86_64.AppImage |
| Linux, aarch64 | ThinkWatch-Lite-2026.10.7-linux-aarch64.AppImage |
Each file is published with a .sha256 file beside it. latest.json is the manifest for in-app updates, and install.sh is the Linux install script.
On Windows, the portable ZIP runs without installation or administrator rights: extract it to any writable folder and start ThinkWatch Lite.exe. Its settings stay in the data folder beside it, separate from an installed copy, and it updates itself in place.
On macOS, Homebrew installs the same disk image:
brew install --cask thinkwatchproject/tap/thinkwatch-liteOn Linux, the install script downloads the AppImage for the machine's architecture, checks its SHA-256 and installs it as ~/Applications/ThinkWatch-Lite.AppImage:
curl -fsSL https://github.com/ThinkWatchProject/ThinkWatch-Lite/releases/latest/download/install.sh | shBoth commands install the latest release. First-launch steps for each platform, such as removing the quarantine attribute from a copy downloaded on macOS, are described in the README.
The ThinkWatch Lite page describes each feature, and the documentation covers installing, connecting clients and routing.
Verifying a download
A .sha256 file holds the SHA-256 of the file followed by its name. With both files in the current directory, on macOS:
shasum -a 256 -c ThinkWatch-Lite-2026.10.7-darwin-arm64.dmg.sha256On Linux:
sha256sum -c ThinkWatch-Lite-2026.10.7-linux-x86_64.AppImage.sha256On Windows, in PowerShell, the following prints True when the installer matches:
(Get-FileHash .\ThinkWatch-Lite-2026.10.7-windows-x64-setup.exe).Hash -eq (Get-Content .\ThinkWatch-Lite-2026.10.7-windows-x64-setup.exe.sha256).Split()[0]The Homebrew cask and the Linux install script check the SHA-256 themselves.
What's Changed
- 2026.10.7: write each model's specs into the clients that list models, core v0.64.0 by @fylorn in #289
Full Changelog: v2026.10.6...v2026.10.7