@columenlabs/lumen-ai 0.1.142 → 0.1.143

package/README.md

@@ -165,7 +165,7 @@ The standard way to search an app's records (Columen's canonical setup, 2026-10-
 - **Words** are matched by an FTS5 index (`porter unicode61`, so "egg" finds "eggs"): `any`, `all`, `none` (leave out: "no milk"), and `in` to say which fields to look in.
 - **Meaning** comes from Vectorize, opt in per app: `like` ("something light for a hot day") asks the index for the nearest rows, and the same filters and words trim them.
 - **Worked-out fields**: a number, date or tag field may be the app's own SQL over the row (`sql: 'json_array_length(t.steps)'`) instead of a column.
-- **Counts**: the result carries `count` (all matches), `returned` and `same_name` (different rows that share a name), so the model says the right number.
+- **Counts**: the result carries `count` (all matches), `returned` and `same_name` (different rows that share a name), so the model says the right number. A search by meaning carries `nearest: true` and no `count`: its rows are the nearest few, not every row that fits, so the model never quotes them as a number of matches.
 
 ```ts
 import { d1Sql, defineFind, findSql, findTool } from '@columenlabs/lumen-ai/assistant';

package/dist/assistant/engine.js

@@ -960,7 +960,7 @@ export class Assistant {
             'Answer in short plain sentences. Use the tools for facts; never guess a number a tool can give you. Call several tools at once when they do not depend on each other.',
             ...([...fns.values()].some((f) => f.def.find)
                 ? [
-                    'Questions about an app\'s records go through its find tool (the tool named <app>_find): put every condition of the question in one call (filters, words to include or leave out, which fields to look in), ask only for the fields the answer needs, then judge the rest yourself from what it returns. Never list or open records one by one to filter them. A loose ask (a mood, an occasion, "something light", "good for a party") goes in its like field when the tool has one; then pick from what it returns yourself. How many match is the result\'s count: say that number, and name each row in same_name, which are different records that share a name. Rows a find already returned you use again only when they answer the whole new question; a new condition (another ingredient, a kind of dish, how quick) is a new find call.',
+                    'Questions about an app\'s records go through its find tool (the tool named <app>_find): put every condition of the question in one call (filters, words to include or leave out, which fields to look in), ask only for the fields the answer needs, then judge the rest yourself from what it returns. Never list or open records one by one to filter them. A loose ask (a mood, an occasion, "something light", "good for a party") goes in its like field when the tool has one; then pick from what it returns yourself. How many match is the result\'s count: say that number (a like search has no count, only the nearest rows: never give a number of matches for it), and name each row in same_name, which are different records that share a name. Rows a find already returned you use again only when they answer the whole new question; a new condition (another ingredient, a kind of dish, how quick) is a new find call.',
                 ]
                 : []),
             ...([...fns.values()].some((f) => !f.draft && !f.write) && !fns.has(BATCH)

package/dist/assistant/find.d.ts

@@ -86,8 +86,13 @@ export interface FindQuery {
     [tagOrRange: string]: unknown;
 }
 export interface FindResult {
-    /** Rows that match, all of them, before `limit`. Say this number when asked how many. */
-    count: number;
+    /**
+     * Rows that match, all of them, before `limit`. Say this number when asked how many. Left out
+     * of a search by meaning, whose rows are the nearest few, not every row that fits.
+     */
+    count?: number;
+    /** Set on a search by meaning: the rows are the nearest in meaning, nearest first, to pick from. */
+    nearest?: true;
     /** Rows in this answer (at most `limit`). */
     returned: number;
     rows: Record<string, unknown>[];

package/dist/assistant/find.js

@@ -301,8 +301,11 @@ export async function runFind(def, sql, q, meaning) {
         return row;
     });
     const same = sameNames(def, out, built.fields);
+    const byMeaning = !!near?.length;
+    if (byMeaning)
+        notes.push('These are the nearest in meaning, nearest first, not every row that fits: pick from them and do not say how many match.');
     return {
-        count,
+        ...(byMeaning ? { nearest: true } : { count }),
         returned: out.length,
         rows: out,
         ...(same.length ? { same_name: same } : {}),
@@ -407,7 +410,7 @@ export async function findTool(def, sql, opts = {}) {
         .join(', ');
     return {
         name: `${def.name}_find`,
-        description: `Finds ${def.label}s in one query${def.about ? ` (${def.about})` : ''}: put every condition of the question in one call (filters, words to include or leave out, which fields to look in${meaning ? ', and like for a loose ask' : ''}) and ask only for the fields the answer needs. Fields: ${fields}. Returns the matching ${def.label}s, how many match in all (count) and any that share a name (same_name).`,
+        description: `Finds ${def.label}s in one query${def.about ? ` (${def.about})` : ''}: put every condition of the question in one call (filters, words to include or leave out, which fields to look in${meaning ? ', and like for a loose ask' : ''}) and ask only for the fields the answer needs. Fields: ${fields}. Returns the matching ${def.label}s, how many match in all (count; a like search returns the nearest instead, marked nearest, with no count) and any that share a name (same_name).`,
         inputSchema: schemaOf(def, tags, Boolean(meaning)),
         read: true,
         find: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@columenlabs/lumen-ai",
-  "version": "0.1.142",
+  "version": "0.1.143",
   "description": "Lumen's assistant and agent parts: a chat assistant's server (Claude tiers, tools over MCP, the web, hand off, spend caps), serving an MCP server from a Worker, read-only tool sets and metered tool calls.",
   "license": "MIT",
   "type": "module",
@@ -41,8 +41,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "0.133.0",
-    "@columenlabs/lumen-ops": "0.1.142",
-    "@columenlabs/lumen-ui-types": "0.1.142",
+    "@columenlabs/lumen-ops": "0.1.143",
+    "@columenlabs/lumen-ui-types": "0.1.143",
     "openai": "7.32.0",
     "zod": "^4.3.6"
   },