my-project-public

repository

loading code, commits, and activity

repositories

loading repo index

#1	# Clawd Memory Provider for Hermes
#2
#3	Deploy Clawd Memory as a first-class MemoryProvider through Hermes' plugin system.
#4
#5	## What This Gives You
#6
#7	When deployed, Clawd Memory gets the same integration tier as Honcho, mem0, and supermemory:
#8
#9	- System prompt injection — memory context in every prompt
#10	- Pre-turn prefetch — Relevant memories injected via `<memory-context>` fence before each API call
#11	- Post-turn sync — User and assistant messages automatically stored to episodic memory
#12	- Tool dispatch — 15 memory tools auto-injected into the model's tool surface
#13	- CLI commands — `hermes mnemosyne {stats\|sleep\|version\|inspect\|clear\|export\|import}`
#14	- Setup wizard — Listed in `hermes memory setup`
#15
#16	All of this without touching Hermes core. Deployed purely through the plugin directory.
#17
#18	## Deploy
#19
#20	```bash
#21	# One-time setup: symlink into Hermes plugin directory
#22	ln -s $(pwd)/hermes_memory_provider ~/.hermes/plugins/mnemosyne
#23
#24	# Activate in config
#25	hermes config set memory.provider mnemosyne
#26	```
#27
#28	Or manually edit `~/.hermes/config.yaml`:
#29
#30	```yaml
#31	memory:
#32	provider: mnemosyne
#33	mnemosyne:
#34	auto_sleep: true
#35	sleep_threshold: 50
#36	vector_type: float32 # float32 \| int8 \| bit
#37	```
#38
#39	## Verify
#40
#41	```bash
#42	hermes memory status # Should show "mnemosyne" as active provider
#43	hermes mnemosyne stats # Show memory statistics
#44	```
#45
#46	## Architecture
#47
#48	```
#49	~/.hermes/plugins/mnemosyne/ ← symlink to hermes_memory_provider/
#50	├── __init__.py ← MnemosyneMemoryProvider (MemoryProvider ABC)
#51	├── cli.py ← hermes mnemosyne subcommands
#52	├── plugin.yaml ← Manifest for discovery
#53	└── README.md ← This file
#54	```
#55
#56	The provider is discovered by `plugins.memory.discover_memory_providers()` which scans:
#57	1. Bundled providers: `hermes-agent/plugins/memory/<name>/`
#58	2. User plugins: `$HERMES_HOME/plugins/<name>/` ← This is where the Clawd Memory compatibility provider lives
#59
#60	User plugins take precedence over bundled plugins on name collision.
#61
#62	## Tools (Auto-Injected)
#63
#64	\| Tool \| Purpose \|
#65	\|------\|---------\|
#66	\| `mnemosyne_remember` \| Store durable memory with importance, scope, expiry \|
#67	\| `mnemosyne_recall` \| Hybrid search (50% vector + 30% FTS + 20% importance) \|
#68	\| `mnemosyne_stats` \| Show working + episodic counts \|
#69	\| `mnemosyne_triple_add` \| Add temporal facts to the knowledge graph \|
#70	\| `mnemosyne_triple_query` \| Query temporal knowledge graph facts \|
#71	\| `mnemosyne_sleep` \| Consolidate working → episodic memory \|
#72	\| `mnemosyne_scratchpad_write` \| Write short-lived scratchpad context \|
#73	\| `mnemosyne_scratchpad_read` \| Read scratchpad context \|
#74	\| `mnemosyne_scratchpad_clear` \| Clear scratchpad context \|
#75	\| `mnemosyne_invalidate` \| Mark memory as expired/superseded \|
#76	\| `mnemosyne_export` \| Export memories for backup or migration \|
#77	\| `mnemosyne_import` \| Import memories from backup files or providers \|
#78	\| `mnemosyne_update` \| Update an existing memory \|
#79	\| `mnemosyne_forget` \| Delete a memory \|
#80	\| `mnemosyne_diagnose` \| Run diagnostics on the memory store \|
#81
#82	## Undeploy
#83
#84	```bash
#85	rm ~/.hermes/plugins/mnemosyne
#86	hermes config set memory.provider null
#87	```
#88
#89	Hermes falls back to built-in memory only.
#90

z6Mkq5mY3JWtxoxUobWcfNHm7AkRubgSWEZTkBVqZXJviFZ5/my-project-public