@usabledev/usable-chat 1.166.0 → 1.167.1

package/cli.js

@@ -90993,7 +90993,7 @@ var init_data_staging_prompt = __esm({
     "use strict";
     DATA_STAGING_PROMPT = `# Staged Data \u2014 read THIS first
 
-The user can drop CSV / TSV / Parquet / XLSX / XLS / JSON / NDJSON / \`.duckdb\` files, paste a URL, or attach a local browser folder. Files stage into a browser-side DuckDB; bytes never leave the user's browser. You query them via the \`data_*\` tools and only see structured JSON results.
+The user can drop CSV / TSV / Parquet / XLSX / XLS / JSON / NDJSON / \`.duckdb\` files, paste URL, or attach a browser folder. Files stage into browser DuckDB. \`RAW\` entries have no rows/cols; host uses \`chat.data.readBytes(alias)\`.
 
 In the actual tool list these usually appear with a \`parent_\` prefix, e.g. \`parent_data_list\`, \`parent_data_load_browser_file\`, \`parent_data_describe\`, \`parent_data_query\`. If present, call the exact \`parent_data_*\` tool; shorter \`data_*\` names below are canonical.
 
@@ -91001,7 +91001,7 @@ In the actual tool list these usually appear with a \`parent_\` prefix, e.g. \`p
 
 Whenever the user types any of these (or anything similar): **"analyze this"**, **"what's in the file"**, **"the data"**, **"the file"**, **"this CSV / spreadsheet / parquet / dataset"**, **"summarise this"**, **"chart this"**, **"plot this"**, **"what does the data look like"** \u2014 **ALWAYS** call \`data_list\` BEFORE you reply.
 
-- If \`data_list\` returns at least one file, **THAT IS WHAT THE USER MEANS**. Proceed with \`data_describe\` \u2192 tools.
+- If \`data_list\` returns a structured file, **THAT IS WHAT THE USER MEANS**. Proceed with \`data_describe\` \u2192 tools. If only \`RAW\` matches, explain that the host app parses it.
 - **NEVER** reply *"please upload a file"*, *"share the file with me"*, *"I don't have access to the file"*, or any variation when \`data_list\` returns \u2265 1 entry. The file is already staged. Just analyse it.
 - **NEVER** ask the user to paste rows. They already gave you the file; query it through the tools.
 - If the user names a file in the attached local folder and it is NOT in \`data_list\`, call \`parent_data_load_browser_file({ path })\` / \`data_load_browser_file({ path })\` first, then list + describe.
@@ -91432,6 +91432,20 @@ var init_parent_tools = __esm({
           required: ["alias"]
         }
       },
+      {
+        name: "data_get_bytes",
+        description: "Return a staged file's raw browser bytes as base64 so the embed host can parse host-specific formats (for example GPX, KML, KMZ) without Usable Chat shipping per-format parsers. Pass a parent alias from data_list; child table aliases are rejected.",
+        parameters: {
+          type: "object",
+          properties: {
+            alias: {
+              type: "string",
+              description: "Alias from data_list. For .duckdb files, pass the parent alias."
+            }
+          },
+          required: ["alias"]
+        }
+      },
       {
         name: "data_load_remote",
         description: "Fetch a CSV/TSV/Parquet/JSON/NDJSON/XLSX/.duckdb file from an HTTPS URL and stage it as if the user had uploaded it. By DEFAULT the request routes through a same-origin proxy (/api/data-proxy with RFC 7233 Range support) \u2014 this is required because the chat's CSP `connect-src` is locked to a small allowlist, so direct cross-origin fetches will fail. Only pass `useProxy: false` when the URL is on a CSP-allowlisted host (rare). Format is auto-detected from the URL extension; pass `format` explicitly when the URL has no extension (e.g. share-link APIs that return a UUID). For `.duckdb` files, multiple sub-aliases are returned \u2014 one per attached table.",
@@ -308972,7 +308986,7 @@ init_tui_select();
 init_model_registry();
 
 // package.json
-var version2 = "1.166.0";
+var version2 = "1.167.1";
 
 // src/adapters/cli/model-catalog.ts
 init_codex_auth();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usabledev/usable-chat",
-  "version": "1.166.0",
+  "version": "1.167.1",
   "description": "usable-chat — terminal harness for usable-chat (headless + TUI)",
   "type": "module",
   "bin": {