crystal_edit

​

What it does

​

Parameters

​

Returns

{
  "success": true,
  "memoryId": "string",
  "message": "Updated memory {memoryId}"
}

• success — Whether the update succeeded
• memoryId — The updated memory’s ID (echo of input)
• message — Confirmation message

​

Examples

​

Basic usage

// Fix a typo in an existing memory
crystal_edit({
  memoryId: "abc123def456",
  content: "Use PostgreSQL for session storage because concurrent writes are needed"
})

// Result:
// {
//   "success": true,
//   "memoryId": "abc123def456",
//   "message": "Updated memory abc123def456"
// }

​

Advanced usage

// Promote a lesson from sensory to semantic store and retag
crystal_edit({
  memoryId: "xyz789",
  store: "semantic",
  category: "lesson",
  tags: ["postgres", "reliability", "database-choice"],
  title: "PostgreSQL concurrency vs SQLite lock contention"
})

// Move a fact to a different category and update content
crystal_edit({
  memoryId: "mem_abc",
  category: "rule",
  content: "Always use prepared statements to prevent SQL injection"
})

​

When to use this vs alternatives

• crystal_edit — When you know the exact memory ID and want to modify it surgically
• crystal_remember — When you want to save a new memory (not update existing)
• crystal_forget — When you want to remove or archive a memory instead of editing it

​

Error handling

​

Notes

• At least one field besides memoryId must be provided (editing nothing is a no-op)
• All string fields are trimmed of leading/trailing whitespace
• Category and store enums are case-sensitive and must match exactly
• Tags are deduplicated automatically on save
• Editing a memory updates its lastAccessedAt timestamp
• The update is transactional — either all fields succeed or the entire operation fails