@mindstudio-ai/agent 0.1.86 → 0.1.87
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.js +57 -14
- package/dist/index.d.ts +161 -0
- package/dist/index.js +46 -3
- package/dist/index.js.map +1 -1
- package/dist/postinstall.js +57 -14
- package/llms.txt +11 -3
- package/package.json +1 -1
package/llms.txt
CHANGED
|
@@ -8,7 +8,7 @@ This file is the complete API reference. No other documentation is needed to use
|
|
|
8
8
|
|
|
9
9
|
There are 150+ actions available. Do NOT try to read or load them all at once. Follow this discovery flow:
|
|
10
10
|
|
|
11
|
-
1. **Identify yourself** — Call `changeName` to set your display name (use your name or whatever your user calls you). If you have a profile picture
|
|
11
|
+
1. **Identify yourself** — Call `changeName` to set your display name (use your name or whatever your user calls you). If you have a profile picture, pass its public image URL to `changeProfilePicture`. This helps users identify your requests in their logs.
|
|
12
12
|
2. **Ask** — Use `mindstudio ask "your question"` (CLI) or the `ask` MCP tool for SDK guidance. It knows every action, model, and connector and returns working TypeScript code with real model IDs and config options. Examples: `mindstudio ask "generate an image with FLUX"`, `mindstudio ask "what models support vision?"`, `mindstudio ask "how do I send a Slack message?"`.
|
|
13
13
|
3. **Browse** — For manual discovery, call `listActions` (MCP tool) or `mindstudio list-actions --summary` (CLI) to get a compact `{ action: description }` map of everything available (~3k tokens). Call `mindstudio info <action>` (CLI) for parameter details.
|
|
14
14
|
4. **Call it** — Invoke the action with the required parameters. All actions share the same calling convention (see below).
|
|
@@ -1791,7 +1791,7 @@ await mindstudio.changeProfilePicture('https://example.com/avatar.png');
|
|
|
1791
1791
|
```
|
|
1792
1792
|
|
|
1793
1793
|
#### `uploadFile(content, options)`
|
|
1794
|
-
|
|
1794
|
+
**Deprecated for app file storage** — use the `files` store below (`files.defineStore(...).put(...)`): private by default, app-scoped, and served on the app's own domain. `uploadFile` uploads to the shared account media CDN and remains only for account-level assets (e.g. an agent avatar for `changeProfilePicture`). Gets a signed upload URL, PUTs the file content, and returns the permanent public URL.
|
|
1795
1795
|
|
|
1796
1796
|
```typescript
|
|
1797
1797
|
import { readFileSync } from 'fs';
|
|
@@ -1856,9 +1856,17 @@ const context = results.map((r) => r.text).join(String.fromCharCode(10, 10));
|
|
|
1856
1856
|
// add a document (background — poll documents() for status)
|
|
1857
1857
|
await Policies.add(buffer, { filename: 'policy.pdf', contentType: 'application/pdf' });
|
|
1858
1858
|
const docs = await Policies.documents();
|
|
1859
|
+
|
|
1860
|
+
// introspection — what is in the corpus, and how one document was split
|
|
1861
|
+
const { chunkCount, pipeline } = await Policies.stats(); // counts + the config actually in effect
|
|
1862
|
+
const chunks = await Policies.chunks(docs[0].id); // why a document does or doesn't match
|
|
1859
1863
|
```
|
|
1860
1864
|
|
|
1861
|
-
`SearchHit`: `{ score, text, citation: { documentId, filename, pageNumber, headingPath, boundingBox?, url } }`. `citation.url` is a stable on-domain link to the source document — drop it in an `<a href>`.
|
|
1865
|
+
`SearchHit`: `{ score, text, citation: { documentId, filename, pageNumber, chunkIndex, headingPath, boundingBox?, url } }`. `citation.url` is a stable on-domain link to the source document — drop it in an `<a href>`. `(documentId, chunkIndex)` is a chunk's stable identity — key an eval set on that, not on `text`.
|
|
1866
|
+
|
|
1867
|
+
Also on each hit: `retrievalRank`/`retrievalScore` (position before reranking — compare with the final position to see what reranking did). Two opt-in search options for debugging: `explain: true` adds `explain.{dense,lexical,matchedVia}` so you can see which half of hybrid found a hit, and `expand: 1` adds `neighbors.{before,after}` for surrounding context. Neither changes the results or their order.
|
|
1868
|
+
|
|
1869
|
+
Search is deterministic for a fixed corpus and configuration — same query, same order — so regression checks are meaningful. `search()` also returns `latencyMs`.
|
|
1862
1870
|
|
|
1863
1871
|
Supported: pdf, docx, pptx, xlsx, odt, rtf, epub, images, txt, md, json, csv, html.
|
|
1864
1872
|
|