Watchline for Hermes Agent
Watchline is an event layer for agents. This Hermes plugin delivers matched Watchline events into a local Hermes gateway without exposing your laptop to the internet.
Watchline uses two integration planes:
- Hosted MCP gives Hermes the watch tools:
start_watch,continue_watch,list_watches,pause_watch,resume_watch, anddelete_watch. - This plugin registers a Hermes gateway platform named
watchline. It polls a Watchline pull channel and forwards matched events as inbound Hermes messages.
The plugin intentionally does not duplicate Watchline tools. Hermes discovers tools from the hosted MCP server, and this adapter only handles local delivery.
Install
hermes plugins install qordinate-ai/watchline-hermes-plugin --enable
The package is also available on PyPI:
python -m pip install watchline-hermes-plugin
For local development:
hermes plugins install file:///absolute/path/to/watchline-hermes-plugin --enable
Configure
Create a Watchline API key and pull channel at https://watch.qordinate.ai, then run:
hermes watchline configure \
--api-key wl_... \
--channel-id ch_... \
--user-id me \
--delivery-channel main \
--api-base-url https://api.watch.qordinate.ai
The command writes:
platforms.watchlinefor delivery.mcp_servers.watchlinefor hosted watch tools.
Restart the Hermes gateway after changing plugin or MCP config:
hermes gateway restart
Use
Ask Hermes to use Watchline:
Use the Watchline start_watch tool to watch Gmail for emails from my boss.
Ask me for the sender email address if needed.
When a matching event arrives, Watchline queues it on your pull channel. The plugin polls that channel, runs Hermes against your main/home channel, and acknowledges the delivery only after Hermes accepts it.
Why a Hermes Plugin?
Hermes also has a built-in webhook adapter for external events. That is a good option when your Hermes gateway already has a public URL, reverse proxy, or tunnel and you want Watchline to push matched events directly into Hermes.
This plugin uses Watchline pull delivery instead. Hermes runs locally, polls the Watchline channel, and injects matched events into the gateway without requiring your Hermes agent to expose an inbound webhook endpoint online. You can still use Hermes webhooks separately for deployments where a public callback URL is already part of your setup.
Commands
hermes watchline status
hermes watchline install-mcp
hermes watchline preview-delivery
Configuration Reference
| Field | Required | Description |
|---|---|---|
api_key |
Yes | Watchline project API key. |
channel_id |
Yes | Watchline pull channel ID. |
user_id |
No | Stable Watchline user id. Defaults to me. |
api_base_url |
No | Watchline API base URL. Defaults to production. |
poll_interval_seconds |
No | Delivery polling interval. Minimum is 5 seconds. |
delivery_channel |
No | Hermes delivery target. Defaults to main, the first configured home channel. Use telegram, discord, or telegram:<chat_id>[:thread_id] to override. |
Links
1 maintainer
Metadata
1 maintainer
Release files for watchline-hermes-plugin 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| watchline_hermes_plugin-0.1.4.tar.gz | 12.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| watchline_hermes_plugin-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.4 kB
Release files / watchline_hermes_plugin-0.1.4.tar.gz
| Download URL | watchline_hermes_plugin-0.1.4.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dafa387e72ab8aa6b451cc3c19461b9f197ea415546c4e8850c9dc06504902f9
|
|
BLAKE2b-256 checksum How to use checksums |
7b92964f073611ceaf5b183c56554c2c20b2cb1baa22ce375ec35547a630b1bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency logRelease files / watchline_hermes_plugin-0.1.4-py3-none-any.whl
| Download URL | watchline_hermes_plugin-0.1.4-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b7c5c8ee095244b755fe966c3f81e937cfee6012f630370e7ba058a7601648a
|
|
BLAKE2b-256 checksum How to use checksums |
d844ebaaee94ff8902412cf543e16fa4b49c7d3701c23e1e07126db6c6aa57a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency log
