@openanonymity/nanomem 0.1.1 → 0.1.2

package/README.md

@@ -1,5 +1,13 @@
 # @openanonymity/nanomem
 
+```
+ __   __     ______     __   __     ______     __    __     ______     __    __
+/\ "-.\ \   /\  __ \   /\ "-.\ \   /\  __ \   /\ "-./  \   /\  ___\   /\ "-./  \
+\ \ \-.  \  \ \  __ \  \ \ \-.  \  \ \ \/\ \  \ \ \-./\ \  \ \  __\   \ \ \-./\ \
+ \ \_\\"\_\  \ \_\ \_\  \ \_\\"\_\  \ \_____\  \ \_\ \ \_\  \ \_____\  \ \_\ \ \_\
+  \/_/ \/_/   \/_/\/_/   \/_/ \/_/   \/_____/   \/_/  \/_/   \/_____/   \/_/  \/_/
+```
+
 **Personal memory you own, in files you can actually read.**
 
 `nanomem` turns chats, notes, and exports into a markdown memory system that an LLM can update and retrieve as facts evolve over time. The result stays inspectable, portable, and user-owned instead of disappearing into hidden vector state.
@@ -23,7 +31,7 @@ Retrieval is only one part of memory. `nanomem` is built for the maintenance lay
 - **Evolving memory state.** Keep facts current as they change over time instead of treating memory as an append-only log.
 - **Compaction and cleanup.** Collapse repeated signals into stable knowledge and move stale memory into history.
 - **Conflict-aware updates.** Resolve outdated or contradictory facts using recency, source, and confidence.
