NVIDIA NeMo Fabric Hermes Agent Adapter

This adapter runs Hermes Agent through its Python SDK.

Install

To install just the Hermes adapter by itself:

pip install "nemo-fabric[adapters-hermes]"

To install just the Hermes adapter along with the NeMo Fabric Runtime:

pip install "nemo-fabric[adapters-hermes, runtime]"

What It Maps

The adapter receives a normalized payload from Fabric and materializes Hermes-native configuration for:

model provider, model name, base URL, temperature, and token settings;
workspace and terminal settings;
Fabric skills as Hermes external skill directories;
Fabric MCP servers as Hermes MCP server config;
tools.blocked as Hermes disabled toolsets, unioned with harness.settings.disabled_toolsets;
optional NeMo Relay telemetry plugin configuration.

hermes_home configures a base directory. The adapter creates a child under runtimes/<runtime_id> so invocations in one Fabric runtime share Hermes state without sharing config or the session database with another runtime.

Execution Model

Each Fabric runtime starts one local adapter host, constructs one Hermes AIAgent, and opens one SessionDB. Ordered Runtime.invoke(...) calls reuse those native objects and pass the prior turn's returned transcript back to run_conversation(...). Runtime stop calls the agent's idempotent close() method, closes the session database, and releases the Relay plugin context when enabled.

Hermes Relay telemetry is finalized after each Fabric invocation so its ATOF and ATIF artifacts are complete when that invocation returns. This telemetry boundary does not recreate the AIAgent or SessionDB.

Maintaining The Adapter

Keep fabric-adapter.json aligned with the Python implementation:

contract_version must match the adapter contract supported by Fabric core.
adapter_id is the stable id selected by harness.adapter_id.
adapter_kind is python because Fabric can invoke it through Python.
runner.module names the persistent host module that Fabric invokes with python -m.
requirements powers fabric doctor; keep required env vars, binaries, or packages current.
config.accepts must match the Fabric sections this adapter maps into Hermes.
telemetry.providers declares provider-specific outputs and integration modes the adapter can produce or forward.

Do not put end-user agent settings in this directory. Users vary harness, model, skills, MCP, tools, telemetry, and runtime behavior through complete typed FabricConfig values and ordinary Python composition. The adapter descriptor describes adapter capabilities; it is not an agent configuration. Add descriptor fields only when Fabric core or the SDK actually uses them.

Metadata

Release files for nemo-fabric-adapters-hermes 0.1.0a20260722

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nemo-fabric-adapters-hermes 0.1.0a20260722
File	Size	Uploaded
nemo_fabric_adapters_hermes-0.1.0a20260722.tar.gz	6.2 kB	Jul 22, 2026	Details

Release files / nemo_fabric_adapters_hermes-0.1.0a20260722.tar.gz

Download URL	nemo_fabric_adapters_hermes-0.1.0a20260722.tar.gz
Size	6.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`ca38c94161d09f4cc3e8022eedb73570b17d817a33cbbbff8aea0d1c4ff246e7`
BLAKE2b-256 checksum How to use checksums	`3a56d82d80b537b441bde51ea52c48a58736122352f07b73c9680dfb1851ccf5`
Upload date	Jul 22, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.14.6`