What problem are you trying to solve?
What problem are you trying to solve?
Hermes Agent (https://github.com/nousresearch/hermes-agent) is Nous Research's
open-source agent harness — a fast-growing project (~27k stars) with a persistent
agent loop that runs code, browses, and connects to many messaging platforms.
Users running Hermes have no way to get full-fidelity observability of their agent
runs in Latitude today. Arize already ships observability for Hermes, so there's
both a proven integration path and competitive pressure.
What would you like to happen?
Ship a @latitude-data/hermes-telemetry package following the same pattern as our
existing harness integrations (@latitude-data/pi-telemetry,
@latitude-data/claude-code-telemetry, @latitude-data/openclaw-telemetry):
- A Hermes plugin/hook/extension that streams each session to Latitude as OTLP
traces — user prompts, model turns, tool calls, tool results, token usage, and
the real system prompt that reached the model.
- A one-shot
npx -y @latitude-data/hermes-telemetry install flow that prompts for
API key + project slug and wires the hook into Hermes's config.
- Docs page under
docs/telemetry/frameworks/ (or a new "agent harnesses" section).
Alternatives you've considered
Users can hand-roll the generic OTEL exporter (docs/telemetry/otel-exporter.md),
but that loses the turnkey install and the harness-specific span tree that makes
the other integrations valuable.
What would you like to happen?
No response
Alternatives you've considered
No response
What problem are you trying to solve?
What problem are you trying to solve?
Hermes Agent (https://github.com/nousresearch/hermes-agent) is Nous Research's
open-source agent harness — a fast-growing project (~27k stars) with a persistent
agent loop that runs code, browses, and connects to many messaging platforms.
Users running Hermes have no way to get full-fidelity observability of their agent
runs in Latitude today. Arize already ships observability for Hermes, so there's
both a proven integration path and competitive pressure.
What would you like to happen?
Ship a
@latitude-data/hermes-telemetrypackage following the same pattern as ourexisting harness integrations (
@latitude-data/pi-telemetry,@latitude-data/claude-code-telemetry,@latitude-data/openclaw-telemetry):traces — user prompts, model turns, tool calls, tool results, token usage, and
the real system prompt that reached the model.
npx -y @latitude-data/hermes-telemetry installflow that prompts forAPI key + project slug and wires the hook into Hermes's config.
docs/telemetry/frameworks/(or a new "agent harnesses" section).Alternatives you've considered
Users can hand-roll the generic OTEL exporter (
docs/telemetry/otel-exporter.md),but that loses the turnkey install and the harness-specific span tree that makes
the other integrations valuable.
What would you like to happen?
No response
Alternatives you've considered
No response