Search the cross-project memory for solutions similar to the current problem.

Call this FIRST before reasoning about a problem from scratch. If similarity ≥ threshold a cached solution is returned — check edge_cases to see if any known limitations apply to the current context. If no match is found, solve normally and then call confirm_solution.

Save a problem/solution pair to the cross-project memory.

Call this after successfully solving a problem so future sessions — in any project — can find and reuse the solution. Returns the entry ID which can be passed to add_edge_case later.

Auto-save a confirmed solution using context from the last search_similar call.

Call this after solving a problem instead of save_solution — you only need to provide the solution text. Problem description, category, tags, and language are taken automatically from the last search_similar call.

If save_solution was already called manually this session, this is a no-op (no duplicate will be created).

Fix a specific piece of text in an already-saved solution.

Call this when the user corrects a name, term, or detail that was saved incorrectly — for example 'it's not called Paperless-NGX, it's Papertagging'. Replaces all occurrences of find with replace in the solution text.

Use enrich_solution to add new context. Use correct_solution to fix wrong text.

Append new context to an already-saved solution.

Call this when a conversation reveals additional details AFTER a solution was already saved — for example, a follow-up clarification that makes the solution more reusable across projects.

This is NOT for failures (use add_edge_case for those). This is for enrichment: new facts, patterns, or context that improve the answer.

Record a context where a cached solution didn't work as-is.

Call this when search_similar returned a match but it needed modification to work in the current project. The edge case is appended to the entry so future suggestions include the caveat.

List saved entries for a specific project.

Use this at the start of a new conversation when you need to find a project-specific entry to correct or enrich but no entry_id is in context. Returns entry ids, problems, and solutions so you can pick the right one and pass its id to correct_solution or enrich_solution.

Rebuild the vector search index for faster similarity search.

LanceDB falls back to brute-force scan when the table has fewer than 256 rows. Once you have 256+ entries, call this once to build an ANN index — subsequent searches will be significantly faster.

Safe to call at any time; existing data is not modified.

Permanently delete a saved entry.

Use this to remove entries that were saved incorrectly, contain wrong information that can't be fixed with correct_solution, or are no longer relevant. This cannot be undone.

List the most recently saved memory entries.

Use this to audit what has been saved — for example, to find a recently saved entry whose id is not in context. Results are ordered newest-first.

Return database statistics: total entries, breakdown by category, and date range.

Useful for understanding the size and composition of the memory store, and for deciding when to call rebuild_index (threshold: 256+ entries).