ThinkWatch Lite 2026.10.14

Upgrade notes:

• The bundled core is now 0.70.0, with control-plane protocol 46. A remote server must be upgraded to core 0.70.0 together with the app: this version does not connect to a server on 0.69.0, and 2026.10.13 and earlier do not connect to 0.70.0.
• Nothing is cleared; the request history, stored payloads and settings carry over.

New upstream:

• The first step lists services in three groups: model providers (Anthropic, OpenAI, Google Gemini, DeepSeek, Z.ai / BigModel), platforms and relays (Amazon Bedrock, OpenRouter, ThinkWatch, Sub2API, New API / One API), and local and custom (Ollama, Custom), each with its logo and a one-line description, and a search box. OpenRouter, ThinkWatch, Sub2API and New API are new.
• The second step asks only for what the chosen service needs. The authentication methods are those the service has: OpenAI offers an API key or a ChatGPT account, Z.ai / BigModel an API key or an account sign-in, Bedrock its three methods, custom and relay services an API key or OAuth; services with a single method show no choice. Fields the service already decides — its address, its protocol, a key for Ollama — are filled in or left out.
• Signing in with a ChatGPT or Z.ai / BigModel account happens inside the dialog, with the same notices as before. The sign-in link can be copied, to open it in a browser other than the default one; ChatGPT can also sign in with a device code. When the app is connected to a remote core, ChatGPT signs in with a device code only, with the verification address and the code each ready to copy. After signing in, the next steps set the models and billing of the upstream just created.

Editing an upstream:

• The dialog recognizes the service from the upstream's address, or for Sub2API, New API and ThinkWatch from where its balance is read, shows its logo and name, and applies the same rules as creating it. A value already set is always shown, even where the service would not normally ask for it.
• A Z.ai or BigModel upstream written by signing in shows Account sign-in as its method, with Sign in again; one with a typed key can switch to signing in.

Balances:

• The Quota / billing column shows each upstream's balance where its service reports one: the key's quota as a bar with what is left, the tightest of its time windows, money left in the account, or what has been spent. Hovering lists every window and the exact amounts. Sources are OpenRouter, DeepSeek, Moonshot, Sub2API, New API / One API and ThinkWatch Enterprise; the source is recognized from the address or set by the service picked when the upstream was created.
• On a ThinkWatch Enterprise gateway, a key with limits of its own shows its own limits and use; a key without shows the account's limits and its total over all of its keys, marked as the account's.
• Check connection shows the balance under its result, and an upstream's menu has Refresh balance. A balance that cannot be read shows why on hover; reading it never affects requests.

Downloads

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

On Linux:

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

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

(Get-FileHash .\ThinkWatch-Lite-2026.10.14-windows-x64-setup.exe).Hash -eq (Get-Content .\ThinkWatch-Lite-2026.10.14-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.14: new upstream wizard, upstream balances; pin core v0.70.0 by @fylorn in #318

Full Changelog: v2026.10.13...v2026.10.14