harald/nixcfg
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

feat(hermes): deploy swafra memory provider declaratively #45

Open
hermes wants to merge 1 commit from hermes/swafra-memory-provider into main AGit
pull from: hermes/swafra-memory-provider
merge into: harald:main
Conversation 0 Commits 1 Files changed 5 +1288 -1
hermes commented 2026-09-20 22:51:07 +02:00
Contributor
Copy link

Ship the swafra memory provider plugin (packages/swafra-memory-provider,
stdlib-only MCP client, zero pip deps) through services.hermes-agent
.extraPlugins, which the upstream module symlinks into the hermes home as
nix-managed-swafra. Memory providers are addressed by directory name, so
memory.provider is set to that symlink name while the provider's own
config block keeps its fixed 'swafra' key (memory.swafra.base_url points
it at the sgx MCP endpoint). The swafra MCP server entry stays for now —
coexistence, removal is deliberate follow-up once the provider has proven
itself. A dedicated HERMES_SWAFRA_PLUGIN_TRIGGER restarts the gateway
whenever the provider's store path changes, same trick as the Talk
plugin.

Ship the swafra memory provider plugin (packages/swafra-memory-provider, stdlib-only MCP client, zero pip deps) through services.hermes-agent .extraPlugins, which the upstream module symlinks into the hermes home as nix-managed-swafra. Memory providers are addressed by directory name, so memory.provider is set to that symlink name while the provider's own config block keeps its fixed 'swafra' key (memory.swafra.base_url points it at the sgx MCP endpoint). The swafra MCP server entry stays for now — coexistence, removal is deliberate follow-up once the provider has proven itself. A dedicated HERMES_SWAFRA_PLUGIN_TRIGGER restarts the gateway whenever the provider's store path changes, same trick as the Talk plugin.
feat(hermes): deploy swafra memory provider declaratively
All checks were successful
nix flake check / flake-check (pull_request) Successful in 4m0s
Details
2056920fcb 
Ship the swafra memory provider plugin (packages/swafra-memory-provider,
stdlib-only MCP client, zero pip deps) through services.hermes-agent
.extraPlugins, which the upstream module symlinks into the hermes home as
nix-managed-swafra. Memory providers are addressed by directory name, so
memory.provider is set to that symlink name while the provider's own
config block keeps its fixed 'swafra' key (memory.swafra.base_url points
it at the sgx MCP endpoint). The swafra MCP server entry stays for now —
coexistence, removal is deliberate follow-up once the provider has proven
itself. A dedicated HERMES_SWAFRA_PLUGIN_TRIGGER restarts the gateway
whenever the provider's store path changes, same trick as the Talk
plugin.
All checks were successful
nix flake check / flake-check (pull_request) Successful in 4m0s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin +refs/pull/45/head:hermes/swafra-memory-provider
git switch hermes/swafra-memory-provider
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harald/nixcfg!45
No description provided.