forge-hermes-plugin 0.2.19__tar.gz

forge_hermes_plugin-0.2.19/MANIFEST.in

@@ -0,0 +1,4 @@
+include README.md
+recursive-include forge_hermes *.md
+recursive-include forge_hermes/scripts *.mjs
+recursive-include forge_hermes/runtime *

forge_hermes_plugin-0.2.19/PKG-INFO

@@ -0,0 +1,81 @@
+Metadata-Version: 2.4
+Name: forge-hermes-plugin
+Version: 0.2.19
+Summary: Curated Hermes plugin for the Forge life operating system
+Author: Forge
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/albertbuchard/forge/tree/main/plugins/forge-hermes
+Project-URL: Repository, https://github.com/albertbuchard/forge
+Project-URL: Issues, https://github.com/albertbuchard/forge/issues
+Keywords: forge,hermes,agent,plugin,productivity
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+
+# Forge Hermes Plugin
+
+Hermes plugin for Forge.
+
+This plugin follows the Hermes plugin guide directly:
+
+- a Python package with a `hermes_agent.plugins` entry point for pip discovery
+- a Hermes plugin manifest and registration module that expose Forge to Hermes
+- bundled Forge runtime assets so Hermes can start Forge safely without repo-only runtime imports
+
+It exposes the same curated Forge contract as the OpenClaw adapter, but through Hermes' Python plugin system.
+
+## Install
+
+From the Forge repo:
+
+```bash
+~/.hermes/hermes-agent/venv/bin/python -m ensurepip --upgrade
+~/.hermes/hermes-agent/venv/bin/python -m pip install --upgrade ./plugins/forge-hermes
+```
+
+That installs the package into Hermes' own Python environment through `pip`, creates
+`~/.hermes/forge/config.json` automatically on first plugin load if it is missing, and defaults the Forge runtime data root to
+`~/.hermes/forge` so local Hermes usage does not write into the repo root.
+
+Use `~/.hermes/hermes-agent/venv/bin/python` so the package lands in the Python
+environment Hermes actually runs and Hermes can discover Forge through the package
+entry point on the next startup.
+
+If you want editable package mode while developing from this repo:
+
+```bash
+~/.hermes/hermes-agent/venv/bin/python -m ensurepip --upgrade
+~/.hermes/hermes-agent/venv/bin/python -m pip install --upgrade --editable ./plugins/forge-hermes
+```
+
+## Runtime behavior
+
+- defaults to `FORGE_ORIGIN=http://127.0.0.1` and `FORGE_PORT=4317`
+- defaults `FORGE_ACTOR_LABEL` to `hermes`
+- defaults `FORGE_DATA_ROOT` to `~/.hermes/forge`
+- supports `FORGE_API_TOKEN` for remote or explicitly scoped access
+- supports `FORGE_DATA_ROOT` when you want Forge to use a specific local data folder
+- when Forge is local and not already running, the plugin calls the repo's tested Forge local-runtime bootstrap helper instead of maintaining a separate startup implementation
+- when port `4317` is busy and not explicitly pinned, the shared runtime helper can move Forge to the next free localhost port and remember that preferred port
+- if another Forge runtime is already serving the wrong storage root, startup fails loudly instead of attaching to the wrong database
+
+## Environment variables
+
+- `FORGE_ORIGIN`
+- `FORGE_PORT`
+- `FORGE_API_TOKEN`
+- `FORGE_ACTOR_LABEL`
+- `FORGE_TIMEOUT_MS`
+- `FORGE_DATA_ROOT`
+
+## Notes
+
+- the recommended install path is now pip-based Hermes entry-point discovery, not the old folder-plugin symlink
+- edit `~/.hermes/forge/config.json` if you want to move the data root or pin a different local port
+- the bundled skill is installed automatically on first plugin load if `~/.hermes/skills/forge-hermes/SKILL.md` does not already exist

forge_hermes_plugin-0.2.19/README.md

