refactor: rename Hermes → Engram#22
Merged
Merged
Conversation
Renames the daemon to Engram. Internal paths now derive from each file's own location (Path(__file__).parent), so the ~/hermes → ~/engram move needs zero path edits and the .venv follows the folder. - hermes.py → engram.py; module docstring + user-facing strings ([ENGRAM], 'Engram starting up', 'Engram commands', session prefix engram-*). - Dual trigger prefix: accepts [ENGRAM] (new) and [HERMES] (muscle-memory); both optional. config trigger_prefix → [ENGRAM]. - project_registry: repo key 'engram' (path from __file__), 'hermes'→'engram' alias so old references still route. - Tests: import engram; sys.path derived from __file__ so they pass before AND after the dir move. - KEPT as-is on purpose: keychain service 'hermes-telegram-bot' (live token), internal markers (## Hermes Run Log, hermes-meta) and /api/hermes/* routes (renaming would orphan existing data / break the Mission Control UI). Live migration (dir move, launchd label, GitHub repo) done separately after merge. Tests: 165 pass / 1 skip. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Renames the daemon Hermes → Engram to disambiguate from Nous Research's
hermes-agent(which we're adopting as the separate home-assistant per the comparison decision).Key move: internal paths now derive from
Path(__file__).parentinstead of hardcoded~/hermes, so the~/hermes → ~/engramfolder move needs zero path edits and the.venvfollows the folder. Tests use the same trick so they pass before and after the move.hermes.py→engram.py; docstring + user-facing strings updated ([ENGRAM], "Engram starting up/commands",engram-*session prefix).[ENGRAM](new) and[HERMES](your muscle-memory) — both optional.project_registry:engramkey +hermes → engramalias so old routes still work.hermes-telegram-bot(that's where the live bot token is — renaming breaks auth), internal markers (## Hermes Run Log,hermes-meta— renaming orphans existing data), and/api/hermes/*Mission Control routes (frontend depends on them).The live parts (folder move, launchd label
dev.arbiterai.engram, GitHub repo rename) happen right after merge, then reload + verify.Tests: 165 pass / 1 skip. Full rename approved by Jaiden.
🤖 Generated with Claude Code