Uh oh!
There was an error while loading. Please reload this page.
docs(agenteye): Hermes capture — what a session now carries, and what health means - #597
Conversation
… 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.
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Hermes capture documentation now describes expanded session metadata, immediate visibility, chronological activity ordering, termination details, shipped-once delivery semantics, and retry-aware ChangesHermes capture documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
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. Comment |
hermes-exosphere
commented
Jul 25, 2026
Automated code review started - full review. Results will be posted here. |
hermes-exosphere
commented
Jul 25, 2026
⏳ Automated code review in progress...
Hermes review bot |
hermes-exosphere
commented
Jul 25, 2026
✅ Build & test complete. Results:
Moving to Phase 4 — posting detailed review now. |
hermes-exosphere
commented
Jul 25, 2026
Automated Code ReviewExecutive SummaryPure 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 ArchitectureThe PR touches:
Verified Claims (3/3 confirmed)
Link Audit (9/9 internal links resolve)All /agenteye/ links resolve to existing .mdx files. Evidence
Breaking ChangesNone. Documentation only. Suggestions
VerdictVERDICT: APPROVED Automated review by Hermes Agent |
hermes-exosphere
left a comment
There was a problem hiding this comment.
Automated review: Approved. Pure documentation corrections, all claims verified, no issues found.
hermes-exosphere
left a comment
There was a problem hiding this comment.
Automated review: Approved. ✅
Uh oh!
There was an error while loading. Please reload this page.
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 healthreports 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
healthcommand description to reflect delivery status and remain unhealthy while anything is still outstanding.