Store durable project memory.

Use procedural for preferences, conventions, and decisions; semantic for stable facts; episodic for events or task outcomes; and entity for named people, projects, or objects. Use a stable context for project memory.

Search memories by text, context, activation, and confidence.

Use this for a targeted question. Use memory_context to assemble working context. Context is soft by default; use strict_context=true for isolation. With include_neighbors=true, bounded graph neighbors are hydrated into the result. Filter relationships with edge_types such as RESPONDS_TO. The neighbor_limit bounds hydrated neighbors; limit remains the total result count. Metadata reports when additional neighbors were available.

Walk the RESPONDS_TO chain from a starting memory ID and return the thread.

Retrieves connected memories in both directions along RESPONDS_TO edges, returning them sorted chronologically.

Return a working-memory set selected by activation and estimated-token budget.

token_budget is an estimated-token budget. Each returned memory fits wholly within the remaining budget; budgets must be greater than zero.

Record whether a retrieved memory helped this task.

Call this after using a recalled memory when it was useful or misleading.

Inhibit a stale or unhelpful memory without deleting it.

Replace an outdated fact while retaining its history.

Consolidate source memories into one durable higher-level memory.

Connect two memories with an explicit graph relationship.

Use RESPONDS_TO when a new handoff, verification, or fix addresses an earlier memory. Use memory_recall(include_neighbors=true) to retrieve linked memories with relationship metadata.

Store multiple durable project memories in a single batch.

Each item in the list should be a dict with 'content' and optional 'memory_class', 'context', 'confidence', 'provenance', and 'metadata' keys.

Connect multiple pairs of memories with explicit graph relationships in a single batch.

Each item in the list should be a dict with 'source_memory_id', 'target_memory_id', and optional 'relationship' (defaults to 'RESPONDS_TO') keys.

Inspect graph neighbors/schema or perform an advanced edge operation.

Prefer memory_link for normal memory relationships. Supported operations are neighbors, add_edge, schema, and relationship_diagnostics. RESPONDS_TO graph edges are authoritative; diagnostics identifies legacy provenance-only relationships.