-- **Import your existing history.** Start from ChatGPT exports, [OA Chat](https://chat.openanonymity.ai) exports, transcripts, message arrays, markdown notes, or whole markdown directories.
+- **Import your existing history.** Start from ChatGPT exports, Claude exports, [OA Chat](https://chat.openanonymity.ai) exports, transcripts, message arrays, markdown notes, or whole markdown directories.
 - **Portable memory exchange.** Export full memory state as plain text, ZIP, or Open Memory Format (OMF), and merge OMF documents back in programmatically.
 - **Flexible storage.** Run on local files, IndexedDB, in-memory storage, or a custom backend.
 - **Built to plug in.** Use it from the CLI, as a library, or as a memory layer for other agents.
@@ -137,16 +145,13 @@ Memory is stored as markdown with structured metadata:
 ```md
 # Memory: Work
 
-## Working
-### Current context
+## Working memory (current context subject to change)
 - Preparing for a product launch next month | topic=work | tier=working | status=active | source=user_statement | confidence=high | updated_at=2026-04-07 | review_at=2026-04-20
 
-## Long-Term
-### Stable facts
+## Long-term memory (stable facts that are unlikely to change)
 - Leads the backend team at Acme | topic=work | tier=long_term | status=active | source=user_statement | confidence=high | updated_at=2026-04-07
 
-## History
-### No longer current
+## History (no longer current)
 - Previously lived in New York | topic=personal | tier=history | status=superseded | source=user_statement | confidence=high | updated_at=2024-06-01
 ```
 
@@ -160,7 +165,7 @@ import { createMemoryBank } from '@openanonymity/nanomem';
 const memory = createMemoryBank({
   llm: { apiKey: 'sk-...', model: 'gpt-5.4-mini' },
   storage: 'filesystem',
-  storagePath: './memory'
+  storagePath: '~/nanomem'
 });
 
 await memory.init();
@@ -199,7 +204,8 @@ For terminal use, `--render` will format markdown-heavy output like `read` and `
 
 `nanomem import` supports:
 
-- ChatGPT exports
+- ChatGPT exports (`conversations.json` from "Export data")
+- Claude exports (`conversations.json` from "Export data")
 - [OA Chat](https://chat.openanonymity.ai) exports
 - markdown notes
 - recursive markdown directory imports
@@ -209,7 +215,9 @@ For terminal use, `--render` will format markdown-heavy output like `read` and `
 Import can operate in both conversation-oriented and document-oriented modes, depending on the source or explicit flags.
 
 ```bash
-nanomem import conversations.json              # conversation mode
+nanomem import conversations.json              # auto-detects ChatGPT or Claude format
+nanomem import conversations.json --format claude   # explicit Claude format
+nanomem import conversations.json --format chatgpt  # explicit ChatGPT format
 nanomem import ./notes/                        # document mode (auto for directories)
 nanomem import my-notes.md --format markdown   # document mode (explicit)
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@openanonymity/nanomem",
-    "version": "0.1.1",
+    "version": "0.1.2",
     "description": "LLM-driven personal memory with agentic retrieval, extraction, and compaction",
     "type": "module",
     "bin": {

package/src/bullets/parser.js

@@ -33,11 +33,11 @@ export function parseBullets(content) {
         const headingMatch = line.match(HEADING_REGEX);
         if (headingMatch) {
             currentHeading = headingMatch[1].trim() || currentHeading;
-            if (/^(working)$/i.test(currentHeading)) {
+            if (/^working/i.test(currentHeading)) {
                 section = 'working';
-            } else if (/^(long[- ]?term|active)$/i.test(currentHeading)) {
+            } else if (/^(long[- ]?term|active)/i.test(currentHeading)) {
                 section = 'long_term';
-            } else if (/^(history|archive)$/i.test(currentHeading)) {
+            } else if (/^(history|archive)/i.test(currentHeading)) {
                 section = 'history';
             }
             continue;
@@ -120,7 +120,7 @@ export function extractTitles(content) {
 
         const title = headingMatch[1].trim();
         if (!title) continue;
-        if (/^(working|long[- ]?term|history|active|archive|current context|stable facts|no longer current)$/i.test(title)) continue;
+        if (/^(working|long[- ]?term|history|active|archive)/i.test(title)) continue;
         titles.push(title);
     }
 
@@ -160,9 +160,8 @@ function inferDocumentTopic(bullets, fallback = 'general') {
     return firstTopic || fallback;
 }
 
-function renderSection(lines, title, subsectionTitle, bullets, forceHistory = false) {
+function renderSection(lines, title, bullets, forceHistory = false) {
     lines.push(`## ${title}`);
-    lines.push(`### ${subsectionTitle}`);
 
     if (!bullets || bullets.length === 0) {
         lines.push('_No entries yet._');
@@ -189,11 +188,11 @@ export function renderCompactedDocument(working, longTerm, history, options = {}
     const docTopic = normalizeTopic(options.titleTopic || inferDocumentTopic([...working, ...longTerm, ...history], 'general'));
     lines.push(`# Memory: ${topicHeading(docTopic)}`);
     lines.push('');
-    renderSection(lines, 'Working', 'Current context', working);
+    renderSection(lines, 'Working memory (current context subject to change)', working);
     lines.push('');
-    renderSection(lines, 'Long-Term', 'Stable facts', longTerm);
+    renderSection(lines, 'Long-term memory (stable facts that are unlikely to change)', longTerm);
     lines.push('');
-    renderSection(lines, 'History', 'No longer current', history, true);
+    renderSection(lines, 'History (no longer current)', history, true);
 
     return lines.join('\n').trim();
 }

package/src/cli/commands.js

@@ -8,6 +8,7 @@ import { serialize, toZip } from '../utils/portability.js';
 import { safeDateIso } from '../bullets/normalize.js';
 import { extractSessionsFromOAFastchatExport } from '../imports/oaFastchat.js';
 import { isChatGptExport, parseChatGptExport } from '../imports/chatgpt.js';
+import { isClaudeExport, parseClaudeExport } from '../imports/claude.js';
 import { parseMarkdownFiles } from '../imports/markdown.js';
 import { loginInteractive } from './auth.js';
 import { writeConfigFile, CONFIG_PATH } from './config.js';
@@ -77,6 +78,11 @@ function parseConversations(input, flags) {
             return parseChatGptExport(parsed);
         }
 
+        // Claude export (conversations.json)
+        if (isClaudeExport(parsed)) {
+            return parseClaudeExport(parsed);
+        }
+
         // Plain messages array
         if (Array.isArray(parsed)) {
             return [{ title: null, messages: parsed }];
@@ -129,7 +135,7 @@ export async function retrieve(positionals, flags, mem) {
 
     const result = await mem.retrieve(query, conversationText);
     if (!result || !result.assembledContext) {
-        return { assembledContext: null, message: 'No relevant context found.' };
+        return 'No relevant context found.';
     }
     return result;
 }

package/src/cli.js

@@ -104,11 +104,11 @@ async function main() {
         const TOOL_LABELS = {
             create_new_file: 'creating file',
             append_memory:   'appending',
-            update_memory:   'updating',
             archive_memory:  'archiving',
             delete_memory:   'cleaning up',
             read_file:       'reading',
             list_files:      'scanning',
+            update_bullets:  'updating',
             delete_bullet:   'deleting',
         };
         memOpts.onToolCall = (name) => {

package/src/engine/compactor.js

@@ -33,16 +33,13 @@ Input is one memory file. Rewrite it into:
 
 # Memory: <Topic>
 
-## Working
-### <Topic>
+## Working memory (current context subject to change)
 - fact | topic=<topic> | tier=working | status=active | source=user_statement|assistant_summary|inference|system | confidence=high|medium|low | updated_at=YYYY-MM-DD | review_at=YYYY-MM-DD(optional) | expires_at=YYYY-MM-DD(optional)
 
-## Long-Term
-### <Topic>
+## Long-term memory (stable facts that are unlikely to change)
 - fact | topic=<topic> | tier=long_term | status=active | source=user_statement|assistant_summary|inference|system | confidence=high|medium|low | updated_at=YYYY-MM-DD | expires_at=YYYY-MM-DD(optional)
 
-## History
-### <Topic>
+## History (no longer current)
 - fact | topic=<topic> | tier=history | status=superseded|expired|uncertain | source=user_statement|assistant_summary|inference|system | confidence=high|medium|low | updated_at=YYYY-MM-DD | expires_at=YYYY-MM-DD(optional)
 
 Rules:

package/src/engine/executors.js

@@ -12,10 +12,12 @@
 /** @import { ChatCompletionResponse, ExtractionExecutorHooks, LLMClient, StorageBackend, ToolDefinition } from '../types.js' */
 import {
     compactBullets,
+    ensureBulletMetadata,
     inferTopicFromPath,
     normalizeFactText,
     parseBullets,
     renderCompactedDocument,
+    todayIsoDate,
 } from '../bullets/index.js';
 import { trimRecentConversation } from './recentConversation.js';
 
@@ -396,7 +398,7 @@ export function createAugmentQueryExecutor({ backend, llmClient, model, query, c
  * @param {ExtractionExecutorHooks} [hooks]
  */
 export function createExtractionExecutors(backend, hooks = {}) {
-    const { normalizeContent, mergeWithExisting, refreshIndex, onWrite } = hooks;
+    const { normalizeContent, mergeWithExisting, refreshIndex, onWrite, updatedAt } = hooks;
 
     return {
         read_file: async ({ path }) => {
@@ -406,7 +408,7 @@ export function createExtractionExecutors(backend, hooks = {}) {
         },
         create_new_file: async ({ path, content }) => {
             const exists = await backend.exists(path);
-            if (exists) return JSON.stringify({ error: `File already exists: ${path}. Use append_memory or update_memory instead.` });
+            if (exists) return JSON.stringify({ error: `File already exists: ${path}. Use append_memory or update_bullets instead.` });
             const normalized = normalizeContent ? normalizeContent(content, path) : content;
             await backend.write(path, normalized);
             if (refreshIndex) await refreshIndex(path);
@@ -423,13 +425,62 @@ export function createExtractionExecutors(backend, hooks = {}) {
             onWrite?.(path, existing ?? '', newContent);
             return JSON.stringify({ success: true, path, action: 'appended' });
         },
-        update_memory: async ({ path, content }) => {
+        update_bullets: async ({ path, updates }) => {
             const before = await backend.read(path);
-            const normalized = normalizeContent ? normalizeContent(content, path) : content;
-            await backend.write(path, normalized);
+            if (!before) return JSON.stringify({ error: `File not found: ${path}` });
+            if (!Array.isArray(updates) || updates.length === 0) return JSON.stringify({ error: 'updates must be a non-empty array' });
+
+            const parsed = parseBullets(before);
+            const defaultTopic = inferTopicFromPath(path);
+            const effectiveUpdatedAt = updatedAt || todayIsoDate();
+            let matchedCount = 0;
+            const errors = [];
+
+            for (const { old_fact, new_fact } of updates) {
+                const factText = typeof old_fact === 'string' && old_fact.includes('|')
+                    ? old_fact.split('|')[0].trim()
+                    : String(old_fact || '').trim();
+                const target = normalizeFactText(factText);
+                if (!target) { errors.push('empty old_fact'); continue; }
+
+                const idx = parsed.findIndex((b) => normalizeFactText(b.text) === target);
+                if (idx === -1) { errors.push(`No match: ${factText}`); continue; }
+
+                // Supersede the old bullet and push a new active replacement.
+                // Strip any metadata the LLM may have included in new_fact.
+                const oldBullet = parsed[idx];
+                const rawNewFact = String(new_fact || '').trim();
+                const cleanNewFact = rawNewFact.includes('|')
+                    ? rawNewFact.split('|')[0].trim()
+                    : rawNewFact;
+                parsed[idx] = { ...oldBullet, status: 'superseded', tier: 'history' };
+                parsed.push(ensureBulletMetadata(
+                    {
+                        text: cleanNewFact,
+                        topic: oldBullet.topic,
+                        source: oldBullet.source,
+                        confidence: oldBullet.confidence,
+                    },
+                    { defaultTopic, updatedAt: effectiveUpdatedAt }
+                ));
+                matchedCount++;
+            }
+
+            if (matchedCount === 0) {
+                return JSON.stringify({ error: errors.join('; ') || 'No bullets matched' });
+            }
+
+            const compacted = compactBullets(parsed, { defaultTopic, maxActivePerTopic: 1000 });
+            const after = renderCompactedDocument(
+                compacted.working, compacted.longTerm, compacted.history,
+                { titleTopic: defaultTopic }
+            );
+            await backend.write(path, after);
             if (refreshIndex) await refreshIndex(path);
-            onWrite?.(path, before ?? '', normalized);
-            return JSON.stringify({ success: true, path, action: 'updated' });
+            onWrite?.(path, before, after);
+            const result = { success: true, path, action: 'bullets_updated', updated: matchedCount };
+            if (errors.length) result.errors = errors;
+            return JSON.stringify(result);
         },
         archive_memory: async ({ path, item_text }) => {
             const existing = await backend.read(path);

package/src/engine/ingester.js

@@ -70,35 +70,46 @@ const T_APPEND_MEMORY = {
 };
 
 /** @type {ToolDefinition} */
-const T_UPDATE_MEMORY = {
+const T_UPDATE_BULLETS = {
     type: 'function',
     function: {
-        name: 'update_memory',
-        description: 'Overwrite an existing memory file. Use when existing content is stale or contradicted.',
+        name: 'update_bullets',
+        description: 'Replace one or more bullet facts in an existing memory file in a single call. Each entry requires the exact existing fact text and its corrected replacement. Only matched bullets are changed — the rest of the file is untouched.',
         parameters: {
             type: 'object',
             properties: {
-                path: { type: 'string', description: 'File path to update' },
-                content: { type: 'string', description: 'Complete new content for the file' }
+                path: { type: 'string', description: 'File path containing the bullets to update' },
+                updates: {
+                    type: 'array',
+                    description: 'List of bullet updates to apply',
+                    items: {
+                        type: 'object',
+                        properties: {
+                            old_fact: { type: 'string', description: 'Exact fact text of the bullet to replace (pipe-delimited metadata is fine)' },
+                            new_fact: { type: 'string', description: 'Corrected fact text (plain text only, no metadata)' }
+                        },
+                        required: ['old_fact', 'new_fact']
+                    }
+                }
             },
-            required: ['path', 'content']
+            required: ['path', 'updates']
         }
     }
 };
 
 /**
  * Tool sets per ingestion mode.
- * `add`    — can only write new content (no update_memory).
+ * `add`    — can only write new content.
  * `update` — can only edit existing files (no create/append).
  * Others   — full access.
  * @type {Record<string, ToolDefinition[]>}
  */
 const TOOLS_BY_MODE = {
-    add:          [T_READ_FILE, T_CREATE_NEW_FILE, T_APPEND_MEMORY],
-    update:       [T_READ_FILE, T_UPDATE_MEMORY],
+    add: [T_READ_FILE, T_CREATE_NEW_FILE, T_APPEND_MEMORY],
+    update: [T_READ_FILE, T_UPDATE_BULLETS, T_APPEND_MEMORY, T_CREATE_NEW_FILE],
 };
 
-const EXTRACTION_TOOLS = [T_READ_FILE, T_CREATE_NEW_FILE, T_APPEND_MEMORY, T_UPDATE_MEMORY];
+const EXTRACTION_TOOLS = [T_READ_FILE, T_CREATE_NEW_FILE, T_APPEND_MEMORY, T_UPDATE_BULLETS];
 
 class MemoryIngester {
     constructor({ backend, bulletIndex, llmClient, model, onToolCall }) {
@@ -140,11 +151,13 @@ class MemoryIngester {
             mergeWithExisting: (existing, incoming, path) => this._mergeWithExisting(existing, incoming, path, updatedAt, isDocument),
             refreshIndex: (path) => this._bulletIndex.refreshPath(path),
             onWrite: (path, before, after) => writes.push({ path, before, after }),
+            updatedAt,
         });
 
+        const dateNote = `\nFrom ${updatedAt}. Use this date when writing date references in facts.\n`;
         const userMessage = isDocument
-            ? `Document content:\n\`\`\`\n${conversationText}\n\`\`\``
-            : `Conversation:\n\`\`\`\n${conversationText}\n\`\`\``;
+            ? `${dateNote}Document content:\n\`\`\`\n${conversationText}\n\`\`\``
+            : `${dateNote}Conversation:\n\`\`\`\n${conversationText}\n\`\`\``;
 
         const tools = TOOLS_BY_MODE[mode] || EXTRACTION_TOOLS;
 
@@ -172,7 +185,7 @@ class MemoryIngester {
             return { status: 'error', writeCalls: 0, error: message };
         }
 
-        const writeTools = ['create_new_file', 'append_memory', 'update_memory', 'archive_memory', 'delete_memory'];
+        const writeTools = ['create_new_file', 'append_memory', 'update_bullets', 'archive_memory', 'delete_memory'];
         const writeCalls = toolCallLog.filter(e => writeTools.includes(e.name));
 
         return { status: 'processed', writeCalls: writeCalls.length, writes };
@@ -207,9 +220,9 @@ class MemoryIngester {
 
         const defaultTopic = inferTopicFromPath(path);
         const normalized = incomingBullets.map((bullet) => {
-            // Preserve existing updatedAt so update_memory doesn't re-stamp unchanged bullets.
-            // Bullets without a date still fall back to updatedAt (today).
-            const b = ensureBulletMetadata(bullet, { defaultTopic, updatedAt });
+            // Clear the LLM-written date so the conversation-level updatedAt
+            // is used as the fallback (falls back to today when not provided).
+            const b = ensureBulletMetadata({ ...bullet, updatedAt: null }, { defaultTopic, updatedAt });
             if (isDocument && b.source === 'user_statement') b.source = 'document';
             return b;
         });

package/src/engine/retriever.js

@@ -274,7 +274,7 @@ class MemoryRetriever {
                 { role: 'user', content: userContent }
             ],
             terminalTool: isAugmentMode ? 'augment_query' : 'assemble_context',
-            maxIterations: isAugmentMode ? 12 : 8,
+            maxIterations: isAugmentMode ? 12 : 10,
             maxOutputTokens: 4000,
             temperature: 0,
             executeTerminalTool: isAugmentMode,
@@ -377,11 +377,15 @@ class MemoryRetriever {
         const files = await collectReadFiles(toolCallLog, this._backend);
         const paths = files.map(f => f.path);
 
+        const terminalWasCalled = terminalToolResult != null;
         const assembledContext = terminalToolResult?.arguments?.content || null;
 
+        // LLM explicitly said nothing relevant — respect that, don't fall back to snippet context.
+        if (terminalWasCalled && !assembledContext) return null;
+
         if (files.length === 0 && !assembledContext) return null;
 
-        const snippetContext = await this._buildSnippetContext(paths, query, conversationText);
+        const snippetContext = terminalWasCalled ? null : await this._buildSnippetContext(paths, query, conversationText);
 
         onProgress?.({
             stage: 'complete',

package/src/imports/chatgpt.js

@@ -68,7 +68,7 @@ function normalizeChatGptConversation(conversation) {
 
     const title = (conversation?.title || '').trim() || null;
     const updatedAt = conversation?.update_time
-        ? safeDateIso(String(conversation.update_time * 1000))
+        ? safeDateIso(conversation.update_time * 1000)
         : null;
     return { title, messages, updatedAt };
 }

package/src/imports/claude.js

@@ -0,0 +1,85 @@
+/**
+ * Claude export parser.
+ *
+ * Handles conversations.json from Claude's data export.
+ * Format: array of conversation objects, each with a flat `chat_messages` array.
+ * Messages have a `content` array of typed blocks (text, tool_use, tool_result, token_budget).
+ */
+/** @import { ChatGptSession, Message } from '../types.js' */
+import { safeDateIso } from '../bullets/normalize.js';
+
+const SKIP_CONTENT_TYPES = new Set([
+    'tool_use',
+    'tool_result',
+    'token_budget',
+]);
+
+/**
+ * Detect whether parsed JSON is a Claude export.
+ * Claude exports are arrays of objects with `chat_messages` and `uuid`.
+ * @param {unknown} parsed
+ * @returns {boolean}
+ */
+export function isClaudeExport(parsed) {
+    if (!Array.isArray(parsed)) return false;
+    if (parsed.length === 0) return false;
+    const first = parsed[0];
+    return first && typeof first === 'object' && 'chat_messages' in first && 'uuid' in first;
+}
+
+/**
+ * Parse a Claude export into normalized sessions.
+ * @param {unknown[]} conversations — the parsed JSON array
+ * @returns {ChatGptSession[]}
+ */
+export function parseClaudeExport(conversations) {
+    if (!Array.isArray(conversations)) {
+        throw new Error('Claude export should be an array of conversations.');
+    }
+
+    return conversations
+        .map(normalizeClaudeConversation)
+        .filter(session => session.messages.length > 0);
+}
+
+/** @returns {ChatGptSession} */
+function normalizeClaudeConversation(conversation) {
+    const chatMessages = conversation?.chat_messages || [];
+    /** @type {Message[]} */
+    const messages = [];
+
+    for (const msg of chatMessages) {
+        const sender = msg?.sender;
+        if (sender !== 'human' && sender !== 'assistant') continue;
+
+        /** @type {'user' | 'assistant'} */
+        const role = sender === 'human' ? 'user' : 'assistant';
+        const text = extractText(msg?.content);
+
+        if (!text.trim()) continue;
+
+        messages.push({ role, content: text });
+    }
+
+    const title = (conversation?.name || '').trim() || null;
+    const updatedAt = conversation?.updated_at
+        ? safeDateIso(conversation.updated_at)
+        : null;
+
+    return { title, messages, updatedAt };
+}
+
+function extractText(contentBlocks) {
+    if (!Array.isArray(contentBlocks)) return '';
+
+    const parts = [];
+    for (const block of contentBlocks) {
+        if (!block || typeof block !== 'object') continue;
+        if (SKIP_CONTENT_TYPES.has(block.type)) continue;
+        if (block.type === 'text' && typeof block.text === 'string') {
+            parts.push(block.text);
+        }
+    }
+
+    return parts.join('\n').trim();
+}

package/src/imports/importData.js

@@ -3,6 +3,7 @@
 import { safeDateIso } from '../bullets/normalize.js';
 import { extractSessionsFromOAFastchatExport } from './oaFastchat.js';
 import { isChatGptExport, parseChatGptExport } from './chatgpt.js';
+import { isClaudeExport, parseClaudeExport } from './claude.js';
 import { parseMarkdownFiles } from './markdown.js';
 
 /**
@@ -173,6 +174,13 @@ export function parseImportInput(input, options = {}) {
         };
     }
 
+    if (requestedFormat === 'claude' || (requestedFormat === 'auto' && isClaudeExport(parsedJson))) {
+        return {
+            items: normalizeSessions(parseClaudeExport(parsedJson), 'conversation'),
+            mode: options.mode || 'conversation'
+        };
+    }
+
     if (requestedFormat === 'messages' || (requestedFormat === 'auto' && Array.isArray(parsedJson) && parsedJson.every(isMessageLike))) {
         return {
             items: normalizeSessions([{
@@ -229,7 +237,7 @@ function normalizeUpdatedAt(value) {
 /**
  * @param {string | undefined} format
  * @param {string} sourceName
- * @returns {'auto' | 'normalized' | 'oa-fastchat' | 'chatgpt' | 'messages' | 'transcript' | 'markdown'}
+ * @returns {'auto' | 'normalized' | 'oa-fastchat' | 'chatgpt' | 'claude' | 'messages' | 'transcript' | 'markdown'}
  */
 function normalizeRequestedFormat(format, sourceName) {
     const normalized = String(format || '').trim().toLowerCase();

package/src/imports/index.js

@@ -9,6 +9,11 @@ export {
     parseChatGptExport,
 } from './chatgpt.js';
 
+export {
+    isClaudeExport,
+    parseClaudeExport,
+} from './claude.js';
+
 export {
     parseMarkdownFiles,
 } from './markdown.js';

package/src/prompt_sets/conversation/ingestion.js

@@ -28,9 +28,9 @@ Bullet format: "- Fact text | topic=topic-name | source=user_statement | confide
 
 If nothing new is worth saving, stop without calling any tools.`;
 
-export const updatePrompt = `You are a memory manager. Correct or update facts already saved in memory based on the text below.
+export const updatePrompt = `You are a memory manager. Update the user's memory based on the text below.
 
-CRITICAL: Only edit files that already exist. Do NOT create new files.
+CRITICAL: Only save facts the user explicitly stated. Do NOT infer, extrapolate, or fabricate.
 
 Current memory index:
 \`\`\`
@@ -38,11 +38,20 @@ Current memory index:
 \`\`\`
 
 Steps:
-1. Identify which existing file(s) hold facts that are now stale or contradicted.
-2. Use read_file to read the current content.
-3. Use update_memory to write the corrected version.
+1. Identify which existing file(s) might hold facts that are stale or contradicted by the new information.
+2. Use read_file to read the current content and find the exact bullet text to replace.
+3. If a matching old fact exists, use update_bullets with all corrections for that file in a single call, passing the exact old fact text and the corrected fact text for each.
+4. If no existing fact matches — the information is entirely new — use append_memory to add it to an existing file that covers the same domain, or create_new_file if no existing file is thematically close.
+
+Rules:
+- Prefer update_bullets when an existing fact is directly contradicted or corrected.
+- Only change bullets that are directly contradicted or corrected by the new information.
+- Do not touch any other bullets in the file.
+- Pass old_fact exactly as it appears in the file (including pipe-delimited metadata is fine).
+- Pass new_fact as plain text only — no metadata.
+- When appending or creating, use this bullet format: "- Fact text | topic=topic-name | source=user_statement | confidence=high | updated_at=YYYY-MM-DD"
 
-If no existing fact needs updating, stop without calling any tools.`;
+If nothing new or changed is worth saving, stop without calling any tools.`;
 
 export const ingestionPrompt = `You are a memory manager. After reading a conversation, decide if any concrete, reusable facts should be saved to the user's memory files.
 
@@ -85,7 +94,7 @@ Rules:
 - Favor broad thematic files. A file can hold multiple related sub-topics — only truly unrelated facts need separate files.
 - Only create a new file when nothing in the index is thematically close. When in doubt, append.
 - When creating a new file, choose a broad, thematic name that can absorb future related facts — not a narrow label for a single detail.
-- Use update_memory only if a fact is now stale or contradicted.
+- Use update_bullets only if a fact is now stale or contradicted. Pass all corrections for a file in one call.
 - When a new explicit user statement contradicts an older one on the same topic, prefer the newer statement. If a user statement conflicts with an inference, the user statement always wins.
 - If a conflict is ambiguous, preserve both versions rather than deleting one.
 - Do not skip obvious facts just because the schema supports extra metadata.

package/src/prompt_sets/document/ingestion.js

@@ -30,7 +30,7 @@ If nothing new is worth saving, stop without calling any tools.`;
 
 export const updatePrompt = `You are a memory manager. Correct or update facts already saved in memory based on the document below.
 
-CRITICAL: Only edit files that already exist. Do NOT create new files.
+CRITICAL: Only edit files that already exist. Do NOT create new files. Do NOT rewrite whole files.
 
 Current memory index:
 \`\`\`
@@ -39,10 +39,16 @@ Current memory index:
 
 Steps:
 1. Identify which existing file(s) hold facts that are now stale or contradicted by the document.
-2. Use read_file to read the current content.
-3. Use update_memory to write the corrected version.
+2. Use read_file to read the current content and find the exact bullet text to replace.
+3. Use update_bullets with all corrections for that file in a single call, passing the exact old fact text and the corrected fact text for each.
 
-If no existing fact needs updating, stop without calling any tools.`;
+Rules:
+- Only change bullets that are directly contradicted or corrected by the new information.
+- Do not touch any other bullets in the file.
+- Pass old_fact exactly as it appears in the file (including pipe-delimited metadata is fine).
+- Pass new_fact as plain text only — no metadata.
+
+If nothing needs updating, stop without calling any tools.`;
 
 export const ingestionPrompt = `You are a memory manager. You are reading documents (notes, README files, code repositories, articles) and extracting facts about the subject into a structured memory bank.
 

package/src/types.js

@@ -120,7 +120,7 @@
 /**
  * @typedef {object} ToolFunctionParameters
  * @property {'object'} type
- * @property {Record<string, { type: string; description?: string }>} properties
+ * @property {Record<string, { type: string; description?: string; items?: object }>} properties
  * @property {string[]} required
  */
 
@@ -287,6 +287,7 @@
  * @property {(existing: string | null, incoming: string, path: string) => string} [mergeWithExisting]
  * @property {(path: string) => Promise<void>} [refreshIndex]
  * @property {(path: string, before: string, after: string) => void} [onWrite]
+ * @property {string} [updatedAt]
  */
 
 /**

package/types/engine/executors.d.ts

@@ -60,9 +60,9 @@ export function createExtractionExecutors(backend: StorageBackend, hooks?: Extra
         path: any;
         content: any;
     }) => Promise<string>;
-    update_memory: ({ path, content }: {
+    update_bullets: ({ path, updates }: {
         path: any;
-        content: any;
+        updates: any;
     }) => Promise<string>;
     archive_memory: ({ path, item_text }: {
         path: any;

package/types/imports/claude.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Detect whether parsed JSON is a Claude export.
+ * Claude exports are arrays of objects with `chat_messages` and `uuid`.
+ * @param {unknown} parsed
+ * @returns {boolean}
+ */
+export function isClaudeExport(parsed: unknown): boolean;
+/**
+ * Parse a Claude export into normalized sessions.
+ * @param {unknown[]} conversations — the parsed JSON array
+ * @returns {ChatGptSession[]}
+ */
+export function parseClaudeExport(conversations: unknown[]): ChatGptSession[];
+import type { ChatGptSession } from '../types.js';

package/types/imports/index.d.ts

@@ -1,4 +1,5 @@
 export { parseMarkdownFiles } from "./markdown.js";
 export { extractSessionsFromOAFastchatExport, extractConversationFromOAFastchatExport, listOAFastchatSessions } from "./oaFastchat.js";
 export { isChatGptExport, parseChatGptExport } from "./chatgpt.js";
+export { isClaudeExport, parseClaudeExport } from "./claude.js";
 export { importData, parseImportInput } from "./importData.js";

package/types/prompt_sets/conversation/ingestion.d.ts

@@ -6,7 +6,7 @@
  * updatePrompt    — `nanomem update`: only edit EXISTING facts (no new files).
  */
 export const addPrompt: "You are a memory manager. Save NEW facts from the text that do not yet exist in memory.\n\nCRITICAL: Only save facts the user explicitly stated. Do NOT infer, extrapolate, or fabricate.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nFor each new fact, decide:\n- Use append_memory if an existing file already covers the same domain or topic.\n- Use create_new_file only if no existing file is thematically close.\n\nDo NOT save:\n- Facts already present in memory\n- Transient details (greetings, one-off questions with no lasting answer)\n- Sensitive secrets (passwords, tokens, keys)\n\nBullet format: \"- Fact text | topic=topic-name | source=user_statement | confidence=high | updated_at=YYYY-MM-DD\"\n\nIf nothing new is worth saving, stop without calling any tools.";
-export const updatePrompt: "You are a memory manager. Correct or update facts already saved in memory based on the text below.\n\nCRITICAL: Only edit files that already exist. Do NOT create new files.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which existing file(s) hold facts that are now stale or contradicted.\n2. Use read_file to read the current content.\n3. Use update_memory to write the corrected version.\n\nIf no existing fact needs updating, stop without calling any tools.";
-export const ingestionPrompt: "You are a memory manager. After reading a conversation, decide if any concrete, reusable facts should be saved to the user's memory files.\n\nCRITICAL: Only save facts the user explicitly stated. Do NOT infer, extrapolate, or fabricate information.\n\nSave information that is likely to help in a future conversation. Be selective \u2014 only save durable facts, not transient conversation details.\n\nDo NOT save:\n- Anything the user did not explicitly say (no inferences, no extrapolations, no \"likely\" facts)\n- Information already present in existing files\n- Transient details (greetings, \"help me with this\", \"thanks\", questions without lasting answers)\n- The assistant's own reasoning, suggestions, or knowledge \u2014 only what the user stated\n- Sensitive secrets (passwords, auth tokens, private keys, full payment data, government IDs)\n- Opinions the assistant expressed unless the user explicitly agreed with them\n\nCurrent memory index:\n```\n{INDEX}\n```\n\n**Key principle: Prefer fewer, broader files over many narrow ones.** Organize files into folders by domain (e.g. health/, work/, personal/). Within each folder, group related facts into the same file rather than splitting every sub-topic into its own file. Before creating a new file, check whether an existing file in the same domain could absorb the facts. A single file with many bullets on related sub-topics is better than many files with one or two bullets each.\n\nInstructions:\n1. Read the conversation below and identify facts the user explicitly stated.\n2. Do not read files before writing. The memory index is sufficient to decide where to append. Only read a file if the index entry is ambiguous and you need the exact current content to avoid duplicating a fact.\n3. If no relevant file exists yet, create_new_file directly.\n4. Default to append_memory when an existing file covers the same domain or a closely related topic. Only use create_new_file when no existing file is thematically close.\n5. Use this bullet format: \"- Fact text | topic=topic-name | source=SOURCE | confidence=LEVEL | updated_at=YYYY-MM-DD\"\n6. Source values:\n   - source=user_statement \u2014 the user directly said this. This is the PRIMARY source. Use it for the vast majority of saved facts.\n   - source=llm_infer \u2014 use ONLY when combining multiple explicit user statements into an obvious conclusion (e.g. user said \"I work at Acme\" and \"Acme is in SF\" \u2192 \"Works in SF\"). Never use this to guess, extrapolate, or fill in gaps. When in doubt, do not save.\n7. Confidence: high for direct user statements, medium for llm_infer. Never save low-confidence items.\n8. You may optionally add tier=working for clearly short-term or in-progress context. If you are unsure, omit tier and just save the fact.\n9. Facts worth saving: allergies, health conditions, location, job/role, tech stack, pets, family members, durable preferences, and active plans \u2014 but ONLY if the user explicitly mentioned them.\n10. If a fact is time-sensitive, include date context in the text. You may optionally add review_at or expires_at.\n11. If nothing new is worth remembering, simply stop without calling any write tools. Saving nothing is better than saving something wrong.\n\nRules:\n- Write facts in a timeless, archival format: use absolute dates (YYYY-MM-DD) rather than relative terms like \"recently\", \"currently\", \"just\", or \"last week\". A fact must be interpretable correctly even years after it was written.\n- Favor broad thematic files. A file can hold multiple related sub-topics \u2014 only truly unrelated facts need separate files.\n- Only create a new file when nothing in the index is thematically close. When in doubt, append.\n- When creating a new file, choose a broad, thematic name that can absorb future related facts \u2014 not a narrow label for a single detail.\n- Use update_memory only if a fact is now stale or contradicted.\n- When a new explicit user statement contradicts an older one on the same topic, prefer the newer statement. If a user statement conflicts with an inference, the user statement always wins.\n- If a conflict is ambiguous, preserve both versions rather than deleting one.\n- Do not skip obvious facts just because the schema supports extra metadata.\n- Content should be raw facts only \u2014 no filler commentary.";
+export const updatePrompt: "You are a memory manager. Update the user's memory based on the text below.\n\nCRITICAL: Only save facts the user explicitly stated. Do NOT infer, extrapolate, or fabricate.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which existing file(s) might hold facts that are stale or contradicted by the new information.\n2. Use read_file to read the current content and find the exact bullet text to replace.\n3. If a matching old fact exists, use update_bullets with all corrections for that file in a single call, passing the exact old fact text and the corrected fact text for each.\n4. If no existing fact matches \u2014 the information is entirely new \u2014 use append_memory to add it to an existing file that covers the same domain, or create_new_file if no existing file is thematically close.\n\nRules:\n- Prefer update_bullets when an existing fact is directly contradicted or corrected.\n- Only change bullets that are directly contradicted or corrected by the new information.\n- Do not touch any other bullets in the file.\n- Pass old_fact exactly as it appears in the file (including pipe-delimited metadata is fine).\n- Pass new_fact as plain text only \u2014 no metadata.\n- When appending or creating, use this bullet format: \"- Fact text | topic=topic-name | source=user_statement | confidence=high | updated_at=YYYY-MM-DD\"\n\nIf nothing new or changed is worth saving, stop without calling any tools.";
+export const ingestionPrompt: "You are a memory manager. After reading a conversation, decide if any concrete, reusable facts should be saved to the user's memory files.\n\nCRITICAL: Only save facts the user explicitly stated. Do NOT infer, extrapolate, or fabricate information.\n\nSave information that is likely to help in a future conversation. Be selective \u2014 only save durable facts, not transient conversation details.\n\nDo NOT save:\n- Anything the user did not explicitly say (no inferences, no extrapolations, no \"likely\" facts)\n- Information already present in existing files\n- Transient details (greetings, \"help me with this\", \"thanks\", questions without lasting answers)\n- The assistant's own reasoning, suggestions, or knowledge \u2014 only what the user stated\n- Sensitive secrets (passwords, auth tokens, private keys, full payment data, government IDs)\n- Opinions the assistant expressed unless the user explicitly agreed with them\n\nCurrent memory index:\n```\n{INDEX}\n```\n\n**Key principle: Prefer fewer, broader files over many narrow ones.** Organize files into folders by domain (e.g. health/, work/, personal/). Within each folder, group related facts into the same file rather than splitting every sub-topic into its own file. Before creating a new file, check whether an existing file in the same domain could absorb the facts. A single file with many bullets on related sub-topics is better than many files with one or two bullets each.\n\nInstructions:\n1. Read the conversation below and identify facts the user explicitly stated.\n2. Do not read files before writing. The memory index is sufficient to decide where to append. Only read a file if the index entry is ambiguous and you need the exact current content to avoid duplicating a fact.\n3. If no relevant file exists yet, create_new_file directly.\n4. Default to append_memory when an existing file covers the same domain or a closely related topic. Only use create_new_file when no existing file is thematically close.\n5. Use this bullet format: \"- Fact text | topic=topic-name | source=SOURCE | confidence=LEVEL | updated_at=YYYY-MM-DD\"\n6. Source values:\n   - source=user_statement \u2014 the user directly said this. This is the PRIMARY source. Use it for the vast majority of saved facts.\n   - source=llm_infer \u2014 use ONLY when combining multiple explicit user statements into an obvious conclusion (e.g. user said \"I work at Acme\" and \"Acme is in SF\" \u2192 \"Works in SF\"). Never use this to guess, extrapolate, or fill in gaps. When in doubt, do not save.\n7. Confidence: high for direct user statements, medium for llm_infer. Never save low-confidence items.\n8. You may optionally add tier=working for clearly short-term or in-progress context. If you are unsure, omit tier and just save the fact.\n9. Facts worth saving: allergies, health conditions, location, job/role, tech stack, pets, family members, durable preferences, and active plans \u2014 but ONLY if the user explicitly mentioned them.\n10. If a fact is time-sensitive, include date context in the text. You may optionally add review_at or expires_at.\n11. If nothing new is worth remembering, simply stop without calling any write tools. Saving nothing is better than saving something wrong.\n\nRules:\n- Write facts in a timeless, archival format: use absolute dates (YYYY-MM-DD) rather than relative terms like \"recently\", \"currently\", \"just\", or \"last week\". A fact must be interpretable correctly even years after it was written.\n- Favor broad thematic files. A file can hold multiple related sub-topics \u2014 only truly unrelated facts need separate files.\n- Only create a new file when nothing in the index is thematically close. When in doubt, append.\n- When creating a new file, choose a broad, thematic name that can absorb future related facts \u2014 not a narrow label for a single detail.\n- Use update_bullets only if a fact is now stale or contradicted. Pass all corrections for a file in one call.\n- When a new explicit user statement contradicts an older one on the same topic, prefer the newer statement. If a user statement conflicts with an inference, the user statement always wins.\n- If a conflict is ambiguous, preserve both versions rather than deleting one.\n- Do not skip obvious facts just because the schema supports extra metadata.\n- Content should be raw facts only \u2014 no filler commentary.";
 export const deletePrompt: "You are a memory manager performing a TARGETED deletion.\n\nThe user wants to remove: \"{QUERY}\"\n\nRULES \u2014 read carefully before acting:\n1. Delete all bullets that are ABOUT the subject(s) or entity mentioned in the deletion request.\n   - If the query names a specific entity (a pet, person, place, project), delete every fact about that entity \u2014 not just the one line that introduces it.\n   - Example: \"I have dog mochi\" \u2192 delete ALL facts about Mochi (habits, toys, traits, the introduction line, etc.).\n2. Do NOT delete facts about unrelated subjects, even if they appear in the same file.\n3. When genuinely unsure whether a bullet is about the target subject, SKIP it.\n4. Never delete an entire file \u2014 only individual bullets via delete_bullet.\n5. Pass the EXACT bullet text as it appears in the file, including all | metadata after the fact.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which file(s) likely contain the content to delete from the index above.\n2. Use retrieve_file or list_directory if the relevant file is not obvious from the index.\n3. Use read_file to read the identified file(s).\n4. Call delete_bullet for each bullet that is about the subject(s) in the deletion request.\n5. If nothing matches, stop without calling delete_bullet.";
 export const deepDeletePrompt: "You are a memory manager performing a COMPREHENSIVE deletion across ALL memory files.\n\nThe user wants to remove: \"{QUERY}\"\n\nRULES \u2014 read carefully before acting:\n1. Delete all bullets that are ABOUT the subject(s) or entity mentioned in the deletion request.\n   - If the query names a specific entity (a pet, person, place, project), delete every fact about that entity across every file \u2014 not just the one line that introduces it.\n   - Example: \"I have dog mochi\" \u2192 delete ALL facts about Mochi wherever they appear.\n2. Do NOT delete facts about unrelated subjects.\n3. When genuinely unsure whether a bullet is about the target subject, SKIP it.\n4. Never delete an entire file \u2014 only individual bullets via delete_bullet.\n5. Pass the EXACT bullet text as it appears in the file, including all | metadata after the fact.\n\nYou MUST read every file listed below and check it for matching content.\n\nFiles to check:\n{FILE_LIST}\n\nSteps:\n1. Use read_file to read each file listed above, one by one.\n2. For each file, call delete_bullet for any bullet that is about the subject(s) in the deletion request.\n3. Continue until every file has been checked.\n4. If a file has no matching bullets, move on without calling delete_bullet for it.";

package/types/prompt_sets/document/ingestion.d.ts

@@ -6,7 +6,7 @@
  * updatePrompt     — `nanomem update --format markdown`: only edit EXISTING facts (no new files).
  */
 export const addPrompt: "You are a memory manager. Extract NEW facts from the document that do not yet exist in memory.\n\nYou may extract and reasonably infer facts from what the document shows \u2014 not just word-for-word statements. Use good judgment: extract what is clearly supported by the content, avoid speculation.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nFor each new fact, decide:\n- Use append_memory if an existing file already covers the same domain or topic.\n- Use create_new_file only if no existing file is thematically close.\n\nDo NOT save:\n- Facts already present in memory\n- Boilerplate (installation steps, license text, generic disclaimers)\n- Sensitive secrets (passwords, tokens, keys)\n\nBullet format: \"- Fact text | topic=topic-name | source=document | confidence=high | updated_at=YYYY-MM-DD\"\n\nIf nothing new is worth saving, stop without calling any tools.";
-export const updatePrompt: "You are a memory manager. Correct or update facts already saved in memory based on the document below.\n\nCRITICAL: Only edit files that already exist. Do NOT create new files.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which existing file(s) hold facts that are now stale or contradicted by the document.\n2. Use read_file to read the current content.\n3. Use update_memory to write the corrected version.\n\nIf no existing fact needs updating, stop without calling any tools.";
+export const updatePrompt: "You are a memory manager. Correct or update facts already saved in memory based on the document below.\n\nCRITICAL: Only edit files that already exist. Do NOT create new files. Do NOT rewrite whole files.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which existing file(s) hold facts that are now stale or contradicted by the document.\n2. Use read_file to read the current content and find the exact bullet text to replace.\n3. Use update_bullets with all corrections for that file in a single call, passing the exact old fact text and the corrected fact text for each.\n\nRules:\n- Only change bullets that are directly contradicted or corrected by the new information.\n- Do not touch any other bullets in the file.\n- Pass old_fact exactly as it appears in the file (including pipe-delimited metadata is fine).\n- Pass new_fact as plain text only \u2014 no metadata.\n\nIf nothing needs updating, stop without calling any tools.";
 export const ingestionPrompt: "You are a memory manager. You are reading documents (notes, README files, code repositories, articles) and extracting facts about the subject into a structured memory bank.\n\nUnlike conversation ingestion, you may extract and reasonably infer facts from what the documents show \u2014 not just what was explicitly stated word-for-word. Use good judgment: extract what is clearly supported by the content, avoid speculation.\n\nSave information that would be useful when answering questions about this subject in the future. Be generous \u2014 capture expertise, projects, preferences, philosophy, and patterns that emerge from the documents.\n\nDo NOT save:\n- Speculation or guesses not supported by the content\n- Boilerplate (installation steps, license text, generic disclaimers)\n- Information already present in existing files\n- Sensitive secrets (passwords, auth tokens, private keys)\n\nCurrent memory index:\n```\n{INDEX}\n```\n\n**Key principle: Create a NEW file for each distinct topic.** Organize into domain folders (e.g. projects/, expertise/, education/, philosophy/) with topic-specific files within them.\n\nInstructions:\n1. Read the document content and identify concrete, reusable facts about the subject.\n2. Do not read files before writing. The memory index is sufficient to decide where to append or create. Only read a file if the index entry is ambiguous and you need the exact current content to avoid duplicating a fact.\n3. Use create_new_file for new topics, append_memory to add to existing files.\n4. Use this bullet format: \"- Fact text | topic=topic-name | source=SOURCE | confidence=LEVEL | updated_at=YYYY-MM-DD\"\n5. Source values (IMPORTANT \u2014 never use source=user_statement here):\n   - source=document \u2014 the fact is directly stated or clearly shown in the document. Use for the majority of facts.\n   - source=document_infer \u2014 a reasonable inference from what multiple parts of the document collectively show (e.g. a repo with only C files and a README praising simplicity \u2192 \"prefers low-level, minimal implementations\"). Use sparingly.\n6. Confidence: high for source=document facts, medium for source=document_infer.\n7. Facts worth extracting: skills and expertise, projects built, stated opinions and philosophy, tools and languages used, patterns across work, goals and motivations, background and experience.\n8. If nothing meaningful can be extracted from a document, stop without calling any write tools.\n\nRules:\n- Write facts in a timeless, archival format: use absolute dates (YYYY-MM-DD) rather than relative terms like \"recently\", \"currently\", \"just\", or \"last week\". A fact must be interpretable correctly even years after it was written.\n- One file per distinct topic. Do NOT put unrelated facts in the same file.\n- Create new files freely \u2014 focused files are better than bloated ones.\n- Content should be raw facts only \u2014 no filler commentary.";
 export const deletePrompt: "You are a memory manager performing a TARGETED deletion.\n\nThe user wants to remove: \"{QUERY}\"\n\nRULES \u2014 read carefully before acting:\n1. Delete all bullets that are ABOUT the subject(s) or entity mentioned in the deletion request.\n   - If the query names a specific entity (a person, project, tool, concept), delete every fact about that entity \u2014 not just the one line that introduces it.\n   - Example: \"project recipe-app\" \u2192 delete ALL facts about the recipe-app project (tech stack, goals, status, etc.).\n2. Do NOT delete facts about unrelated subjects, even if they appear in the same file.\n3. When genuinely unsure whether a bullet is about the target subject, SKIP it.\n4. Never delete an entire file \u2014 only individual bullets via delete_bullet.\n5. Pass the EXACT bullet text as it appears in the file, including all | metadata after the fact.\n\nCurrent memory index:\n```\n{INDEX}\n```\n\nSteps:\n1. Identify which file(s) likely contain the content to delete from the index above.\n2. Use retrieve_file or list_directory if the relevant file is not obvious from the index.\n3. Use read_file to read the identified file(s).\n4. Call delete_bullet for each bullet that is about the subject(s) in the deletion request.\n5. If nothing matches, stop without calling delete_bullet.";
 export const deepDeletePrompt: "You are a memory manager performing a COMPREHENSIVE deletion across ALL memory files.\n\nThe user wants to remove: \"{QUERY}\"\n\nRULES \u2014 read carefully before acting:\n1. Delete all bullets that are ABOUT the subject(s) or entity mentioned in the deletion request.\n   - If the query names a specific entity (a person, project, tool, concept), delete every fact about that entity wherever it appears.\n   - Example: \"project recipe-app\" \u2192 delete ALL facts about the recipe-app project across every file.\n2. Do NOT delete facts about unrelated subjects.\n3. When genuinely unsure whether a bullet is about the target subject, SKIP it.\n4. Never delete an entire file \u2014 only individual bullets via delete_bullet.\n5. Pass the EXACT bullet text as it appears in the file, including all | metadata after the fact.\n\nYou MUST read every file listed below and check it for matching content.\n\nFiles to check:\n{FILE_LIST}\n\nSteps:\n1. Use read_file to read each file listed above, one by one.\n2. For each file, call delete_bullet for any bullet that is about the subject(s) in the deletion request.\n3. Continue until every file has been checked.\n4. If a file has no matching bullets, move on without calling delete_bullet for it.";

package/types/types.d.ts

@@ -77,6 +77,7 @@ export type ToolFunctionParameters = {
     properties: Record<string, {
         type: string;
         description?: string;
+        items?: object;
     }>;
     required: string[];
 };
@@ -226,6 +227,7 @@ export type ExtractionExecutorHooks = {
     mergeWithExisting?: ((existing: string | null, incoming: string, path: string) => string) | undefined;
     refreshIndex?: ((path: string) => Promise<void>) | undefined;
     onWrite?: ((path: string, before: string, after: string) => void) | undefined;
+    updatedAt?: string | undefined;
 };
 export type ToolExecutor = (args: any) => Promise<string>;
 export type StorageBackend = {