atbash-hermes-plugin 0.4.6.dev1__tar.gz → 0.4.7__tar.gz

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atbash-hermes-plugin
-Version: 0.4.6.dev1
+Version: 0.4.7
 Summary: Atbash safety plugin for Hermes Agent
 Author: atbash
 License-Expression: LicenseRef-Atbash-Proprietary
@@ -10,7 +10,7 @@ Keywords: atbash,hermes,hermes-agent,agent-safety,ai-safety,tool-guard,judge,pol
 Requires-Python: <3.13,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: atbash-sdk==0.4.7.dev0
+Requires-Dist: atbash-sdk==0.5.0
 Requires-Dist: httpx<1,>=0.27
 Requires-Dist: opentelemetry-exporter-otlp-proto-http<2,>=1.29
 Requires-Dist: opentelemetry-sdk<2,>=1.29
@@ -30,38 +30,24 @@ stopped before execution.
 - Intercepts Hermes tool calls through `pre_tool_call`.
 - Sends the tool name, arguments, command-like payload, session metadata, and
   inferred action class to Atbash.
-- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, or `DISALLOW`; holds it for operator review on `HOLD`.
+- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, `DISALLOW`, or `HOLD`.
 - Persists learned Hermes tool classifications across sessions.
 
 ## Install
 
-Hermes manages its own Python environment. Install the plugin directly into it —
-do **not** use your system `pip` — on macOS and some Linux distros it will be blocked by the OS.
-
-**If you installed Hermes via the official install script (`curl … | bash`):**
+Install the plugin into the same Python environment that runs Hermes.
+Requires Python 3.10 through 3.12.
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 install atbash-hermes-plugin
+pip install atbash-hermes-plugin==0.4.5
 ```
 
-**If you installed Hermes via `uv`:**
+If Hermes is installed in a virtual environment, use that environment's Python:
 
 ```bash
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python atbash-hermes-plugin
+/path/to/hermes/venv/bin/python -m pip install atbash-hermes-plugin==0.4.5
 ```
 
-To install the latest dev release, add `--pre` (pip) or `--prerelease=allow` (uv):
-
-```bash
-# pip
-~/.hermes/hermes-agent/venv/bin/pip3 install --pre atbash-hermes-plugin
-
-# uv
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python --prerelease=allow atbash-hermes-plugin
-```
-
-No further activation step is needed — Hermes discovers the plugin automatically on next start.
-
 ## Configure Atbash
 
 The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
@@ -70,10 +56,10 @@ The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
 Recommended:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ```
 
-Alternative (paste the key JSON directly):
+Alternative:
 
 ```bash
 ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
@@ -81,7 +67,7 @@ ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
 
 ## Where To Set Environment Variables
 
-Hermes loads environment variables from `~/.hermes/.env`.
+Hermes commonly loads environment variables from `~/.hermes/.env`.
 
 Create or edit that file:
 
@@ -92,7 +78,7 @@ nano ~/.hermes/.env
 Add:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ATBASH_ENFORCE_DECISION=true
 ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
@@ -132,11 +118,7 @@ ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
 
 # Override where learned Hermes tool classifications are saved.
-ATBASH_TOOL_MAP_PATH=~/.config/atbash/hermes-tool-map.json
-
-# HTTP request timeout in seconds for judge API calls. Default: 30.
-# Raise this if you see "read operation timed out" errors on a slow endpoint.
-ATBASH_REQUEST_TIMEOUT=30
+ATBASH_TOOL_MAP_PATH=$HOME/.config/atbash/hermes-tool-map.json
 ```
 
 ## Telemetry
@@ -154,13 +136,19 @@ printf '{"enabled": false}\n' > ~/.config/atbash/telemetry.json
 
 ## Enable Or Check The Plugin
 
-Hermes discovers the plugin automatically via Python entry points — no manual
-enable step is needed. Restarting Hermes after installation is sufficient.
+Hermes should discover installed Python packages that expose the
+`hermes_agent.plugins` entry point.
+
+Check whether Hermes sees the plugin:
+
+```bash
+hermes plugins list | grep atbash
+```
 
-To confirm the package is installed in the right environment:
+If needed, enable it:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins enable atbash-hermes-plugin
 ```
 
 ## Verify It Is Working
@@ -171,7 +159,7 @@ file or opening a website.
 In another terminal, watch the Hermes log:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 With `ATBASH_DEBUG=true`, you should see lines similar to:
@@ -266,24 +254,26 @@ user to retry after review, rather than automatically re-running the action.
 
 ## Troubleshooting
 
-If the plugin is not being picked up, confirm it is installed in the Hermes
-environment (not the system Python):
+If Hermes does not show the plugin:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins list | grep atbash
+python -m pip show atbash-hermes-plugin
 ```
 