@@ -0,0 +1,61 @@
+# Forge Hermes Plugin
+
+Hermes plugin for Forge.
+
+This plugin follows the Hermes plugin guide directly:
+
+- a Python package with a `hermes_agent.plugins` entry point for pip discovery
+- a Hermes plugin manifest and registration module that expose Forge to Hermes
+- bundled Forge runtime assets so Hermes can start Forge safely without repo-only runtime imports
+
+It exposes the same curated Forge contract as the OpenClaw adapter, but through Hermes' Python plugin system.
+
+## Install
+
+From the Forge repo:
+
+```bash
+~/.hermes/hermes-agent/venv/bin/python -m ensurepip --upgrade
+~/.hermes/hermes-agent/venv/bin/python -m pip install --upgrade ./plugins/forge-hermes
+```
+
+That installs the package into Hermes' own Python environment through `pip`, creates
+`~/.hermes/forge/config.json` automatically on first plugin load if it is missing, and defaults the Forge runtime data root to
+`~/.hermes/forge` so local Hermes usage does not write into the repo root.
+
+Use `~/.hermes/hermes-agent/venv/bin/python` so the package lands in the Python
+environment Hermes actually runs and Hermes can discover Forge through the package
+entry point on the next startup.
+
+If you want editable package mode while developing from this repo:
+
+```bash
+~/.hermes/hermes-agent/venv/bin/python -m ensurepip --upgrade
+~/.hermes/hermes-agent/venv/bin/python -m pip install --upgrade --editable ./plugins/forge-hermes
+```
+
+## Runtime behavior
+
+- defaults to `FORGE_ORIGIN=http://127.0.0.1` and `FORGE_PORT=4317`
+- defaults `FORGE_ACTOR_LABEL` to `hermes`
+- defaults `FORGE_DATA_ROOT` to `~/.hermes/forge`
+- supports `FORGE_API_TOKEN` for remote or explicitly scoped access
+- supports `FORGE_DATA_ROOT` when you want Forge to use a specific local data folder
+- when Forge is local and not already running, the plugin calls the repo's tested Forge local-runtime bootstrap helper instead of maintaining a separate startup implementation
+- when port `4317` is busy and not explicitly pinned, the shared runtime helper can move Forge to the next free localhost port and remember that preferred port
+- if another Forge runtime is already serving the wrong storage root, startup fails loudly instead of attaching to the wrong database
+
+## Environment variables
+
+- `FORGE_ORIGIN`
+- `FORGE_PORT`
+- `FORGE_API_TOKEN`
+- `FORGE_ACTOR_LABEL`
+- `FORGE_TIMEOUT_MS`
+- `FORGE_DATA_ROOT`
+
+## Notes
+
+- the recommended install path is now pip-based Hermes entry-point discovery, not the old folder-plugin symlink
+- edit `~/.hermes/forge/config.json` if you want to move the data root or pin a different local port
+- the bundled skill is installed automatically on first plugin load if `~/.hermes/skills/forge-hermes/SKILL.md` does not already exist

forge_hermes_plugin-0.2.19/forge_hermes/__init__.py

@@ -0,0 +1,50 @@
+"""Forge Hermes plugin package."""
+
+from __future__ import annotations
+
+import logging
+import shutil
+from pathlib import Path
+
+from .catalog import TOOL_CATALOG
+from .config import ensure_plugin_config
+from .schemas import SCHEMAS
+from .tools import build_handler
+from .version import __version__
+
+logger = logging.getLogger(__name__)
+PACKAGE_DIR = Path(__file__).resolve().parent
+
+
+def _install_skill() -> None:
+    try:
+        from hermes_cli.config import get_hermes_home  # type: ignore
+
+        destination = get_hermes_home() / "skills" / "forge-hermes" / "SKILL.md"
+    except Exception:
+        destination = Path.home() / ".hermes" / "skills" / "forge-hermes" / "SKILL.md"
+
+    if destination.exists():
+        return
+
+    source = PACKAGE_DIR / "skill.md"
+    if not source.exists():
+        return
+
+    destination.parent.mkdir(parents=True, exist_ok=True)
+    shutil.copy2(source, destination)
+
+
+def register(ctx) -> None:
+    ensure_plugin_config()
+
+    for spec in TOOL_CATALOG:
+        ctx.register_tool(
+            name=spec["name"],
+            toolset="forge",
+            schema=SCHEMAS[spec["name"]],
+            handler=build_handler(spec["name"]),
+        )
+
+    _install_skill()
+    logger.info("Registered Forge Hermes plugin with %s tools", len(TOOL_CATALOG))