Skip to content

Suppress Hermes runtime status in chat#321

Merged
mostlydev merged 1 commit into
masterfrom
issue-257-259-hermes-status-noise
Jun 23, 2026
Merged

Suppress Hermes runtime status in chat#321
mostlydev merged 1 commit into
masterfrom
issue-257-259-hermes-status-noise

Conversation

@mostlydev

Copy link
Copy Markdown
Owner

Summary

  • refresh hermes-base to upstream Hermes v2026.6.19 and publish ghcr.io/mostlydev/hermes-base:v2026.6.19-claw.2
  • keep managed Hermes chat status callbacks and background-review summaries out of content channels by default, with opt-in knobs for debug surfaces
  • rebase Clawdapus Hermes runtime patches onto the upstream module split and update docs/site/changelog

Verification

  • go test ./...
  • go vet ./...
  • go test -tags spike -run TestSpikeHermesBaseImageContract ./cmd/claw
  • npm run build (site)
  • docker buildx imagetools inspect ghcr.io/mostlydev/hermes-base:v2026.6.19-claw.2
  • gh api /users/mostlydev/packages/container/hermes-base --jq "{name, visibility, updated_at}"
  • go run ./scripts/check-release-infra-tags --release-tag v0.23.1

Closes #257
Closes #259

@mostlydev mostlydev merged commit 51201df into master Jun 23, 2026
1 check passed
@mostlydev mostlydev deleted the issue-257-259-hermes-status-noise branch June 23, 2026 18:27
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.

Hermes should keep runtime status telemetry out of chat delivery by default Keep Hermes runtime and scheduler notices out of content channels

1 participant