jupyter-hermes-proxy 0.1.0

Jupyter server proxy for Hermes Agent dashboard

jupyter-hermes-proxy

Launch the Hermes Agent dashboard from JupyterLab as a native launcher entry.

Features

• One-click launch from the JupyterLab launcher panel with a custom Hermes icon
• Automatic port management via jupyter-server-proxy
• Works behind reverse proxies (no manual port forwarding needed)
• Two modes: spawn a new dashboard, or connect to an existing one
• Configurable Hermes executable path via HERMES_BIN_PATH

Installation

pip install jupyter-hermes-proxy

Then restart JupyterLab. The "Hermes Dashboard" launcher entry will appear automatically.

Configuration

Spawn mode (default)

By default the proxy searches for hermes in PATH and spawns a new dashboard process when you click the launcher.

Override the binary path:

export HERMES_BIN_PATH=/path/to/hermes

URL mode (connect to existing dashboard)

When Hermes dashboard is already running (e.g. supervised by s6 in Docker), point the proxy at it:

export HERMES_DASHBOARD_URL=http://127.0.0.1:9119

In this mode the proxy does not spawn a new process — it simply proxies traffic to the existing dashboard. No hermes binary on PATH is required.

Related Packages

• jupyter-ai-hermes — Hermes Agent as an ACP persona for Jupyter AI chat, with live notebook context injection and MCP tools for cell management.

Both packages share the same HERMES_BIN_PATH environment variable convention.

Development

git clone [e-mail]:dive4dec/jupyter-hermes-proxy.git
cd jupyter-hermes-proxy
pip install -e .

How It Works

This package registers a server spec under the jupyter_serverproxy_servers entry point.

• Spawn mode: jupyter-server-proxy calls setup_hermes() which returns a command that spawns hermes dashboard on an ephemeral port and proxies it through the Jupyter server.
• URL mode: setup_hermes() returns the pre-existing dashboard URL directly, so jupyter-server-proxy connects to it without spawning anything.

License

MIT