[codex] sync skills to named client profiles#11
Merged
Conversation
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.
Summary
hermesto all configured named instances such ashermes:devRoot cause
Hermes isolates both MCP configuration and Skill discovery by profile. Syncing only the default
hermesroot left named profiles without the shared Memory Loop Skill. The previous metadata wording also allowed agents to omit the client or invent placeholder session values.Impact
Newly configured Hermes profiles receive the same shared Skills without duplicating registry entries. Recall telemetry can distinguish Hermes calls reliably, while unknown session IDs are omitted instead of fabricated.
Validation
python3 -m pytest -q(160 passed)python3 -m compileall -q dna.py dna scripts testspython3 scripts/check_public_safety.pygit diff --check