report harness version in hermes /tlon version - #6266
Merged
patosullivan merged 2 commits intoAug 13, 2026
Conversation
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
latter-bolden
approved these changes
Aug 13, 2026
patosullivan
merged commit Aug 13, 2026
28a5760
into
patrick/tlon-6300-bots-advertise-their-slash-command-manifests
9 checks passed
patosullivan
deleted the
patrick/tlon-6320-hermes-report-harness-version-in-tlon-version
branch
August 13, 2026 19:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
Harness Versionrow to the Hermes adapter's/tlon versionreply, 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_replyinpackages/hermes-tlon-adapter/version.pytakes an optionalharness_versionand renders*Harness Version*directly beneath*Harness*, matching OpenClaw's row order. An absent or blank value rendersunknown, so the row is never dropped and the two replies stay line-for-line comparable.packages/hermes-tlon-adapter/adapter.py(the startup log line and_version_reply) passself._harness_version(), the existing cached resolver that reads the running agent'shermes_cli.__version__and__release_date__(e.g.0.17.0 (2026.6.19)) with animportlib.metadatafallback.test_version.pyandtest_adapter_owner_listen.py, and a newtest_absent_harness_version_renders_unknowncoversNone, empty, and whitespace input.How did I test?
./dev/test.sh): 1013 tests, all passing.format_version_replyfails 6 tests.Risks and impact
/tlon versionreply and startup log lineRollback plan
Revert
Stacked on #6243 and #6252; retarget to
developonce those merge.