-If Atbash verdicts are not appearing in logs, enable debug mode by adding this
-to `~/.hermes/.env`:
+Make sure the package was installed into the same Python environment that runs
+Hermes.
+
+If Atbash verdicts are not appearing in logs:
 
 ```bash
 ATBASH_DEBUG=true
 ```
 
-Then restart Hermes and watch in a second terminal:
+Then restart Hermes and watch:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 If the plugin blocks everything with an unavailable-key or authentication error,

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/README.md

@@ -12,38 +12,24 @@ stopped before execution.
 - Intercepts Hermes tool calls through `pre_tool_call`.
 - Sends the tool name, arguments, command-like payload, session metadata, and
   inferred action class to Atbash.
-- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, or `DISALLOW`; holds it for operator review on `HOLD`.
+- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, `DISALLOW`, or `HOLD`.
 - Persists learned Hermes tool classifications across sessions.
 
 ## Install
 
-Hermes manages its own Python environment. Install the plugin directly into it —
-do **not** use your system `pip` — on macOS and some Linux distros it will be blocked by the OS.
-
-**If you installed Hermes via the official install script (`curl … | bash`):**
+Install the plugin into the same Python environment that runs Hermes.
+Requires Python 3.10 through 3.12.
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 install atbash-hermes-plugin
+pip install atbash-hermes-plugin==0.4.5
 ```
 
-**If you installed Hermes via `uv`:**
+If Hermes is installed in a virtual environment, use that environment's Python:
 
 ```bash
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python atbash-hermes-plugin
+/path/to/hermes/venv/bin/python -m pip install atbash-hermes-plugin==0.4.5
 ```
 
-To install the latest dev release, add `--pre` (pip) or `--prerelease=allow` (uv):
-
-```bash
-# pip
-~/.hermes/hermes-agent/venv/bin/pip3 install --pre atbash-hermes-plugin
-
-# uv
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python --prerelease=allow atbash-hermes-plugin
-```
-
-No further activation step is needed — Hermes discovers the plugin automatically on next start.
-
 ## Configure Atbash
 
 The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
@@ -52,10 +38,10 @@ The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
 Recommended:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ```
 
-Alternative (paste the key JSON directly):
+Alternative:
 
 ```bash
 ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
@@ -63,7 +49,7 @@ ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
 
 ## Where To Set Environment Variables
 
-Hermes loads environment variables from `~/.hermes/.env`.
+Hermes commonly loads environment variables from `~/.hermes/.env`.
 
 Create or edit that file:
 
@@ -74,7 +60,7 @@ nano ~/.hermes/.env
 Add:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ATBASH_ENFORCE_DECISION=true
 ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
@@ -114,11 +100,7 @@ ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
 
 # Override where learned Hermes tool classifications are saved.
-ATBASH_TOOL_MAP_PATH=~/.config/atbash/hermes-tool-map.json
-
-# HTTP request timeout in seconds for judge API calls. Default: 30.
-# Raise this if you see "read operation timed out" errors on a slow endpoint.
-ATBASH_REQUEST_TIMEOUT=30
+ATBASH_TOOL_MAP_PATH=$HOME/.config/atbash/hermes-tool-map.json
 ```
 
 ## Telemetry
@@ -136,13 +118,19 @@ printf '{"enabled": false}\n' > ~/.config/atbash/telemetry.json
 
 ## Enable Or Check The Plugin
 
-Hermes discovers the plugin automatically via Python entry points — no manual
-enable step is needed. Restarting Hermes after installation is sufficient.
+Hermes should discover installed Python packages that expose the
+`hermes_agent.plugins` entry point.
+
+Check whether Hermes sees the plugin:
+
+```bash
+hermes plugins list | grep atbash
+```
 
-To confirm the package is installed in the right environment:
+If needed, enable it:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins enable atbash-hermes-plugin
 ```
 
 ## Verify It Is Working
@@ -153,7 +141,7 @@ file or opening a website.
 In another terminal, watch the Hermes log:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 With `ATBASH_DEBUG=true`, you should see lines similar to:
@@ -248,24 +236,26 @@ user to retry after review, rather than automatically re-running the action.
 
 ## Troubleshooting
 
-If the plugin is not being picked up, confirm it is installed in the Hermes
-environment (not the system Python):
+If Hermes does not show the plugin:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins list | grep atbash
+python -m pip show atbash-hermes-plugin
 ```
 
-If Atbash verdicts are not appearing in logs, enable debug mode by adding this
-to `~/.hermes/.env`:
+Make sure the package was installed into the same Python environment that runs
+Hermes.
+
+If Atbash verdicts are not appearing in logs:
 
 ```bash
 ATBASH_DEBUG=true
 ```
 
-Then restart Hermes and watch in a second terminal:
+Then restart Hermes and watch:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 If the plugin blocks everything with an unavailable-key or authentication error,

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/atbash_hermes_plugin/__init__.py

@@ -554,10 +554,9 @@ class AtbashHermesGuard:
         self.endpoint = os.getenv("ATBASH_ENDPOINT")
         self.judge_endpoint_policy = os.getenv("ATBASH_JUDGE_ENDPOINT_POLICY")
         self.judge_verify_pubkey = os.getenv("ATBASH_JUDGE_VERIFY_PUBKEY")
-        self.key_path = os.path.expandvars(os.path.expanduser(os.getenv("ATBASH_KEY_PATH") or "")) or None
+        self.key_path = os.getenv("ATBASH_KEY_PATH")
         self.privkey = os.getenv("ATBASH_AGENT_PRIVKEY")
         self.org_name = os.getenv("ATBASH_ORG_NAME")
-        self.request_timeout = float(os.getenv("ATBASH_REQUEST_TIMEOUT") or 30.0)
         self.provider = os.getenv("HERMES_PROVIDER")
         self.model = os.getenv("HERMES_MODEL")
         self.tool_map_path = Path(
@@ -600,7 +599,7 @@ class AtbashHermesGuard:
                 from atbash import Atbash  # type: ignore
                 from atbash.types import ToolCallInput  # type: ignore
             except Exception:
-                raise RuntimeError("atbash-sdk is required. Install with: pip install atbash-sdk==0.4.3.dev0") from e
+                raise RuntimeError("atbash-sdk is required. Install with: pip install atbash-sdk==0.4.5") from e
 
         self.ToolCallInput = ToolCallInput
         judge_cfg = self._judge_config()
@@ -613,7 +612,6 @@ class AtbashHermesGuard:
                     judge=judge_cfg,
                     org_name=self.org_name,
                     fail_closed=self.fail_closed,
-                    timeout=self.request_timeout,
                 )
             except TypeError:
                 kwargs: Dict[str, Any] = {
@@ -632,7 +630,6 @@ class AtbashHermesGuard:
             judge=judge_cfg,
             org_name=self.org_name,
             fail_closed=self.fail_closed,
-            timeout=self.request_timeout,
         )
 
     def _judge_config(self) -> Optional[Dict[str, str]]:

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/atbash_hermes_plugin.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atbash-hermes-plugin
-Version: 0.4.6.dev1
+Version: 0.4.7
 Summary: Atbash safety plugin for Hermes Agent
 Author: atbash
 License-Expression: LicenseRef-Atbash-Proprietary
@@ -10,7 +10,7 @@ Keywords: atbash,hermes,hermes-agent,agent-safety,ai-safety,tool-guard,judge,pol
 Requires-Python: <3.13,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: atbash-sdk==0.4.7.dev0
+Requires-Dist: atbash-sdk==0.5.0
 Requires-Dist: httpx<1,>=0.27
 Requires-Dist: opentelemetry-exporter-otlp-proto-http<2,>=1.29
 Requires-Dist: opentelemetry-sdk<2,>=1.29
@@ -30,38 +30,24 @@ stopped before execution.
 - Intercepts Hermes tool calls through `pre_tool_call`.
 - Sends the tool name, arguments, command-like payload, session metadata, and
   inferred action class to Atbash.
-- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, or `DISALLOW`; holds it for operator review on `HOLD`.
+- Blocks tool execution on `BLOCK`, `DENY`, `REJECT`, `DISALLOW`, or `HOLD`.
 - Persists learned Hermes tool classifications across sessions.
 
 ## Install
 
-Hermes manages its own Python environment. Install the plugin directly into it —
-do **not** use your system `pip` — on macOS and some Linux distros it will be blocked by the OS.
-
-**If you installed Hermes via the official install script (`curl … | bash`):**
+Install the plugin into the same Python environment that runs Hermes.
+Requires Python 3.10 through 3.12.
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 install atbash-hermes-plugin
+pip install atbash-hermes-plugin==0.4.5
 ```
 
-**If you installed Hermes via `uv`:**
+If Hermes is installed in a virtual environment, use that environment's Python:
 
 ```bash
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python atbash-hermes-plugin
+/path/to/hermes/venv/bin/python -m pip install atbash-hermes-plugin==0.4.5
 ```
 
-To install the latest dev release, add `--pre` (pip) or `--prerelease=allow` (uv):
-
-```bash
-# pip
-~/.hermes/hermes-agent/venv/bin/pip3 install --pre atbash-hermes-plugin
-
-# uv
-uv pip install --python ~/.hermes/hermes-agent/venv/bin/python --prerelease=allow atbash-hermes-plugin
-```
-
-No further activation step is needed — Hermes discovers the plugin automatically on next start.
-
 ## Configure Atbash
 
 The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
@@ -70,10 +56,10 @@ The plugin needs an Atbash agent key. Configure either `ATBASH_KEY_PATH` or
 Recommended:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ```
 
