How A Request Runs
A Row-Bot request is a controlled loop, not a single message sent blindly to every connected service.
- A thread provides continuity. Your message joins the selected conversation. The thread supplies recent history and any thread-specific model or profile choice.
- Row-Bot assembles useful context. Depending on your settings and request, this can include profile instructions, pinned or task-selected Skills, attachments, and relevant local memory or document results. Enabled skills that are not yet selected stay in a compact searchable catalog. It does not mean the whole local data directory is attached.
- The selected model route receives the model prompt. A local model keeps that inference on the configured local runtime. A hosted, API, subscription, or remote custom endpoint sends the assembled prompt to that provider under its terms.
- The model may answer or ask for a tool. Core tools are bound under the active profile. In Auto mode, Row-Bot can search enabled external MCP, plugin, Custom Tool, and channel capabilities when needed. It then checks that the selected tool is enabled, provider-compatible, and permitted by policy.
- Consequential actions stop at an approval boundary. The approval describes the proposed action and target. Rejecting it prevents that action; approving it does not give unrelated future actions permission.
- Tool results return to the active run. A local file tool, browser, channel, account, plugin, or MCP server has its own execution and data boundary. The model can use the result to continue the loop.
- The result is recorded locally. The thread keeps the conversation and run evidence. Optional extraction, memory, and document features decide what becomes reusable knowledge later.
Three Boundaries To Keep In Mind
| Boundary | What crosses it | What controls it |
|---|---|---|
| Model route | The assembled prompt and later tool results needed for reasoning. | Selected provider/model, thread override, profile or workflow policy. |
| Tool execution | Arguments needed by a local or external capability. | Tool enablement, workspace or account scope, approval policy. |
| Durable knowledge | Reviewed or extracted information that may be recalled in another request. | Memory, Knowledge, document, embedding, and retention settings. |
Local-first describes where Row-Bot and its durable data live. It does not make a hosted model, web tool, channel, remote MCP server, realtime voice provider, or external account local.
Change How Requests Run
- Choose routes and defaults in Models And Providers, Provider Settings, and Model Settings.
- Control tools and approvals in Tools, Approvals, And Terminal and Privacy And Safety.
- Control reusable context in Knowledge Settings, Documents Settings, and Skills Settings.
- Configure automatic or eager external capability loading in Tools Settings and read Progressive Tools And Skills.