Skip to content

report harness version in hermes /tlon version - #6266

Merged
patosullivan merged 2 commits into
patrick/tlon-6300-bots-advertise-their-slash-command-manifestsfrom
patrick/tlon-6320-hermes-report-harness-version-in-tlon-version
Aug 13, 2026
Merged

report harness version in hermes /tlon version#6266
patosullivan merged 2 commits into
patrick/tlon-6300-bots-advertise-their-slash-command-manifestsfrom
patrick/tlon-6320-hermes-report-harness-version-in-tlon-version

Conversation

@patosullivan

@patosullivan patosullivan commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary

Adds a Harness Version row to the Hermes adapter's /tlon version reply, reporting the running Hermes Agent's own version. OpenClaw already emits this row, so both harnesses now answer with the same field-per-line summary. Fixes TLON-6320.

Changes

  • format_version_reply in packages/hermes-tlon-adapter/version.py takes an optional harness_version and renders *Harness Version* directly beneath *Harness*, matching OpenClaw's row order. An absent or blank value renders unknown, so the row is never dropped and the two replies stay line-for-line comparable.
  • Both call sites in packages/hermes-tlon-adapter/adapter.py (the startup log line and _version_reply) pass self._harness_version(), the existing cached resolver that reads the running agent's hermes_cli.__version__ and __release_date__ (e.g. 0.17.0 (2026.6.19)) with an importlib.metadata fallback.
  • Assertions that pin the reply's line positions are updated in test_version.py and test_adapter_owner_listen.py, and a new test_absent_harness_version_renders_unknown covers None, empty, and whitespace input.

How did I test?

  • Full Hermes adapter suite (./dev/test.sh): 1013 tests, all passing.
  • Mutation check: deleting the new row from format_version_reply fails 6 tests.

Risks and impact

  • Safe to rollback without consulting PR author? Yes
  • Affects important code area:
    • Onboarding
    • State / providers
    • Message sync
    • Channel display
    • Notifications
    • Other: Hermes bot /tlon version reply and startup log line

Rollback plan

Revert

Stacked on #6243 and #6252; retarget to develop once those merge.

OpenClaw's reply carries a Harness Version row naming its host runtime;
the Hermes reply had no equivalent, so the two harnesses answered with
different shapes despite the README describing one field-per-line summary.

Render the row directly beneath Harness, sourced from the adapter's
existing cached resolver. An absent or blank value reads `unknown` rather
than dropping the row, matching OpenClaw, so the replies stay line-for-line
comparable.

The chat-reply assertions bind to a sentinel the resolver alone can supply:
a regex for "some nonempty string" stays green when the wiring is removed
and every bot silently reports `unknown`.
…-their-slash-command-manifests' into patrick/tlon-6320-hermes-report-harness-version-in-tlon-version
@linear-code

linear-code Bot commented Aug 12, 2026

Copy link
Copy Markdown

TLON-6320

@patosullivan
patosullivan merged commit 28a5760 into patrick/tlon-6300-bots-advertise-their-slash-command-manifests Aug 13, 2026
9 checks passed
@patosullivan
patosullivan deleted the patrick/tlon-6320-hermes-report-harness-version-in-tlon-version branch August 13, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants