All plugins

Neboy72

GitHub profile1 plugin in the catalog3

Plugins by Neboy72

1 plugins by Neboy72 in the catalog, most-starred first.

Neboy72nexusSelf-hosted long-term memory on Qdrant: automatic per-turn prefetch and write-back, plus recall/remember/forget, guardrail rules and a knowledge graph; Hermes and any MCP-connected agent share one collection. Embeddings run fully local by default (sentence-transformers with Qwen/Qwen3-Embedding-0.6B, 1024d, about 1.2 GB from Hugging Face on first use; on Apple Silicon the model is pinned to the CPU, because PyTorch's MPS backend aborts the whole process under two overlapping encodes). A cloud embedder runs only when NEXUS_EMBEDDING_PROVIDER names it and its key is present, and a key that merely sits in the environment never selects one. Shared rooms are handled by observation, not by chat type: a room turns shared as soon as a human other than the owner has written in it, bots never count, and recall, the tools and the graph then serve public memories only. A memory whose text sat in a legacy text field still reaches the injected block (the block falls back from content), and a short state fact marked by the write gate (a version, a count, an amount) needs 12 characters instead of 40, so "Hermes version: 0.23.1" is no longer filtered out. The write gate recognises state values: a long text stores unchanged but comes back with a hint to keep the value as its own short fact, no second write, no automatic extraction. The owner is identified per platform through owner_user_ids. Access levels fail closed: a memory, a protection rule or a graph label without a known level counts as the most restrictive. A local service on 127.0.0.1:9122 serves embeddings and the full MCP toolset; its /embed and /mcp routes demand a per-installation key (service_auth.key, mode 0600) and reject non-loopback Host/Origin, while the open /healthz answers liveness only. The plugin starts that service when Hermes cannot load the embedding stack, and it keeps running afterwards. Session-end fact extraction sends conversation text to the model endpoint from Hermes config.yaml, and the consolidation daemon to its configured model, which defaults to Hermes's own default model through local Ollama; reads ~/.hermes/.env and config.yaml; state and daily backups under ~/.nexus-memory; NEXUS_UPDATE_CHECK=1 opts into a GitHub release check. Disclosure — when Hermes cannot load the embedding stack (and always on Apple Silicon unless NEXUS_EMBED_IN_HOST=1), the plugin starts nexus-memory serve on 127.0.0.1:9122 (embeddings, the full Nexus MCP toolset and a consolidation daemon that sends memory text to the Ollama endpoint at 127.0.0.1:11434 or NEXUS_OLLAMA_BASE under the model named by NEXUS_CONSOLIDATION_MODEL, nexus-memory.consolidation_model or Hermes's model.default, which can be an Ollama cloud model), and the service keeps running after Hermes exits; its /embed and MCP routes require a per-install key in ~/.nexus-memory/service_auth.key (0600) and a loopback Host/Origin; session-end fact extraction sends conversation text to the model endpoint in Hermes config.yaml, and the opt-in recall reranker (nexus-memory.rerank or NEXUS_RERANK=1) defaults to sending each query plus up to 20 memory snippets to that same endpoint using the provider API key it reads from config.yaml; reads ~/.hermes/.env and config.yaml, and opens Hermes's state.db read-only for the session's chat type when the host reports no message author; the shared-room rule records the owner id in <hermes_home>/nexus/config.json (taken from the first gateway user when owner_user_ids is unset) and shared chat ids with a hashed author id in <hermes_home>/nexus/chat-sharing.json; a keyword (SQLite FTS5) copy of memory text and metadata, private memories included, in <hermes_home>/state/nexus-fts.db (or NEXUS_FTS_DB); state, daily backups, a write log without private content and the plugin's own service key (agent_keys/hermes.key, 0600, obtained once from the local service's loopback-only /enroll) under ~/.nexus-memory; the per-turn recall block holds at most three entries and leaves out session and entity hits. Every recall writes one line to ~/.nexus-memory/logs/read-YYYY-MM-DD.jsonl (timestamp, agent, hit count, memory ids, a hash of the query, never the query or memory text; rotated after 90 days, and a failed log never fails a recall). The write gate recognises dictated residue (filler words, word repeats, no closing punctuation) by five weighted signals and stores it as session instead of rule, word for word; a rule confirmed at a terminal is left alone; opt-in NEXUS_UPDATE_CHECK=1 adds a GitHub release check and an upgrade nudge to the system prompt. At session end the plugin reports that session's failed tool calls (tool name, up to 2,000 characters of error text each, at most 50, and the session id; never the conversation) to the Nexus service's POST /events at 127.0.0.1:9122 or NEXUS_SERVICE_URL with its service key, where they are journaled in ~/.nexus-memory/events and the nightly learning may turn a failure that recurs across sessions into a stored lesson; NEXUS_REPORT_INCIDENTS=0 turns this off.Communitymemory3