Skip to content

The agent that grows with you

fix(catalog): update hermes-resetwatch to 0.2.24

Adolanium53cf7bd5ed9e
diff --git a/plugin-catalog/hermes-resetwatch.yaml b/plugin-catalog/hermes-resetwatch.yaml
index bb1086674db..e86064e123c 100644
--- a/plugin-catalog/hermes-resetwatch.yaml
+++ b/plugin-catalog/hermes-resetwatch.yaml
@@ -1,8 +1,8 @@
name: hermes-resetwatch
repo: https://github.com/Adolanium/hermes-resetwatch
-sha: 002c8c378cb6fa092241cbe94dcffa29bd26184e
-version: "0.2.23"
-image: https://raw.githubusercontent.com/Adolanium/hermes-resetwatch/002c8c378cb6fa092241cbe94dcffa29bd26184e/assets/catalog-banner.png
+sha: 7bef46c90024357761fe807f7d18c4809f2d6e2f
+version: "0.2.24"
+image: https://raw.githubusercontent.com/Adolanium/hermes-resetwatch/7bef46c90024357761fe807f7d18c4809f2d6e2f/assets/catalog-banner.png
description: "Track subscription quotas and reset times in Hermes Desktop. Disclosure — probe.py re-executes itself under the Hermes Python interpreter located via HERMES_PYTHON / VIRTUAL_ENV / the parent process or the Hermes installer's managed venv (HERMES_HOME/installs); it reads provider API keys from the Hermes .env, Hermes's own saved OAuth logins (auth.json credential pool, read-only), the Vaultwarden plugin's local secret cache (cache/vaultwarden_cache.json, read-only, only when Vaultwarden is the sole enabled secret source) and Docker s6 container env files, plus other coding-assistant CLIs' local logins (including macOS keychain entries), and sends each key only to its own vendor's usage endpoint."
maintainer: Adolanium
tier: community