Repository navigation
Release 2.6.2
Date: 2026-11-01
This release improves Windows startup diagnostics and live configuration handling.
Changes
- Accept a successful OpenRouter startup response when its one output token is used for reasoning and visible content is empty. API and choice errors still fail startup.
- Log structured request and response details when file logging is enabled, including provider order, HTTP status, elapsed time, finish reason, and token counts. API keys, images, and extracted text are excluded.
- Reload valid changes to the selected config and API key file while the resident runs. On Windows, directory notifications use
ReadDirectoryChangesW; the config file is not held open. A 30-second check and a check before each capture back up notifications. - Keep the last valid settings if a reload fails. Changes to the hotkey or resident TCP port still require a restart.
- Show startup and fatal errors in a Windows dialog and remove per-key keyboard event logs.
Configuration
Set RELOAD_CONFIG_ON_GRAB=false to disable resident reload until the next restart. An executable-local .env takes precedence over SCREEN_OCR_LLM.
MODEL accepts an OpenRouter model variant such as :nitro. PROVIDERS accepts a comma-separated ordered list. With no provider list, OpenRouter chooses routing. With a list, fallback outside the list is disabled.
Verification
The Windows GUI executable was built with -ldflags "-H=windowsgui". Startup was verified with :nitro and no provider override, one provider, and four comma-separated providers. Each returned HTTP 200 and kept the resident running. A live Windows file edit triggered a config reload.
The full Go suite passed with live API credentials unavailable; go vet ./... and LSP checks passed. The live CLI image integration test did not extract text with the locally selected :nitro model; OCR output for that model remains unverified.