jiayan-xu/dsh-memoria-extra
Advanced memoria tools: session context injection (profile + recall), recent decisions, health report, namespace allowlist, memory relation graph, and entity search; companion to dsh-memoria.
Listed
0
Memory
Bundle verified
What it does
Advanced memoria tools: session context injection (profile + recall), recent decisions, health report, namespace allowlist, memory relation graph, and entity search; companion to dsh-memoria.
Best for
- Existing memoria users who need session context assembled from profiles and recalled memories.
- Agents that need recent decision retrieval or entity search over memoria data.
- Operators inspecting authorized namespaces, memory relationships, or service and index health.
Not ideal for
- Users without the companion memoria setup and a reachable memoria service.
- Health checks where no `MEMORIA_ADMIN_KEY` is available, because that tool uses the admin identity.
- Analyses requiring a complete large relation graph in one response; sampling is capped at 5,000 and output at 50 nodes and 50 edges.
- Basic remember and recall workflows already covered by dsh-memoria's core tools.
README
dsh-memoria-extra
dsh-memoria-extra provides six advanced memoria tools for dsh. It is a companion to @dsh-external/dsh-memoria and connects to the same memoria service and configuration source.
Tools
-
memoria_context: Build a session context block from a memory profile and optional top-k recall results. Supports profile inclusion, static and dynamic limits, and anas_oftimestamp. -
memoria_recent_decisions: Retrieve recent decision records, with a default limit of 10. -
memoria_health: Request a read-only health report covering service, index, quota, and related status through the admin identity. -
memoria_allowed_ns: Return the namespaces authorized for the current caller. -
memoria_graph: Retrieve a weighted sample of the memory relation graph together with summary totals. The sample defaults to 200 nodes and is capped at 5,000; output includes at most 50 nodes and 50 edges. -
memoria_entity_search: Search entities by name, aliases, summary, memory context, and optional entity type.
Configuration
The plugin reads the memoria section from ~/.dsh/settings.yaml when tools are invoked, allowing settings changes to be picked up without recreating the plugin. Supported fields are:
memoria:
baseURL: http://127.0.0.1:9003
agentId: dsh-main
apiKeyEnv: MEMORIA_AGENT_KEY
namespace: agent/xujiayan
These values are the built-in defaults when the corresponding settings are absent.
Normal requests send X-Agent-Id using agentId and obtain X-Agent-Key from the environment variable named by apiKeyEnv. memoria_health instead uses the admin identity and MEMORIA_ADMIN_KEY. If that environment variable is absent, the plugin also looks for a MEMORIA_ADMIN_KEY entry in ~/agent-core/.env.
Most operations use JSON-RPC at <baseURL>/mcp. memoria_graph uses GET <baseURL>/graph.
The dsh bundle registers @jhp830901/dsh-memoria-extra with the ID dsh-memoria-extra.
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:jiayan-xu/dsh-memoria-extra in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.