MemPalace v3.0.0 — Ezra Integration Packet

This packet turns issue #570 into an executable, reviewable integration plan for Ezra's Hermes home. It is a repo-side scaffold: no live Ezra host changes are claimed in this artifact.

Commands

pip install mempalace==3.0.0
mempalace init ~/.hermes/ --yes
cat > ~/.hermes/mempalace.yaml <<'YAML'
wing: ezra_home
palace: ~/.mempalace/palace
rooms:
  - name: sessions
    description: Conversation history and durable agent transcripts
    globs:
      - "*.json"
      - "*.jsonl"
  - name: config
    description: Hermes configuration and runtime settings
    globs:
      - "*.yaml"
      - "*.yml"
      - "*.toml"
  - name: docs
    description: Notes, markdown docs, and operating reports
    globs:
      - "*.md"
      - "*.txt"
people: []
projects: []
YAML
echo "" | mempalace mine ~/.hermes/
echo "" | mempalace mine ~/.hermes/sessions/ --mode convos
mempalace search "your common queries"
mempalace wake-up
hermes mcp add mempalace -- python -m mempalace.mcp_server

Manual config template

wing: ezra_home
palace: ~/.mempalace/palace
rooms:
  - name: sessions
    description: Conversation history and durable agent transcripts
    globs:
      - "*.json"
      - "*.jsonl"
  - name: config
    description: Hermes configuration and runtime settings
    globs:
      - "*.yaml"
      - "*.yml"
      - "*.toml"
  - name: docs
    description: Notes, markdown docs, and operating reports
    globs:
      - "*.md"
      - "*.txt"
people: []
projects: []

Why this shape

wing: ezra_home matches the issue's Ezra-specific integration target.
rooms split the mined material into sessions, config, and docs to keep retrieval interpretable.
Mining commands pipe empty stdin to avoid the interactive entity-detector hang noted in the evaluation.

Gotchas

mempalace init is still interactive in room approval flow; write mempalace.yaml manually if the init output stalls.
The yaml key is wing: not wings:. Using the wrong key causes mine/setup failures.
Pipe empty stdin into mining commands (echo "" | ...) to avoid the entity-detector stdin hang on larger directories.
First mine downloads the ChromaDB embedding model cache (~79MB).
Report Ezra's before/after metrics back to issue #568 after live installation and retrieval tests.

Report back to #568

After live execution on Ezra's actual environment, post back to #568 with:

install result
mine duration and corpus size
2-3 real search queries + retrieved results
wake-up context token count
whether MCP wiring succeeded

Honest scope boundary

This repo artifact does not prove live installation on Ezra's host. It makes the work reproducible and testable so the next pass can execute it without guesswork.

2.7 KiB Raw Blame History