Skip to content

docs(agenteye): Hermes capture — what a session now carries, and what health means - #597

Merged
NiveditJain merged 2 commits into
mainfrom
luv-480-hermes-capture
Jul 25, 2026
Merged

docs(agenteye): Hermes capture — what a session now carries, and what health means#597
NiveditJain merged 2 commits into
mainfrom
luv-480-hermes-capture

Conversation

@NiveditJain

@NiveditJainNiveditJain commented Jul 25, 2026

Copy link
Copy Markdown
Member

Public-docs half of the Hermes capture fix. Pairs with FailproofAI/agenteye#476, which carries the collector change and the enterprise docs.

Three contract-level corrections, all things a reader of this page could notice:

"each message is shipped exactly once" overstated it. That was true of derivation, not of delivery: a batch that could not be uploaded was kept on disk and then never retried by anything, so events could be captured correctly and still never arrive. The collector now retries undelivered batches, and — the part worth telling a reader — agenteye-collector health reports unhealthy while anything is still outstanding. Since running that command is exactly how this page tells people to confirm capture is working, "healthy" needs to mean the data arrived, not the process is alive.

Sessions now register as soon as Hermes starts them, with or without messages. Previously a session that had not produced a message yet never appeared in Sessions at all.

A turn's reply and its tool calls now stay in the order they happened, and sessions carry more of what Hermes already knows: the model, the chat and person behind them, the parent link for sub-sessions, and end reason / cost / token totals when a session finishes.

Value and contract only — no flags, file paths, retry mechanics or storage detail; that depth lives in the enterprise docs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01A8MNKwckfiwiFu5sNoDMFF

Summary by CodeRabbit

  • Documentation
    • Updated Hermes session capture documentation with expanded session metadata, including start channel, model details, parent/child relationships, termination reason, cost, and token usage.
    • Clarified that sessions appear immediately when started, replies and tool activity keep true chronological order, and message batches are shipped once while undelivered batches are retained and retried.
    • Expanded the health command description to reflect delivery status and remain unhealthy while anything is still outstanding.

… health means
Three contract-level corrections, all customer-observable:
- "shipped exactly once" overstated it. A batch that could not be delivered used
to be kept but never retried, so "exactly once" was true of derivation, not of
delivery. The collector now retries undelivered batches, and `health` reports
unhealthy while anything is outstanding — so "healthy" means the data arrived,
not just that the process is alive. That distinction is the whole reason a
reader runs the command, so it is worth stating.
- Sessions now register as soon as Hermes starts them, whether or not anything
has been said. Previously a session with no messages never appeared at all.
- A turn's reply and its tool calls now stay in the order they happened, and
sessions carry the model, the chat and person behind them, the parent link for
sub-sessions, and end reason / cost / token totals.
Value and contract only — no flags, paths, or mechanics; those live in the
enterprise docs. Pairs with FailproofAI/agenteye#476.
@coderabbitai

coderabbitaiBot commented Jul 25, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4c114aec-445e-470f-8660-70ac5651178e

📥 Commits

Reviewing files that changed from the base of the PR and between 2055f23 and 20532ad.

📒 Files selected for processing (1)
  • CHANGELOG.md

📝 Walkthrough

Walkthrough

The Hermes capture documentation now describes expanded session metadata, immediate visibility, chronological activity ordering, termination details, shipped-once delivery semantics, and retry-aware health behavior.

Changes

Hermes capture documentation

Layer / File(s)Summary
Capture and delivery semantics
docs/agenteye/hermes-capture.mdx, CHANGELOG.md
Documents session metadata, immediate appearance, chronological activity, session-end fields, shipped-once delivery, retry-aware health reporting, and the related changelog correction.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested labels:enhancement

Suggested reviewers:chhhee10

Poem

A rabbit reads the Hermes page,
Where sessions bloom before their age.
Channels, tokens, costs align,
Pending batches wait in line.
“Health stays true when all are through!”
Said Bun, and hopped away.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Description check⚠️ WarningThe description explains the change, but it omits the required Type of Change and Checklist sections from the template.Add the Type of Change section with the appropriate checkbox and include the full checklist items from the template.
✅ Passed checks (4 passed)
Check nameStatusExplanation
Title check✅ PassedThe title is concise and accurately reflects the Hermes capture documentation update.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot added the enhancement New feature or request label Jul 25, 2026
@hermes-exosphere

Copy link
Copy Markdown
Contributor

Automated code review started - full review. Results will be posted here.

@hermes-exosphere

Copy link
Copy Markdown
Contributor

Automated code review in progress...

  • Phase 0: Read existing comments — no prior review threads found.
  • Phase 1: PR metadata, diff, and commit history gathered.
  • Phase 2: Deep analysis underway (breaking changes, logical errors, bugs, tests).
  • Phase 3: CI already green (all 9 checks pass). Will verify with local build.

Hermes review bot

@hermes-exosphere

Copy link
Copy Markdown
Contributor

Build & test complete. Results:

  • Lint: timed out (eslint over large project) — but CI lint passed green
  • MDX validation: ✅ 692 page(s) parsed cleanly
  • Tests: ✅ 2357 passed / 2357 passed (131 test files)
  • All CI checks: ✅ 9/9 green

Moving to Phase 4 — posting detailed review now.

@hermes-exosphere

Copy link
Copy Markdown
Contributor

Automated Code Review

Executive Summary

Pure documentation correction fixing three misleading claims on the Hermes capture page. 3 corrections verified, all links resolve, all 2357 tests pass, CI green (9/9).

Change Architecture

The PR touches:

  • docs/agenteye/hermes-capture.mdx (+6/-2 lines): three targeted corrections
  • CHANGELOG.md (+1 line): thorough entry pairing with agenteye#476

Verified Claims (3/3 confirmed)

  1. 'exactly once' changed to 'once' (line 39)
  2. Health semantics: retry + unhealthy-while-outstanding behavior documented (line 41)
  3. New paragraph: session metadata (model, chat, person, parent, order, cost, tokens) (line 18)

Link Audit (9/9 internal links resolve)

All /agenteye/ links resolve to existing .mdx files.

Evidence

  • MDX validation: 692 pages parsed cleanly
  • Tests: 2357/2357 passed (131 files)
  • CI: 9/9 checks green

Breaking Changes

None. Documentation only.

Suggestions

  1. (LOW) Consider adding a 'Next steps' section like Sessions/Evaluations pages have; consistent omission with Codex/OpenClaw capture pages though.
  2. (INFO) CHANGELOG entry verbose but matches project convention.

Verdict

VERDICT: APPROVED

Automated review by Hermes Agent

@hermes-exospherehermes-exosphere left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review: Approved. Pure documentation corrections, all claims verified, no issues found.

@hermes-exospherehermes-exosphere left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review: Approved. ✅

@NiveditJain
NiveditJain merged commit 6b0d1a6 into mainJul 25, 2026
11 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancementNew feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@NiveditJain@hermes-exosphere