feat(cli): aggregate Hermes profiles in scheduled sync - #68
Open
kvnloo wants to merge 1 commit into
Open
Conversation
Author
|
Maintainer-ready evidence for exact head |
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.
Problem
Scheduled sync captures
HERMES_HOMEonly when users set it explicitly. Hermes Agent isolates named profiles under.hermes/profiles/<name>/state.db, so the service installed by tokenmaxxing can miss profile usage even though ccusage supports multiple comma-separated Hermes roots. This extends the Hermes support merged in #65; it does not replace or duplicate that integration.Approach
state.dbfiles whenHERMES_HOMEis absent.HERMES_HOMEunchanged.Tests
bun test apps/cli/src/commands/service.test.ts(90 passed)bun run test(all workspace suites passed; CLI 254 tests)bun run typecheckbun run lint(passes with one unrelated existing warning)bun run fmtbun run buildSecurity and compatibility
Discovery never scans outside the canonical per-user Hermes root and fails closed for escaped or unrepresentable paths. Existing explicit configuration keeps precedence. No API, server schema, or ccusage wire changes are required. Filesystem discovery failures do not block non-Hermes scheduled sync.
Scope
This PR changes only CLI service environment discovery and its tests.