From 3eecfa8b44a4b25cfa7061985671508ffc75c0d8 Mon Sep 17 00:00:00 2001 From: os-zhuang Date: Fri, 26 Jun 2026 14:51:09 +0800 Subject: [PATCH] docs(ai-capabilities): in-UI ask & build are cloud/Enterprise, not open-source MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The agent table marked `ask` as "open-source · free" and the skills section called only `build` cloud-only — both contradicted the note at the top of the guide (the in-UI AI runtime ships in the cloud/Enterprise distribution; the open framework exposes objects, queries, and actions to your own AI via @objectstack/mcp). Mark both in-UI agents cloud/Enterprise, add a short pointer to the MCP/BYO-AI path, and align the skills tiering note. Co-Authored-By: Claude Opus 4.8 --- content/docs/guides/ai-capabilities.mdx | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/content/docs/guides/ai-capabilities.mdx b/content/docs/guides/ai-capabilities.mdx index 1f06be69f1..99fc339b41 100644 --- a/content/docs/guides/ai-capabilities.mdx +++ b/content/docs/guides/ai-capabilities.mdx @@ -50,8 +50,13 @@ is in — the user never picks from a roster: | Agent | Surface | Does | Edition | |---|---|---|---| -| **`ask`** | data console | Read / query / explore records + run the business **actions** the app exposes. RLS-bounded. | open-source · free | -| **`build`** | Studio | Author *metadata* (objects, fields, views, flows) via plan → draft → verify → publish. | cloud · paid | +| **`ask`** | data console | Read / query / explore records + run the business **actions** the app exposes. RLS-bounded. | cloud / Enterprise | +| **`build`** | Studio | Author *metadata* (objects, fields, views, flows) via plan → draft → verify → publish. | cloud / Enterprise | + +Both in-UI agents ship in the **cloud / Enterprise** distribution, not the open +framework. A self-hosted **open-source** runtime has no in-product `ask`/`build` +assistant; it instead exposes the same objects, queries, and actions to *your own* +AI through **`@objectstack/mcp`** (bring-your-own-AI) — see the note at the top. There is no per-turn intent classifier and no agent dropdown: the surface binds the agent (data console → `ask`, Studio → `build`). A `build`-shaped request that @@ -68,8 +73,10 @@ Actions / Flows / queries; it then attaches to `ask`. Every skill declares surface-compatible skills' tools** — there is no global fall-through, so a skill reaches an agent only when their surfaces match ([ADR-0064](https://github.com/objectstack-ai/framework/blob/main/docs/adr/0064-tool-scoping-to-agent.md)). -`surface:'build'` skills are inert on the open-source framework (the `build` agent -is cloud-only) — intentional tiering, not a bug. +The in-UI `ask` and `build` agents are cloud / Enterprise only, so +`surface:'ask'` / `surface:'build'` skills bind no in-product agent on the +open-source framework — there you reach the same Actions, Flows, and queries +through `@objectstack/mcp` instead. Intentional tiering, not a bug. ### The shape of an agent