ThinkWatch Lite 2026.10.28

Upgrade notes:

• The bundled core is now 0.81.0. The control-plane protocol stays at 51, so a remote server running core 0.80.0 still connects; the behavior described below needs 0.81.0 on the side that runs the gateway.
• Nothing is cleared; the request history, stored payloads and settings carry over.

Conversations with encrypted history stay on their upstream:

• OpenAI Responses upstreams, such as a ChatGPT account, hand clients encrypted history that only the same account can read. Codex sends it back every turn. Before, moving Codex's route to another upstream made a conversation under way fail on every turn.
• Such a conversation now goes back to the upstream that encrypted its history, even after its route changes. The request details show this under Conversation.
• If that upstream was removed, or another upstream is asked to read the history, the request fails with a message that explains why and suggests routing the conversation back or starting a new one.

Routing:

• In the route table's rule list, the letter tile shown for an upstream without a logo lines up with the text.

Downloads

Platform	File
macOS, Apple silicon	ThinkWatch-Lite-2026.10.28-darwin-arm64.dmg
Windows, x64, installer	ThinkWatch-Lite-2026.10.28-windows-x64-setup.exe
Windows, x64, portable	ThinkWatch-Lite-2026.10.28-windows-x64-portable.zip
Windows, ARM64, installer	ThinkWatch-Lite-2026.10.28-windows-arm64-setup.exe
Windows, ARM64, portable	ThinkWatch-Lite-2026.10.28-windows-arm64-portable.zip
Linux, x86_64	ThinkWatch-Lite-2026.10.28-linux-x86_64.AppImage
Linux, aarch64	ThinkWatch-Lite-2026.10.28-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-lite

On 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 | sh

Both 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.28-darwin-arm64.dmg.sha256

On Linux:

sha256sum -c ThinkWatch-Lite-2026.10.28-linux-x86_64.AppImage.sha256

On Windows, in PowerShell, the following prints True when the installer matches:

(Get-FileHash .\ThinkWatch-Lite-2026.10.28-windows-x64-setup.exe).Hash -eq (Get-Content .\ThinkWatch-Lite-2026.10.28-windows-x64-setup.exe.sha256).Split()[0]

The Homebrew cask and the Linux install script check the SHA-256 themselves.

What's Changed

• Routing: align the letter tile of an upstream without a logo by @fylorn in #366
• 2026.10.28: conversations with encrypted history stay on their upstream; pin core v0.81.0 by @fylorn in #367

Full Changelog: v2026.10.27...v2026.10.28