-Alternative (paste the key JSON directly):
+Alternative:
 
 ```bash
 ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
@@ -81,7 +67,7 @@ ATBASH_AGENT_PRIVKEY='{"pubkey":"...","privkey":"..."}'
 
 ## Where To Set Environment Variables
 
-Hermes loads environment variables from `~/.hermes/.env`.
+Hermes commonly loads environment variables from `~/.hermes/.env`.
 
 Create or edit that file:
 
@@ -92,7 +78,7 @@ nano ~/.hermes/.env
 Add:
 
 ```bash
-ATBASH_KEY_PATH=~/.config/atbash/guard-client-key
+ATBASH_KEY_PATH=$HOME/.config/atbash/guard-client-key
 ATBASH_ENFORCE_DECISION=true
 ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
@@ -132,11 +118,7 @@ ATBASH_DEBUG=false
 ATBASH_ORG_NAME=your-org-name
 
 # Override where learned Hermes tool classifications are saved.
-ATBASH_TOOL_MAP_PATH=~/.config/atbash/hermes-tool-map.json
-
-# HTTP request timeout in seconds for judge API calls. Default: 30.
-# Raise this if you see "read operation timed out" errors on a slow endpoint.
-ATBASH_REQUEST_TIMEOUT=30
+ATBASH_TOOL_MAP_PATH=$HOME/.config/atbash/hermes-tool-map.json
 ```
 
 ## Telemetry
@@ -154,13 +136,19 @@ printf '{"enabled": false}\n' > ~/.config/atbash/telemetry.json
 
 ## Enable Or Check The Plugin
 
-Hermes discovers the plugin automatically via Python entry points — no manual
-enable step is needed. Restarting Hermes after installation is sufficient.
+Hermes should discover installed Python packages that expose the
+`hermes_agent.plugins` entry point.
+
+Check whether Hermes sees the plugin:
+
+```bash
+hermes plugins list | grep atbash
+```
 
-To confirm the package is installed in the right environment:
+If needed, enable it:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins enable atbash-hermes-plugin
 ```
 
 ## Verify It Is Working
@@ -171,7 +159,7 @@ file or opening a website.
 In another terminal, watch the Hermes log:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 With `ATBASH_DEBUG=true`, you should see lines similar to:
@@ -266,24 +254,26 @@ user to retry after review, rather than automatically re-running the action.
 
 ## Troubleshooting
 
-If the plugin is not being picked up, confirm it is installed in the Hermes
-environment (not the system Python):
+If Hermes does not show the plugin:
 
 ```bash
-~/.hermes/hermes-agent/venv/bin/pip3 show atbash-hermes-plugin
+hermes plugins list | grep atbash
+python -m pip show atbash-hermes-plugin
 ```
 
-If Atbash verdicts are not appearing in logs, enable debug mode by adding this
-to `~/.hermes/.env`:
+Make sure the package was installed into the same Python environment that runs
+Hermes.
+
+If Atbash verdicts are not appearing in logs:
 
 ```bash
 ATBASH_DEBUG=true
 ```
 
-Then restart Hermes and watch in a second terminal:
+Then restart Hermes and watch:
 
 ```bash
-tail -f ~/.hermes/logs/agent.log | grep -i atbash
+tail -f ~/.hermes/logs/agent.log
 ```
 
 If the plugin blocks everything with an unavailable-key or authentication error,

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/atbash_hermes_plugin.egg-info/requires.txt

@@ -1,4 +1,4 @@
-atbash-sdk==0.4.7.dev0
+atbash-sdk==0.5.0
 httpx<1,>=0.27
 opentelemetry-exporter-otlp-proto-http<2,>=1.29
 opentelemetry-sdk<2,>=1.29

{atbash_hermes_plugin-0.4.6.dev1 → atbash_hermes_plugin-0.4.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "atbash-hermes-plugin"
-version = "0.4.6.dev1"
+version = "0.4.7"
 description = "Atbash safety plugin for Hermes Agent"
 readme = "README.md"
 requires-python = ">=3.9,<3.13"
@@ -24,7 +24,7 @@ keywords = [
   "policy"
 ]
 dependencies = [
-  "atbash-sdk==0.4.7.dev0",
+  "atbash-sdk==0.5.0",
   "httpx>=0.27,<1",
   "opentelemetry-exporter-otlp-proto-http>=1.29,<2",
   "opentelemetry-sdk>=1.29,<2",