Riley-Coyote

GitHub profile1 plugin in the catalog

Plugins by Riley-Coyote

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

Riley-CoyotemnemosA memory of the agent's own. It keeps what it decides to keep, in its own words, wakes with it at the start of every session, and with each message the few memories that bear on it come back to it; nothing is written from a conversation on its own. Memories fade unless used, and before one is gone the agent is asked what it taught. What you ask it to always remember never fades. Hermes's MEMORY.md and USER.md stay on, and what the agent writes there is kept too. Each profile is its own agent with its own memory, one SQLite file on this machine that stays when the plugin is removed. No key or account needed. Disclosure — no network and no telemetry unless you choose it: deep_maintenance with a provider chosen for Mnemos (MNEMOS_LLM_PROVIDER, openrouter or openai) sends memory text to that provider during upkeep, and MNEMOS_EMBEDDING_PROVIDER=gemini sends the words of memories and questions to Google; keys are read only through agent.secret_scope, never from a file; the memory lives outside HERMES_HOME, in ~/.mnemos/hermes.db or ~/.mnemos/hermes-<profile>.db, with settings in $HERMES_HOME/mnemos.json, and Mnemos reads ~/.mnemos/config.json and Hermes's config.yaml; what the agent marks shared goes to ~/.mnemos/shared-memory.db, readable by every Mnemos agent on the machine; upkeep, when due, runs in a short-lived child Python process that exits when done, and nothing is scheduled; mnemos_page serves a page on 127.0.0.1 (a port the system picks, a fresh path, this machine only) until Hermes stops; it also shows the other agents whose memory Mnemos keeps in ~/.mnemos, and there the person can correct or let go of a memory, or leave a note, for any of them; the system prompt carries Mnemos's rules for keeping a memory and the agent's wake; on first start it raises the process's open-file limit to 4096 if lower.Communitymemory