From pensyve
Stores a semantic memory fact about an entity via Pensyve MCP. Parses entity:fact syntax or infers entity, then calls pensyve_remember tool.
How this command is triggered — by the user, by Claude, or both
Slash command
/pensyve:remember <entity: fact> or <fact>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /remember Store a fact about an entity as a semantic memory in Pensyve. ## Instructions When the user invokes `/remember <fact>`, follow these steps: 1. **Parse the input.** Look for an entity prefix in the format `entity: fact` or `entity - fact`. If no entity prefix is found, infer the most appropriate entity name from the fact content. Use lowercase, hyphenated names for entities (e.g., `auth-service`, `project-config`, `user-preferences`). 2. **Call the MCP tool.** Use `pensyve_remember` with: - `entity`: The parsed or inferred entity name (lowercase, hyphenated) - `fact`: ...
Store a fact about an entity as a semantic memory in Pensyve.
When the user invokes /remember <fact>, follow these steps:
Parse the input. Look for an entity prefix in the format entity: fact or entity - fact. If no entity prefix is found, infer the most appropriate entity name from the fact content. Use lowercase, hyphenated names for entities (e.g., auth-service, project-config, user-preferences).
Call the MCP tool. Use pensyve_remember with:
entity: The parsed or inferred entity name (lowercase, hyphenated)fact: The fact text to storeconfidence: Default to 1.0 unless the user indicates uncertaintyConfirm storage. Report back to the user what was stored, including:
User: /remember auth-service: uses JWT tokens with RS256 signing
auth-serviceuses JWT tokens with RS256 signingUser: /remember the database migration script requires Python 3.11+
database-migration (inferred)the database migration script requires Python 3.11+User: /remember we decided to use SQLite instead of PostgreSQL for the MVP
project-decisions (inferred)we decided to use SQLite instead of PostgreSQL for the MVP.claude/ memory files. All memory operations go through the Pensyve MCP tools.auth-service, not AuthService or auth service).pensyve_remember returns an error, display the error message and suggest the user check that the Pensyve MCP server is running (pensyve-mcp).npx claudepluginhub khwstolle/memory --plugin pensyve2plugins reuse this command
First indexed Apr 4, 2026
/rememberStores a semantic memory fact about an entity via Pensyve MCP. Parses entity:fact syntax or infers entity, then calls pensyve_remember tool.
/memsy-rememberStores a fact, decision, or note into Memsy memory for retrieval in future sessions. Accepts text via argument, with input validation and optional confirmation.
/rememberStores a fact, preference, decision, convention, or gotcha in Honeycomb's memory, auto-classifying its type and confirming the stored entry.
/rememberSaves a fact, preference, or decision to CortexDB memory with a stable memory ID and concise content. Uses knowledge_save for durable reference knowledge.
/captureCaptures a new memory to the mnemonic filesystem with required namespace and title, optional type (semantic/episodic/procedural), tags, scope (project/org), confidence, citations. Validates against ontology.