Repository navigation
ThinkWatch v3.1.0
Images
ghcr.io/thinkwatchproject/think-watch-server:3.1.0ghcr.io/thinkwatchproject/think-watch-web:3.1.0
Helm
helm install think-watch ./think-watch-3.1.0.tgz \
--namespace thinkwatch --create-namespaceThe thinkwatch-core crates move from v0.59.0 to v0.62.0. Two changes reach
the gateway: tool-call inspection gains a built-in rule for ThinkWatch's own
data directory, and an upstream whose base URL already ends in an API
version is no longer sent a second one.
Read before upgrading
- The new tool-call rule
thinkwatch-datais on and set to cut off, like
the other high-risk built-in rules. A deployment whose tool-call
inspection is in enforce mode starts cutting off answers whose tool call
reads or changes one of the paths below; one in observe mode only records
them. Set the rule to record, or switch it off, on the security page to
keep the previous behaviour.
Added
- Tool-call inspection:
thinkwatch-data(Read or change ThinkWatch's own
data). A tool call whose path or command points into ThinkWatch's data
directory (~/.thinkwatch,%APPDATA%\ThinkWatch,/var/lib/thinkwatch,
/etc/thinkwatch) — where the desktop gateway keeps every upstream key and
its own protection settings. Text that only mentions the directory, such as
a document being edited, does not count. The security page lists it with
the other built-in rules.
Fixed
- Upstream base URLs that end in their own API version (
…/api/paas/v4,
…/api/v3) now receive requests under that version instead of a second
/v1appended to it, which returned 404. Requests and connection tests
both use it.
Changed
- thinkwatch-core crates (tw-bedrock, tw-breaker, tw-dialect, tw-guard)
v0.59.0 → v0.62.0.