# Row-Bot Docs Full Text

Concatenated public documentation for Row-Bot.

## Row-Bot Documentation

Route: /docs/

A complete public user guide for installing, configuring, and using Row-Bot end to end.

# Row-Bot Documentation Row-Bot is a local-first desktop AI assistant for people who want models, memory, tools, workflows, design, code help, integrations, and voice in one controllable app. This guide explains how to install Row-Bot, choose a model path, use the main interface, configure settings, and understand what happens when Row-Bot uses external services. These pages describe Row-Bot 4.5.0, the current stable release represented by this source tree. ## Start Here - [Getting Started](/docs/getting-started/) explains the install path, first launch, and setup choices. - [Row-Bot Interface](/docs/app-shell/navigation) tours the sidebar, thread list, Home tabs, Activity Center, Buddy, Settings, and terminal. - [Chat](/docs/chat/) explains conversations, composer controls, attachments, model selection, approvals, and tool results. - [Settings](/docs/settings/) explains every configuration tab and what each choice changes. - [Profiles, Goals, And Agents](/docs/profiles-goals-agents/) explains reusable roles, bounded goals, and delegated work. - [Computer Use](/docs/computer-use/) explains the opt-in native desktop tool, setup, live controls, and safety boundaries. ## Feature Guides - [Workflows](/docs/guides/workflows) for repeatable background work and scheduled agents. - [Designer Studio](/docs/designer/) for creating pages, slides, mockups, branded assets, and exportable designs. - [Developer Studio](/docs/developer/) for folders, repositories, code chat, inspectors, commands, and sandbox modes. - [Knowledge](/docs/knowledge/) for local memory, documents, graph review, and background organization. - [Computer Use](/docs/computer-use/) for target-window automation in native Windows and macOS applications. - [Android And Native Desktop](/docs/mobile-native/) for pairing, mobile Chat and Activity, and native-only behaviour. - [Monitor](/docs/monitor/) for logs, journals, channel state, and background activity. - [Skills Hub](/docs/skills/) for browsing, enabling, creating, and reviewing skills. - [Channels](/docs/integrations/channels), [MCP](/docs/integrations/mcp), and [Plugins](/docs/integrations/plugins) for integrations. - [Extend Row-Bot](/docs/extending/) to choose safely between Skills, Custom Tools, plugins, MCP, channels, and accounts. - [Operations, Data, And Recovery](/docs/operations/) for backups, restore, updates, repair, uninstall, and diagnostic sharing. - [Voice and Buddy](/docs/voice-and-buddy/) for speech input, Talk, Dictate, read-aloud, and the visual companion. ## How To Read These Docs Each major page explains what the feature is, where to find it, the important controls, a common workflow, what is saved, privacy and safety implications, and troubleshooting. Screenshot captions describe the product UI so you can connect the text to what you see in the app. ## References Use [Reference](/docs/reference/) when you need tables of tools, providers, settings tabs, channels, skills, MCP servers, plugins, storage, or approval behavior. The guided pages should be your first stop; the reference pages are for lookup.

## Getting Started

Route: /docs/getting-started/

Install Row-Bot, complete first launch, and learn the first choices that matter.

# Getting Started Start here if you are new to Row-Bot. You only need three things for a useful first session: the app installed, one working model path, and a basic understanding of where Row-Bot stores local data. ## The Short Path 1. Install Row-Bot from the release package for your platform. 2. Launch the app and complete the first-run wizard. 3. Choose one model path: local Ollama, a hosted provider, a subscription account, or a custom endpoint. 4. Send a first chat message. 5. Open Settings later when you are ready for documents, workflows, Designer, Developer, channels, MCP, plugins, Skills, Buddy, or voice. ## Important Concepts - **Local app** means Row-Bot runs on your machine and opens a local desktop or browser window. - **Data directory** means the folder where Row-Bot keeps conversations, memories, documents, settings, workflows, logs, Designer projects, Developer workspaces, skills, plugins, and local integration state. - **Model provider** means the service or local runtime that supplies a model. Ollama is local; API and subscription providers usually use the internet. - **Tools** are actions Row-Bot can take, such as reading files, searching documents, using a browser, running Developer commands, or sending through a channel. - **Approvals** are prompts that ask you to review sensitive actions before Row-Bot proceeds. ## Pages In This Section - [Installation](/docs/getting-started/installation) - [First Launch](/docs/getting-started/first-launch) - [Row-Bot Interface](/docs/app-shell/navigation)

## Installation

Route: /docs/getting-started/installation

Install Row-Bot from a release package or run it from source with clear next steps.

# Installation For ordinary use, install Row-Bot from the latest release package for your operating system. Running from source is useful for contributors, testers, and people who want to inspect or modify the app. ## Install From A Release 1. Download the latest Row-Bot release for Windows, macOS, or Linux. 2. Run the installer or unpack the archive. 3. Launch Row-Bot from the Start Menu, Applications, app launcher, or the provided command. 4. Let the first-run wizard open and choose a model path. The installed app starts a local Row-Bot process and opens the UI in a desktop window or browser, depending on your platform and launch preference. If the usual port is busy, Row-Bot chooses another local port. ## Run From Source Use the source path if you are developing Row-Bot or testing changes: 1. Clone the repository. 2. Create a Python environment. 3. Install uv and sync the locked Python dependencies with `uv sync --locked --all-extras --group test`. 4. Install the docs-site dependencies only if you are working on documentation. 5. Run the app entry point from the repository. `requirements.txt` is a generated pip export from `uv.lock` for installer compatibility. It is available as a fallback for environments that cannot use uv, but source dependency changes should be made in `pyproject.toml`. Source runs use the same local data concepts as the packaged app. Keep test data separate from personal data when experimenting. ## Local Data Directory Row-Bot stores local app data under the active Row-Bot data directory. This includes conversations, memories, model/provider metadata, workflows, Designer projects, Developer workspace records, documents, logs, skills, plugins, Buddy assets, channel settings, and MCP settings. Advanced users can set `ROW_BOT_DATA_DIR` before launch to use a separate data directory for testing or portable runs. Do this before starting the app, and remember that Row-Bot will treat that folder as the active local data store for the whole process. ## After Installing Continue to [First Launch](/docs/getting-started/first-launch). You can finish optional setup later from the Setup Center and Settings.

## First Launch

Route: /docs/getting-started/first-launch

Complete the first-run wizard, choose a model path, and revisit setup later.

# First Launch The first-run wizard appears until setup is complete. Its job is to help you connect one working model path so Row-Bot can answer a first chat message. Everything else can be configured later. ## Choose A Model Path A model is the AI system that writes responses and reasons through tasks. Row-Bot can work with several kinds of model providers: | Path | Good For | Tradeoffs | | --- | --- | --- | | Local Ollama | Privacy-focused local chats and tool use when your machine has enough resources. | Requires installing models locally. Larger models need more memory and disk space. | | Hosted API provider | Strong models without local downloads. | Requires an API key, internet access, and provider billing. Prompt content can be sent to that provider. | | Subscription account | Using a supported account-backed provider from inside Row-Bot. | Requires sign-in or token import and follows that provider's account terms. | | Custom endpoint | Advanced local or self-hosted runtimes such as LM Studio, vLLM, llama.cpp, LocalAI, LiteLLM, or SGLang. | Requires endpoint details and compatible model behavior. Tool use needs enough context and function-calling support. | For beginners, start with the provider path you already trust. If you are unsure, Ollama is the simplest local-first path, while an API provider is usually the quickest path to strong hosted models. ## Setup Center Setup Center is the place to finish or revisit optional setup after the first launch. It can guide you through models, documents, workflows, Designer, Developer, channels, accounts, MCP, plugins, Buddy, and voice. The wizard gets you started; Setup Center helps you build out the rest of your app over time. ## Privacy, Cost, And Credentials Local model runs can stay on your machine. Hosted, subscription, realtime voice, web search, account, channel, MCP, and plugin features can contact outside services when configured and used. Provider keys and account tokens should be entered only through the relevant Settings or account flow. Cost depends on the provider or service you choose. ## Troubleshooting - If the wizard cannot find a local model, start Ollama and install a model first. - If a hosted provider connects but no models appear, refresh Providers and Models. - If you skip optional setup, open Setup Center or Settings later.

## Models And Providers

Route: /docs/configuration/models-and-providers

Configure providers, discover models, choose defaults, and pin quick model choices.

# Models And Providers Providers are where models come from. Models are the specific choices you use in Chat, workflows, Designer, Developer, voice, and other Row-Bot surfaces. To understand what leaves the app, when tools run, and where approvals fit, read [How A Request Runs](/docs/concepts/request-lifecycle). ## Recommended Setup Order 1. Open Settings -> Providers. 2. Connect one provider path. 3. Refresh provider health. 4. Open Settings -> Models. 5. Refresh the catalog. 6. Choose a default model. 7. Pin Quick Choices. 8. Test in Chat. ## Choosing A Provider Path Use local Ollama for local-first privacy and no provider billing. Use an API provider for strong hosted models. Use a subscription account when you already have the supported provider account. Use a custom endpoint for advanced local or self-hosted OpenAI-compatible runtimes. ## Choosing Models Keep at least one everyday chat model and one stronger tool-capable model pinned. For Developer, Designer, workflows, and complex tools, choose a model that can handle tool calls and enough context. ## Troubleshooting - If a provider connects but has no models, refresh Models. - If a model fails with tools, choose a tool-capable model. - If a custom endpoint fails, check base URL, model name, API compatibility, and context window.

## Row-Bot Interface

Route: /docs/app-shell/navigation

Navigate Row-Bot's sidebar, threads, Home tabs, Activity Center, Buddy, Settings, and terminal.

# Row-Bot Interface The Row-Bot Interface is the main workspace you see after launch. It combines conversations, Home tabs, status panels, approvals, workflows, Buddy, Settings, and terminal output in one local app window. ## Left Sidebar - **Home** returns to the Home tabs: Workflows, Designer, Developer, Knowledge, and Monitor. - **New** starts a fresh conversation thread. - **Conversations** shows recent threads. The sidebar keeps the list short so the workspace stays usable; use **Show all** when you need older threads. - **Thread menu** on a conversation row opens actions such as rename and delete. - **Rename** changes the visible thread title without changing the messages. - **Delete** removes the thread after confirmation. Use it carefully if you still need the conversation history. - **Agent profiles** opens the profile selector and profile management area. - **Buddy** appears near the bottom when enabled. - **Settings** opens the full configuration dialog. ## Show All Threads When you have more threads than the sidebar shows, use Show All from the conversations area. The dialog is for search and cleanup: find an older thread, reopen it, rename it, or delete it after confirming. Start a new thread when the task has a new goal; continue an existing thread when the earlier context still matters. ## Home Tabs The central Home area has five tabs: - **Workflows** for saved automations and background agents. - **Designer** for starting design projects. - **Developer** for opening code workspaces and Custom Tools. - **Knowledge** for memory, document, and graph review. - **Monitor** for logs, journals, channel state, and background activity. Home pages in these docs are short entry-point pages. The dedicated feature pages are the full guides. ## Activity Center And Right Drawer The right side summarizes what needs attention: - **Current goals and agents** shows running or waiting goal-mode and child-agent activity. - **Approvals** shows pending approval prompts from chats, child agents, and background work. - **Workflows** shows active and upcoming workflow state, plus run and new controls. - **Launch** lets you choose a workflow and run it manually. - **Insights** expands supporting status and suggestions when available. Use the Activity Center when you want to know whether Row-Bot is idle, waiting for you, running background work, or ready to launch a workflow. Child-agent approvals also appear in the parent thread so you can decide without leaving the conversation. ## Terminal Panel The terminal panel at the bottom shows command-oriented output when a tool, Developer workspace, or local runtime exposes it through the UI. It is not a general replacement for your system terminal. Command execution still follows Row-Bot's active tool availability, workspace boundaries, and approval mode. ## Agent Profiles Agent profiles change how Row-Bot behaves for a thread or specialist run. The sidebar profile control opens the profile selector; the detailed walkthrough is in [Agent Profiles](/docs/app-shell/agent-profiles). ## What Is Saved Threads, thread names, selected models, profile choices, workflow records, knowledge records, settings, and logs are saved in the local Row-Bot data directory. Some choices are thread-specific; Settings usually changes global app behavior. ## Troubleshooting - If a thread is missing from the sidebar, open Show All and search. - If a panel looks stale, use the visible refresh control or reload the app. - If a button is disabled, check the related Settings tab and Monitor for readiness messages.

## Chat

Route: /docs/chat/

Use Row-Bot chat, composer controls, model choices, attachments, tools, approvals, and history.

# Chat Chat is the main place to ask Row-Bot for help. A chat thread can stay simple, or it can use models, memory, documents, tools, approvals, attachments, skills, voice, workflows, and specialist profiles. ## UI Walkthrough - **Thread header** shows the current thread title and actions such as rename, profile selection, model state, and export when available. - **Transcript** contains user messages, assistant responses, tool results, charts, images, reasoning sections, and status messages. - **Composer** is where you type the next request. Use plain language and include the outcome you want. - **Send** submits the composer text to the selected model. - **Stop** appears while Row-Bot is responding and asks the current run to stop. - **Regenerate or retry controls** appear when a response can be run again. - **Model picker** chooses the model for this thread. See [Model Picker](/docs/chat/model-picker). - **Approval mode** controls how sensitive actions are reviewed for this thread. - **Attachments and context controls** add files or local context to the current request. - **Skills and slash commands** help start structured tasks when available. - **Voice buttons** use Dictate or Talk when voice is configured. - **Tool traces** show what tools Row-Bot used and what came back. - **Approval prompts** pause gated actions until you approve or reject them. When a child agent needs approval, the prompt appears in the parent thread too. ## Beginner Workflow 1. Start a new thread. 2. Choose a model that is ready for chat. 3. Ask one clear question or task. 4. Attach files only when the task needs them. 5. Review any approval prompt before allowing Row-Bot to act. 6. Rename the thread when it becomes useful enough to keep. ## Power Workflow 1. Choose an Agent Profile for the kind of work. 2. Pick a stronger tool-capable model. 3. Attach documents or enable retrieval only for relevant context. 4. Let Row-Bot use tools, but approve file writes, browser actions, shell commands, account actions, channel sends, MCP calls, and plugin tools deliberately. 5. Export or continue the thread after the work is complete. ## What Is Saved Thread names, messages, selected model overrides, approval mode, profile selection, attachments copied into Row-Bot-managed storage, and tool results are saved locally. Some external providers may receive prompt content when you choose their models. ## Privacy And Safety Local model runs can stay on your machine. Hosted models, web search, browser actions, account tools, MCP servers, plugins, and channels can send data outside the app when configured and used. Row-Bot should not insert secrets into chat; enter credentials only through Settings or the provider's sign-in flow. ## Troubleshooting - If Row-Bot cannot answer with the current model, choose a more capable model in the picker. - If attachments are ignored, confirm the files finished uploading and are relevant to the prompt. - If a tool is unavailable, check Settings, the current Agent Profile, and approval mode. - If a run is stuck, press Stop, then retry with a narrower prompt.

## Model Picker

Route: /docs/chat/model-picker

Choose, pin, and troubleshoot Row-Bot models across local, hosted, subscription, and custom providers.

# Model Picker The Model Picker chooses which model powers the current chat thread. It is where provider setup becomes visible in day-to-day use. ## Where Models Come From Models appear after Row-Bot discovers them from a connected provider or local runtime: - Local Ollama models come from the Ollama service running on your machine. - API provider models come from a provider connected in Settings -> Providers. - Subscription models come from a supported account-backed provider after sign-in or token import. - Custom endpoint models come from the compatible endpoint details you provide. - Pinned Quick Choices come from Settings -> Models and are shown first for convenience. ## UI Walkthrough - **Pinned models** are your quick picks for everyday use. - **Provider groups** keep local, API, subscription, and custom endpoint models understandable. - **Search** narrows long model lists. - **Capability labels** help distinguish chat, tool-capable, vision, reasoning, embedding, media, and voice models. - **Disabled or missing providers** stay out of normal selection until they are configured and healthy. - **Thread override** means the selected model applies to the active thread without changing your global default. ## Choosing Well Use a smaller or local model for quick private chats. Use a stronger tool-capable model for workflows, Developer Studio, Designer Studio, long context, or multi-step tool use. For local and self-hosted endpoints, prefer a context window large enough for Row-Bot's instructions and tool schemas. ## Pinning Models Open Settings -> Models, refresh the catalog, and pin the models you use often. Pinning does not create a new model; it just puts an existing discovered model into your Quick Choices. ## Troubleshooting - If a model is missing, refresh Providers, then refresh Models. - If a provider is connected but disabled, review the provider row message. - If a model appears but fails with tools, choose a model labeled or tested for Agent Mode. - If custom endpoint models look duplicated, use the provider-qualified name.

## Tools, Approvals, And Terminal

Route: /docs/chat/tools-approvals-and-terminal

Understand Row-Bot tools, approval prompts, tool results, and terminal output.

# Tools, Approvals, And Terminal Tools are actions Row-Bot can take beyond writing text. They can search documents, read files, use a browser, run Developer commands, create designs, inspect knowledge, call MCP servers, use plugins, or send through channels. ## How Tool Use Appears When Row-Bot uses a tool, the transcript can show a tool trace or result block. Read it as an activity receipt: what Row-Bot tried, what came back, and whether more action is needed. ## Approval Prompts Approval prompts appear when an action can change local files, run commands, contact external systems, use accounts, start servers, send messages, call MCP/plugin tools, or do something else that deserves review. If a child agent needs approval, Row-Bot posts a compact approval prompt in the parent thread, keeps the desktop Activity Center in sync, and routes channel-started work back to the originating channel when possible. The prompt may include a short model-written reason, but Row-Bot's approval policy still decides whether the action is blocked, allowed, or waiting for you. Before approving, check: - What action is being requested. - What file, workspace, account, channel, server, or provider is involved. - Whether the action can send data outside the app. - Whether the proposed command or file change matches your request. - Whether rejecting is safer until you inspect settings. Approving lets Row-Bot continue that action. Rejecting stops that action and returns control to the conversation. On small screens and in channels, prompts stay brief; open the thread or Activity Center when you need more context. ## Terminal Output The terminal panel shows command-style output when Row-Bot surfaces it from local tools, Developer Studio, or related runtime activity. It is a review surface, not permission by itself. Commands still follow workspace boundaries, tool availability, and approval mode. ## Common Workflow 1. Ask for a task that may need tools. 2. Let Row-Bot explain the intended action. 3. Review the approval prompt. 4. Approve only if the action matches your intent. 5. Inspect the tool trace or terminal output. 6. Ask Row-Bot to summarize what changed. ## Troubleshooting - If no approval appears, the action may be read-only or blocked before execution. - If a tool result is confusing, ask Row-Bot to explain the last tool call. - If command output is missing, check whether you are in Developer Studio or a tool-capable context. - If you rejected by mistake, ask Row-Bot to try again and review the next prompt.

## Profiles, Goals, And Agents

Route: /docs/profiles-goals-agents/

Choose reusable Agent Profiles, run bounded goals, and review delegated parent and child agents.

# Profiles, Goals, And Agents These three features work together but solve different problems. An **Agent Profile** is a reusable role and policy. A **goal** is a bounded objective for the current task. An **agent run** is one execution of delegated work, with its own status and evidence. For the mental model behind delegation and hand-offs, read [How Profiles, Goals, And Agents Work](/docs/concepts/profiles-goals-and-agents). ## Choose Or Create A Profile 1. Open a chat and expand **Agent profiles** in the left sidebar. 2. Choose a built-in profile or create one for a repeated role. 3. Keep the role narrow: describe the outcome, sources it may use, and what it must not do. 4. Review its model, skill, tool, delegation, and approval policy. 5. Save it, then select it before asking for work. Profiles do not grant capabilities by themselves. A selected tool must still be enabled, available, and allowed by the active approval policy. A profile that can delegate may start child agents, but each run remains visible in the Activity Center and the chat agent strip. New runs also receive a checkpointed work budget. The Models settings tab shows the recommended application-wide work-round, nesting, concurrency, and optional child active-time limits. Extra children wait in a first-in, first-out queue when capacity is full; changing a setting affects new runs, not work already in progress. ## Run A Goal A goal is useful when work needs more than one turn. State the objective and an observable finish condition. Row-Bot records progress, blockers, evidence, turns, and status so it can continue without pretending that partial work is complete. - **Active** means work can continue. - **Complete** means the objective and required checks are genuinely finished. - **Blocked** is for a repeated impasse that requires your input or an external change. - **Stop** ends the active run; it does not delete the thread or its evidence. ## Review Delegated Work Parent agents coordinate. Child agents handle bounded subtasks. Open an agent row to review its prompt, profile, model, status, result, evidence, and thread. A completed child result is evidence for the parent, not automatic permission to write files, send messages, commit code, or publish. If a run appears stuck, inspect its last update before stopping it. If several agents edit the same resource, narrow their ownership or run them sequentially. Keep consequential final actions with the parent and a human approval point. Repeated model-and-tool states are detected before a run can loop indefinitely. The fourth identical no-progress state is blocked; a fifth ends the run cleanly with a durable reason. Reaching a configured work limit also finalizes the run instead of leaving it marked as active. ## What Is Saved Profiles, goals, agent runs, edges, progress, results, and evidence are stored in the active local data directory. Provider prompts still follow the privacy terms of the model route selected for each run.

## Workflows

Route: /docs/guides/workflows

Create, run, schedule, edit, deliver, and troubleshoot Row-Bot workflows.

# Workflows Workflows are repeatable Row-Bot tasks. Use them for things you want to run again: a morning brief, inbox follow-up, document digest, research check, report draft, or channel delivery. For the execution model behind schedules, persistent runs, approvals, and delivery, read [How Background Workflows Run](/docs/concepts/background-workflows). ## Where To Find Workflows Open Home -> Workflows. The Home tab is the dashboard; this page is the full guide. ## UI Walkthrough - **Workflow list** shows saved workflows, status, next run, and quick actions. - **New Workflow** opens the creation flow. - **Delivery defaults** choose where results go unless a workflow overrides them. - **Run** starts the selected workflow manually. - **Pause/resume** controls whether scheduled runs continue. - **Edit** opens the saved workflow for changes. - **Delete** removes a workflow after confirmation. - **Status labels** show whether a workflow is ready, paused, running, waiting for approval, or needs attention. ## Basic Workflow Creation 1. Click **New Workflow**. 2. Give the workflow a clear name. 3. Describe the task Row-Bot should perform. 4. Choose when it should run: manual, scheduled, or triggered when that option is available. 5. Choose delivery: app only, a channel, or another configured destination. 6. Save the workflow. 7. Run it manually once and review the result. ## Advanced Workflow Creation Advanced workflows can include richer instructions, required inputs, model/profile choices, delivery overrides, approval rules, and multi-step behavior. Keep each step observable: what information Row-Bot should gather, what it should produce, where it should save or send output, and what requires your approval. ## What Is Saved Workflow definitions, schedules, run history, delivery defaults, and status are local Row-Bot data. Results may be sent to channels only when configured and selected. ## Safety Avoid workflows that send messages, write files, start servers, or call external systems without a review point. Use approvals for actions that can affect files, accounts, channels, MCP servers, plugins, or external services. ## Troubleshooting - If a workflow does not run, check whether it is paused. - If delivery fails, check the selected channel and its Settings tab. - If a run waits for approval, decide from the thread prompt or open the Activity Center. - If results are too broad, split the workflow into smaller steps.

## Designer Studio

Route: /docs/designer/

Create and iterate on design projects, pages, assets, previews, brands, and exports.

# Designer Studio Designer Studio helps you create visual work with Row-Bot: pages, slides, mockups, landing-page drafts, branded assets, charts, image or video inserts, and exportable design projects. ## Where To Find It Open Home -> Designer to start or reopen a project. The Home tab is the launcher. Designer Studio is the full workspace for editing, previewing, reviewing, and exporting. ## End-To-End Workflow 1. Start from a prompt, template, goal, or existing project. 2. Describe the audience, tone, length, and outcome. 3. Add reference files or brand details if they matter. 4. Create the project and review the first draft. 5. Use the editor and preview to inspect each page. 6. Ask Row-Bot to revise text, layout, media, charts, or brand details. 7. Review quality, export, or share a preview when ready. ## UI Walkthrough - **Project gallery** lists recent saved projects. - **New design flow** collects the goal, template, audience, tone, references, and brand. - **Editor/canvas** shows the current page or screen. - **Page navigator** moves through pages and lets you add, delete, reorder, or rename where available. - **Control panels** expose brand, layout, import, export, share, review, and history actions. - **Preview/output** lets you inspect the user-facing result before exporting. - **Save/export** writes project state locally and creates files in the selected format. ## Brand And Assets Designer can use saved brand presets, extract brand hints from a URL, accept reference uploads, and reuse project assets. Generated images or videos may call configured media providers; local-only design edits stay in local project data. ## Troubleshooting - If a project starts empty, provide a more specific goal and audience. - If exports look wrong, preview each page before exporting. - If media generation is unavailable, check Providers and model capabilities. - If a brand extraction fails, enter colors, fonts, or notes manually.

## Developer Studio

Route: /docs/developer/

Use Row-Bot for folders, repositories, code chat, inspectors, commands, changes, and sandbox modes.

# Developer Studio Developer Studio is Row-Bot's code workspace. Use it when you want Row-Bot to understand a local folder or Git repository, discuss code, inspect files, run approved commands, propose edits, and help review changes. ## Where To Find It Open Home -> Developer. Choose an existing folder, connect a repository already on your machine, or clone a repository into a local workspace. ## End-To-End Workflow 1. Open or clone a project. 2. Confirm the workspace name, path, branch, and dirty state. 3. Ask Developer chat a code question or assign a change. 4. Review the inspector for files, detected commands, todos, context, and approvals. 5. Approve only the commands or edits you understand. 6. Run tests or checks. 7. Review the changed files before committing or exporting a patch. ## UI Walkthrough - **Open folder** connects a local project without cloning. - **Connect repository** uses a local Git checkout. - **Clone repository** creates a new checkout from a remote URL. - **Developer chat** is the conversation bound to that workspace. - **Inspector** shows workspace identity, files, command suggestions, todos, changes, and run state. - **File/context panel** helps Row-Bot and you see what code is relevant. - **Command controls** run detected or requested commands through approval policy. - **Change review** summarizes edits and lets you inspect before accepting next steps. ## Sandbox Modes Local mode lets Row-Bot operate in the selected workspace with your configured file and command permissions. Docker sandbox mode, when available, isolates command execution in a container and requires an import step before changes affect the real workspace. Docker is safer for risky commands but requires Docker setup and can differ from your local environment. For most users, start with local mode on a disposable branch. Use Docker when you want stronger isolation or are testing uncertain commands. ## Troubleshooting - If Developer tools are unavailable, open a Developer workspace first. - If commands are missing, inspect detected commands or ask Row-Bot to identify the project tooling. - If a command asks for approval, read the exact command and workspace before approving. - If Docker sandbox import is offered, review the patch before importing it into the real project.

## Knowledge

Route: /docs/knowledge/

Review and manage Row-Bot memory, documents, knowledge graph records, filters, details, and dream cycle activity.

# Knowledge Knowledge is Row-Bot's local memory and retrieval area. It includes saved memories, extracted document information, graph records, entity relationships, and background organization that can help future chats. For the relationship between thread history, memory, documents, the graph, Wiki Vault, and Dream Cycle, read [How Memory Becomes Knowledge](/docs/concepts/memory-knowledge-and-dream-cycle). ## Where To Find It Open Home -> Knowledge. Configure memory and embeddings in Settings -> Knowledge and Settings -> Documents. ## UI Walkthrough - **List or grid** shows available knowledge records. - **Filters** narrow records by type, source, status, or search text. - **Detail cards** show the exact record, source, confidence, timestamps, and related information when available. - **Edit mode** lets you correct useful information instead of deleting everything around it. - **Dream cycle controls** review or trigger background organization when enabled. - **Extraction journal links** connect Knowledge to Monitor so you can see how records were created. ## Common Workflow 1. Open Knowledge after a few useful chats or document imports. 2. Filter to the topic you care about. 3. Open a detail card. 4. Correct or remove misleading records. 5. Ask Chat to use knowledge only after you have verified important entries. ## What Is Saved Knowledge records are local data. They can be used as context in future chats when memory, document search, or knowledge retrieval is enabled. ## Troubleshooting - If Knowledge is empty, enable memory or index documents first. - If records are wrong, edit or remove them. - If retrieval feels noisy, reduce memory/search settings and review graph entries. Continue with [Wiki Vault](/docs/knowledge/wiki-vault) and [Provenance And Repair](/docs/knowledge/provenance-repair) for the file-output and recovery workflows.

## Wiki Vault

Route: /docs/knowledge/wiki-vault

Generate and maintain a local Markdown vault from reviewed Row-Bot knowledge.

# Wiki Vault Wiki Vault turns selected Knowledge entities and relationships into linked Markdown pages in a folder you control. It is an output of the local knowledge graph, not a replacement for the underlying memory and provenance records. ## Configure The Vault 1. Open **Settings -> Knowledge**. 2. Choose a vault folder that is separate from application code and important personal notes while you test. 3. Enable Wiki output only after reviewing the current Knowledge graph. 4. Run the rebuild or sync action shown in the tab. 5. Open the generated Markdown pages in your preferred editor and check links, titles, and source notes. The vault contains generated summaries and links. Correct important facts in Knowledge first, then rebuild, so the graph remains the source of truth. Avoid hand-editing generated sections unless the page clearly identifies an area intended for manual notes. ## Updates And Deletions New or changed entities can update their corresponding pages. Removed or merged records may cause generated pages or links to change on the next rebuild. Back up a vault before a large repair, migration, or rebuild if it also contains your own notes. ## Privacy The vault is local, but it is deliberately easy to open in other software or sync with a third-party folder. Treat the destination as an export boundary. Review it before placing it in cloud storage, a shared repository, or a publishing system. ## Troubleshooting - If pages are empty, verify that Knowledge contains reviewed entities and relations. - If links duplicate, run Knowledge repair before rebuilding the vault. - If a path is unavailable, choose a writable local folder and try again. - If private material appears, correct or remove its source record, rebuild, and review the destination before sharing.

## Knowledge Provenance And Repair

Route: /docs/knowledge/provenance-repair

Trace where knowledge came from, correct records, repair relations, and rebuild derived outputs safely.

# Knowledge Provenance And Repair Knowledge is useful only when you can tell where it came from. Review provenance before relying on a memory, document fact, entity, or relation for consequential work. ## Review A Record 1. Open **Home -> Knowledge** and filter to the topic. 2. Open the record detail. 3. Check its source, timestamps, type, confidence or status, and related entities. 4. Compare important claims with the original conversation or document. 5. Correct, merge, or remove the record if it is misleading. ## Repair Order Use the smallest repair that fixes the problem: 1. Correct a title, type, description, or relation. 2. Merge a duplicate entity when both records refer to the same thing. 3. Remove a bad relation without deleting sound entities. 4. Rebuild derived indexes if search still returns stale results. 5. Rebuild Wiki Vault output only after the graph is correct. Monitor's extraction and Dream Cycle journals help explain background changes. A repair should preserve useful source evidence and avoid touching unrelated memories. ## Recovery Before a large repair or migration, close Row-Bot and back up the active data directory. Restore the whole related data set together rather than mixing database files from different moments. If the app offers a built-in repair action, read its scope and completion message before manually replacing files. ## Safety Boundary Deleting a thread does not necessarily mean every derived record disappears immediately, and deleting one graph entity can affect linked output. Review the exact record and its relationships first. Never run repair tests against a personal data directory.

## Computer Use

Route: /docs/computer-use/

Set up and safely use Row-Bot's opt-in native Windows and macOS application control.

# Computer Use Computer Use is Row-Bot's provider-neutral tool for operating native Windows and macOS applications. It is separate from browser automation: use Browser for web pages and Computer Use only when the task must interact with a desktop application window. Computer Use is a beta feature. It is off by default, supports one interactive local task at a time, and is unavailable to schedules, channels, background workflows, child agents, plugins, external MCP callers, mobile clients, and headless or server sessions. ## Set It Up 1. Open **Settings -> System -> Browser & Computer Use**. 2. Expand **Computer Use (Beta)** and read the capability and privacy summary. 3. Choose **Install**. Row-Bot shows the required Cua Driver telemetry disclosure before it downloads or starts anything. 4. Choose **Continue** only if you accept the disclosure. Row-Bot downloads the pinned Cua Driver 0.7.1 asset for your platform, verifies its SHA-256, and extracts it into Row-Bot's private data directory. 5. On macOS, grant Accessibility and Screen Recording to the Row-Bot process when prompted, then choose **Recheck**. Restart the same process after changing permissions if the status asks you to. 6. Turn on **Computer Use (Beta)** after the setup card reports ready. Install, Repair, Reinstall, Remove, and system-binary controls affect only the optional driver. Row-Bot never runs the upstream installer or updater. A custom system binary is accepted only after explicit opt-in and version verification. ## Run A Native Task Ask from a normal local desktop chat and name the application and desired outcome. Row-Bot discovers applications and windows, acquires one exclusive task lease, and binds actions to the selected target window. It can launch an allowlisted application, observe that window, click, type, press keys, scroll, and drag when the current policy permits the operation. When accessibility data is insufficient, Row-Bot may send one ephemeral target-window screenshot to the Vision model configured in Settings. The live control card shows sanitized state and a shielded thumbnail; screenshot bytes are not written to chat, durable memory, replay history, logs, or tool results. ## Stop Or Take Over - **Stop** cancels queued work and releases the session. - **Take over** cancels queued mutation and pauses the lease so you can interact directly. - **Resume** requires Row-Bot to observe the target again before it can act. Window replacement, permission loss, target changes, or driver failure invalidates stale state. Row-Bot must reacquire and observe before another mutation. ## Safety Boundaries Computer Use blocks terminals, password managers, Row-Bot itself, secure desktops, elevation prompts, security settings, and attempts to handle credentials, one-time codes, CAPTCHAs, biometrics, or operating-system permission dialogs. Consequential actions use approval policy at the point of risk, and external handoff flows stay with the user. The reviewed Cua telemetry sends a stable random Cua installation ID, Cua version, operating-system name and version, architecture, CI flag, event category, and timestamp to Cua's PostHog endpoint. It excludes usernames, file paths, command or tool arguments, typed content, and screenshots. Row-Bot adds no first-party telemetry and prevents its prompts, files, memories, secrets, screenshots, tool arguments, and channel content from reaching Cua telemetry. For the exact allowlist and reviewed dependency record, see [Computer Use Beta: architecture and security decision](https://github.com/siddsachar/row-bot/blob/main/docs/COMPUTER_USE_SECURITY.md). ## Troubleshooting - If setup reports an archive or checksum error, choose **Repair** and retry on a trusted network. - If macOS reports missing permission, use the provided buttons to open Accessibility and Screen Recording settings, grant the running Row-Bot process, restart it, and recheck. - If the requested app is blocked, do not work around the policy with a terminal or generic MCP tool. Operate it manually or use a narrower supported application. - If a session is busy, stop or finish the active Computer Use task before starting another. - If the target window closes or changes, ask Row-Bot to reacquire it before resuming.

## Monitor

Route: /docs/monitor/

Inspect Row-Bot logs, journals, workflow state, channels, and background activity.

# Monitor Monitor shows what Row-Bot is doing and what recently happened. Use it when a workflow, channel, background job, knowledge extraction, dream cycle, or provider setup needs investigation. ## Where To Find It Open Home -> Monitor. ## UI Walkthrough - **System Monitor** is the top-level status area. - **Refresh** updates visible logs and state. - **Knowledge Extraction** shows extraction activity and links to the extraction journal. - **Dream Cycle** shows background organization activity and links to the dream journal. - **Channels** shows whether configured external message channels are running. - **Recent Logs** shows current app events with timestamps and severity. - **View Full Log** opens a longer log view for troubleshooting. - **Status labels** identify running, idle, disabled, warning, or failed states. ## Logs And Journals Recent logs help with immediate diagnosis. The knowledge extraction journal explains what Row-Bot extracted from conversations or documents. The dream journal explains background organization attempts. Use journals when you need a narrative of why a knowledge record or background status exists. ## Common Workflow 1. Reproduce or observe the issue. 2. Open Monitor and refresh. 3. Check status labels and recent logs. 4. Open the relevant journal. 5. Copy only non-sensitive details into a support request. ## What Is Saved Logs and journals are local Row-Bot data. They may include file names, thread names, provider names, channel names, or task summaries, so review them before sharing. ## Troubleshooting - If logs are empty, reproduce the issue and refresh. - If background work is disabled, check Settings -> Preferences and Settings -> Knowledge. - If a channel is stopped, open Settings -> Channels before restarting it.

## Android And Native Desktop

Route: /docs/mobile-native/

Pair an Android companion, use mobile Chat and Activity, and understand native-only desktop behaviour.

# Android And Native Desktop Row-Bot's mobile companion gives a paired Android device a compact view of the local app. The native desktop build adds operating-system integration such as window, tray, microphone, file-picker, and updater behaviour. Neither surface changes the approval rules of the underlying task. ## Pair An Android Device 1. On desktop, open **Settings -> System** and find Mobile Access. 2. Read the network disclosure and choose the narrowest access mode that fits your network. 3. Create a pairing invitation from the desktop app. 4. Open the shown address or QR code on the Android device while both devices can reach the same Row-Bot host. 5. Confirm the device name and access request on desktop. 6. Revoke the device from desktop settings when it is lost, replaced, or no longer trusted. Pairing credentials grant access to your local Row-Bot instance. Do not share a pairing invitation, expose the local server broadly, or use an untrusted network without understanding the tunnel or proxy in front of it. ## Native-Only Checks Some states cannot be reproduced faithfully in browser automation: OS microphone prompts, native file pickers, tray menus, updater/restart dialogs, Computer Use takeover, and physical-device network permission. The public guide documents their intent; release review must test them on the target operating system and a physical Android device. ## Troubleshooting - If the phone cannot connect, confirm the host, port, access mode, firewall, and network reachability shown on desktop. - If a token expires, pair again rather than copying cookies or local credential files. - If an approval is missing, open Activity and confirm the relevant thread is still active. - If the mobile layout opens on desktop, remove the mobile query parameter or reopen the normal local address.

## How Row-Bot Works

Route: /docs/concepts/

Understand Row-Bot's request, knowledge, agent, workflow, and extension models before configuring them.

# How Row-Bot Works These pages explain the ideas behind Row-Bot without walking through every control. Use them when you want to predict what the app will do, where data goes, why work continues in the background, or what an extension is allowed to change. - [How A Request Runs](/docs/concepts/request-lifecycle) follows a message from a thread through model context, tools, approvals, and saved results. - [How Memory Becomes Knowledge](/docs/concepts/memory-knowledge-and-dream-cycle) separates thread history, memory, documents, the Knowledge Graph, Wiki Vault, and Dream Cycle. - [How Profiles, Goals, And Agents Work](/docs/concepts/profiles-goals-and-agents) explains reusable roles, durable objectives, parent coordination, and child-agent hand-offs. - [How Background Workflows Run](/docs/concepts/background-workflows) explains schedules, run state, approvals, retries, and delivery. - [Extensions And Trust Boundaries](/docs/concepts/extensions-and-trust) compares built-in tools, Skills, Custom Tools, plugins, MCP, channels, and accounts. Each page ends with links to the settings and task guides that change the behaviour it describes.

## How A Request Runs

Route: /docs/concepts/request-lifecycle

Follow a Row-Bot request through context assembly, a selected model route, tools, approvals, and local history.

# How A Request Runs A Row-Bot request is a controlled loop, not a single message sent blindly to every connected service. 1. **A thread provides continuity.** Your message joins the selected conversation. The thread supplies recent history and any thread-specific model or profile choice. 2. **Row-Bot assembles useful context.** Depending on your settings and request, this can include profile instructions, enabled Skills, attachments, and relevant local memory or document results. It does not mean the whole local data directory is attached. 3. **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. 4. **The model may answer or ask for a tool.** Row-Bot checks that the tool exists, is enabled for the active profile or workflow, and is permitted by policy. 5. **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. 6. **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. 7. **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](/docs/configuration/models-and-providers), [Provider Settings](/docs/settings/providers), and [Model Settings](/docs/settings/models). - Control tools and approvals in [Tools, Approvals, And Terminal](/docs/chat/tools-approvals-and-terminal) and [Privacy And Safety](/docs/privacy-safety/). - Control reusable context in [Knowledge Settings](/docs/settings/knowledge), [Documents Settings](/docs/settings/documents), and [Skills Settings](/docs/settings/skills).

## How Memory Becomes Knowledge

Route: /docs/concepts/memory-knowledge-and-dream-cycle

Understand thread history, memory, documents, the Knowledge Graph, Wiki Vault, and Dream Cycle as related but distinct layers.

# How Memory Becomes Knowledge Row-Bot has several kinds of continuity. They work together, but none is a magical copy of everything the app has ever seen. | Layer | What it represents | How it is used | | --- | --- | --- | | Thread history | Messages, attachments, tool traces, approvals, and results in one conversation. | Keeps the current conversation coherent and reviewable. | | Memory | Reusable facts, preferences, summaries, and events saved or extracted for later recall. | Supplies selected relevant context to future requests when enabled. | | Documents | Files deliberately added to the document library and split into searchable content. | Finds passages related to a question without placing every document in every prompt. | | Knowledge Graph | Local entities and directed relationships with source and confidence information. | Connects related people, projects, events, facts, and sources during review and recall. | | Wiki Vault | Linked Markdown pages generated from reviewed graph material. | Makes a portable, human-browsable projection in a folder you choose. | ## From Conversation To Recall When extraction is enabled, Row-Bot can identify useful information from eligible conversations or documents and save structured records. Search combines the available lexical, vector, and graph signals to choose candidates relevant to a later request. Recall refreshes useful memories; it does not make every stored item equally likely to appear. The source record matters. A graph relation or memory should remain traceable to the conversation, document, or process that produced it. Correct the underlying Knowledge record before rebuilding derived indexes or Wiki Vault pages. ## What Dream Cycle Does Dream Cycle is idle-time knowledge maintenance. When enabled and due, it can examine the local knowledge set, merge high-confidence duplicates, refresh summaries from available source context, infer strongly supported relationships, and prune stale low-confidence inferred relations. It records a journal so you can review what happened. Dream Cycle is not an autonomous second assistant and it does not make external facts true. It should run only during the configured window while the app is idle. Inferred relationships use confidence thresholds, but important knowledge still deserves human review. ## What Wiki Vault Does Wiki Vault writes a readable view of selected graph material. The graph remains the source of truth; the vault is a generated output. If the destination is synced to a cloud drive, repository, or publishing tool, that folder becomes a separate sharing boundary. ## Configure And Review It - Review records in [Knowledge](/docs/knowledge/) and investigate changes in [Monitor](/docs/monitor/). - Configure extraction, recall, embeddings, graph maintenance, Dream Cycle, and Wiki output in [Knowledge Settings](/docs/settings/knowledge). - Configure indexed files in [Documents Settings](/docs/settings/documents). - Set up the export folder in [Wiki Vault](/docs/knowledge/wiki-vault) and correct mistakes with [Provenance And Repair](/docs/knowledge/provenance-repair). - Back up the related local data as one set using [Operations, Data, And Recovery](/docs/operations/).

## How Profiles, Goals, And Agents Work

Route: /docs/concepts/profiles-goals-and-agents

Understand reusable Agent Profiles, durable goals, parent coordination, and bounded child-agent delegation.

# How Profiles, Goals, And Agents Work Profiles, goals, and agent runs describe different parts of long-running work. - An **Agent Profile** is a reusable operating role: instructions, model policy, Skills, tools, delegation limits, and approval policy. - A **goal** is the durable objective and finish condition for a piece of work that may span several turns. - An **agent run** is one execution attempt with a prompt, model, status, result, and evidence. - A **parent agent** coordinates the objective and combines results. - A **child agent** receives a bounded subtask and returns a hand-off to its parent. ## Why Delegate Delegation is useful when independent research, inspection, or implementation can happen in parallel or needs a specialist profile. It is less useful when agents would edit the same small resource or when only one decision is needed. The parent remains responsible for deciding whether the combined evidence actually completes the goal. Child agents do not become invisible background permissions. Their runs remain linked to the parent, and a returned result is evidence rather than automatic authorisation to write, send, publish, or declare the goal complete. Tool availability and approvals still apply to the run doing the action. Delegation capacity is bounded. Each new run snapshots the application-wide work-round, nesting, per-parent concurrency, app-wide concurrency, and optional child active-time settings. When capacity is full, eligible children wait in a first-in, first-out queue rather than bypassing the limits. ## Status And Hand-Offs An active goal can accumulate progress across turns. Completion should mean the finish condition and required checks are satisfied. A block should identify a real impasse, not merely unfinished work. Stopping an agent ends that run without deleting the parent thread, goal history, or already-recorded evidence. The work-round budget is checked at model, tool, and resume boundaries so a restart cannot reset it. Repeated no-progress states are blocked and then terminated cleanly, and every terminal path writes one durable final status and reason. A useful child-agent hand-off says what was checked, what changed, what evidence was found, what remains uncertain, and whether any consequential action still needs the parent or user. ## Configure And Use It - Create and select roles with [Profiles, Goals, And Agents](/docs/profiles-goals-agents/). - Choose a profile in a workflow with [Workflows](/docs/guides/workflows). - Control the models behind runs in [Models And Providers](/docs/configuration/models-and-providers). - Review waiting work and failures in [Mobile And Native Surfaces](/docs/mobile-native/) or [Monitor](/docs/monitor/).

## How Background Workflows Run

Route: /docs/concepts/background-workflows

Understand saved workflow definitions, schedules, isolated runs, approvals, retries, and delivery semantics.

# How Background Workflows Run A workflow is a saved task definition. A run is one attempt to execute it. Keeping those separate lets Row-Bot preserve history when you edit the next schedule or retry a failed attempt. 1. **A trigger starts a run.** This can be a manual click, a recurring schedule, a one-time time, or another supported trigger. 2. **The run resolves its policy.** Row-Bot chooses the workflow's Agent Profile, model override, tools, Skills, steps, and approval mode. 3. **The run gets its own state.** Status, progress, step output, logs, and any persistent thread link are recorded so the scheduler can recover cleanly. 4. **Approval can pause the run.** A background action that needs a decision becomes a pending approval instead of silently continuing. Approving resumes that action; rejecting or expiring it leaves a visible run outcome. 5. **Completion and delivery are recorded separately.** A useful result can complete even if an external channel delivery fails, so the app can show the result and the delivery problem honestly. ## Delivery Defaults The web app always receives run status. External channels are an additional destination. - **Inherit defaults** means the workflow uses the current workflow-level external channel selection. - **An explicit empty selection** means web app only, even when a global external default exists. - **An explicit channel selection** targets those configured running channels. This distinction prevents a workflow that was deliberately set to app-only from beginning to send externally after someone changes the global default. ## Failure And Retry A failed run remains evidence; retrying creates another attempt rather than rewriting history. Fix the underlying provider, model, tool, approval, input, or delivery problem first. For multi-step work, keep steps narrow enough that the status identifies where the run stopped. Scheduled work can outlive the screen where it was created, but it cannot outlive the local Row-Bot process indefinitely. Pausing a workflow prevents future schedule starts; stopping one active run does not necessarily change the saved schedule. ## Configure And Operate It - Create schedules, profiles, approvals, steps, and delivery in [Workflows](/docs/guides/workflows). - Configure external destinations in [Channels](/docs/integrations/channels) and [Channel Settings](/docs/settings/channels). - Review live status in [Monitor](/docs/monitor/) and mobile Activity in [Mobile And Native Surfaces](/docs/mobile-native/). - Back up workflow definitions and history with [Operations, Data, And Recovery](/docs/operations/).

## Extensions And Trust Boundaries

Route: /docs/concepts/extensions-and-trust

Compare Row-Bot tools, Skills, Custom Tools, plugins, MCP servers, channels, and accounts by what they add and where they run.

# Extensions And Trust Boundaries Row-Bot can learn a procedure, gain a tool, load code, connect a server, or authorise an account. Those are different changes and deserve different review. | Capability | What it adds | Main trust question | | --- | --- | --- | | Built-in tool | A maintained capability shipped with Row-Bot. | Is it enabled for this profile, and does this action need approval? | | Skill | Instructions, examples, and supporting files that shape behaviour. | Do the instructions match your intent and avoid unexpected data or tool use? | | Custom Tool | Reviewed local code or a command exposed as a reusable tool. | What code runs, in which workspace, with which dependencies and command class? | | Plugin | A packaged extension that can add code, tools, Skills, channels, configuration, or UI. | Do you trust its publisher, source, permissions, dependencies, and update path? | | MCP server | Tools supplied by a separate local process or remote service. | What can the server access, where does it run, and which of its tools are enabled? | | Channel | A bridge for incoming messages or outgoing results. | Who can contact it, which conversation receives replies, and may workflows deliver there? | | Account | Authorisation for a service such as GitHub, Google, or X. | Which service scopes and account data become available to enabled tools? | ## Instructions Are Not Permissions A Skill or profile can tell the model when to use a capability, but it does not create credentials or bypass Row-Bot's tool and approval policy. Conversely, installing a plugin or MCP server can add real executable capability even when no Skill mentions it. Review both the guidance layer and the execution layer. ## Local Does Not Always Mean Harmless A local plugin, command, or MCP process can still read files, start programs, or use locally stored credentials. A remote server or account can send data outside the app even if its configuration is stored locally. Use narrow workspaces, least-privilege accounts, disabled-by-default imports, and fictional test data. Third-party dependency telemetry is not Row-Bot telemetry. Review dependency behaviour before installation and do not expose prompts, files, memories, secrets, screenshots, tool arguments, or channel content unless that transfer is the feature you intentionally selected. ## Browse And Configure Extensions - Compare extension types and browse screenshots in [Extend Row-Bot](/docs/extending/). - Browse and review Skills in [Skills Hub](/docs/skills/) and [Skills Settings](/docs/settings/skills). - Install and control packaged code in [Plugins](/docs/integrations/plugins) and [Plugin Settings](/docs/settings/plugins). - Browse, add, test, and enable servers in [MCP](/docs/integrations/mcp) and [MCP Settings](/docs/settings/mcp). - Configure external messaging in [Channels](/docs/integrations/channels) and service authorisation in [Accounts And Authorisation](/docs/integrations/accounts).

## Settings

Route: /docs/settings/

Understand every Row-Bot Settings tab and what each configuration area changes.

# Settings Settings is Row-Bot's configuration center. It affects model providers, model choices, documents, search, skills, system access, accounts, utilities, tracker, knowledge, Buddy, voice, channels, MCP, plugins, and preferences. ## How Settings Is Organized - **Providers** connects local, hosted, subscription, and custom model providers. - **Models** chooses defaults and pinned Quick Choices. - **Documents** manages uploads, extraction, embeddings, and vector rebuilds. - **Search** controls web research, local retrieval, and browser automation. - **Skills** manages Smart Skills and Skills Hub access. - **System** configures local access, workspace boundaries, window behavior, tunnels, logs, and diagnostics. - **Accounts** connects account-level integrations. - **Utilities** manages built-in helper tools. - **Tracker** configures structured personal logs. - **Knowledge** manages memory, graph, embeddings, and wiki export. - **Buddy** controls the visual companion. - **Voice** configures Talk, Dictate, read-aloud, models, devices, and diagnostics. - **Channels** configures external messaging connectors. - **MCP** manages external MCP tool servers. - **Plugins** manages installed plugins and Custom Tool promotion. - **Preferences** changes identity, launch behavior, background intelligence, updates, and migration. ## A Good Setup Order 1. Providers 2. Models 3. Documents and Search 4. Skills 5. System access 6. Integrations: Accounts, Channels, MCP, Plugins 7. Voice and Buddy 8. Preferences ## Safety Notes Credentials belong in Providers, Accounts, Channels, MCP, or plugin-specific settings, not in chat messages. Enable only the tools and integrations you intend to use. Review approvals before actions that write files, run commands, use accounts, contact external services, or send messages.

## Settings: Providers

Route: /docs/settings/providers

Connect local, hosted, subscription, and custom model providers.

# Settings: Providers Providers are the model services Row-Bot can call. This tab answers whether each provider is connected, what kind of credential it uses, and whether Row-Bot has enough information to use it for chat, tools, Designer, Developer, voice, or embeddings. ## Where To Find It Open **Settings**, then choose **Providers** from the left tab list. ## Controls - Connection Status summarizes how many providers are connected, local, API-based, subscription-based, or media-capable. - Local providers show runtimes such as Ollama. Refresh checks what the local service currently exposes. - Subscription accounts show sign-in based providers such as ChatGPT / Codex or Claude Subscription. Use connect, reconnect, test, and refresh actions from the row. - API providers show services that need an API key or compatible endpoint. Their credential buttons open the setup flow for that provider. - Custom endpoint providers let advanced users point Row-Bot at OpenAI-compatible servers such as LM Studio, vLLM, llama.cpp, LocalAI, LiteLLM, or SGLang. - Runtime tests check whether a provider can handle the kind of requests Row-Bot needs. A failed test keeps the provider visible but may stop Row-Bot from offering it for agent work. ## Common Workflow 1. Pick one provider path first: local Ollama for private local runs, a subscription account if you already use one, or an API provider if you prefer hosted models. 2. Add credentials or sign in only through the provider row you intend to use. 3. Refresh the provider so Row-Bot can discover available models. 4. Open Settings -> Models to pin the models you want in the chat picker. ## What Is Saved Provider connection state is global to the local Row-Bot app. Secrets are stored in the operating system key store when available; Row-Bot settings keep masked status and catalog metadata. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#providers-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a provider is connected but models do not appear, refresh Providers, then refresh Models. - If a runtime test fails, read the row message before changing credentials; the model may be chat-capable but not tool-capable. - If local Ollama is missing, start Ollama and make sure at least one model is installed.

## Settings: Models

Route: /docs/settings/models

Choose defaults, pin Quick Choices, review model catalogs, and set Agent runtime limits.

# Settings: Models Models are the specific brains exposed by a provider. The Models tab decides which model Row-Bot should use by default and which choices appear quickly in chat and specialist surfaces. ## Where To Find It Open **Settings**, then choose **Models** from the left tab list. ## Controls - Default model controls choose what new chats use when a thread has no override. - Quick Choices are pinned models shown in the chat picker for fast switching. - Catalog refresh asks connected providers and local runtimes what models are available now. - Compatibility labels separate ordinary chat models from tool-capable, vision-capable, reasoning, embedding, voice, or media models. - Provider filters and search help find a specific model when many are available. - Warnings explain when a model is visible but not recommended for tool-heavy Agent Mode. - Agent runtime and delegation controls set work rounds, nesting depth, per-parent and app-wide child capacity, and an optional active-time limit for new runs. ## Common Workflow 1. Refresh the catalog after connecting a provider. 2. Pin one everyday chat model and one stronger tool-capable model. 3. Use provider-qualified names when two providers expose models with similar names. 4. Return to Chat and pick the pinned model from the model picker. 5. Keep the recommended Agent runtime limits unless you have a measured reason to change them; active runs retain the snapshot they started with. ## What Is Saved Default and pinned models are global preferences. A thread can still carry its own model override when you select a model inside that thread. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#models-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If the picker is empty, connect a provider first. - If a model is missing, refresh the catalog and check whether the provider is disabled. - If a small local model fails before answering, choose a larger context window or a more capable model.

## Settings: Knowledge

Route: /docs/settings/knowledge

Configure memory, graph review, embeddings, document knowledge, and wiki export.

# Settings: Knowledge Knowledge settings decide how Row-Bot stores useful information, retrieves it later, and organizes it into a local knowledge graph. This affects what Row-Bot can remember between conversations. ## Where To Find It Open **Settings**, then choose **Knowledge** from the left tab list. ## Controls - Memory controls decide whether Row-Bot can save and recall useful facts. - Embedding controls affect how memories and documents become searchable. - Graph review controls decide how extracted entities and relationships are handled. - Dream cycle options control background organization when that feature is enabled. - Wiki export creates local markdown-style views of selected knowledge records. ## Common Workflow 1. Enable memory only if you want Row-Bot to remember useful details. 2. Set embeddings before indexing a large document or memory collection. 3. Use the Knowledge Home tab to review and correct important entries. 4. Export a wiki when you want a readable local snapshot outside the app. ## What Is Saved Knowledge records live in local Row-Bot data. They can be sent to a model provider only as relevant prompt context when you ask Row-Bot to use them. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#knowledge-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If recall feels stale, refresh vectors or review extraction journals. - If Row-Bot remembers something wrong, edit or remove the knowledge entry. - If background organization is noisy, reduce or disable dream cycle behavior.

## Settings: Buddy

Route: /docs/settings/buddy

Configure Row-Bot's companion behavior, visibility, look, motion, and generated looks.

# Settings: Buddy Buddy is Row-Bot's visual companion. It can live in the sidebar, float in the workspace, or open as a desktop overlay. Buddy reflects app state but does not change model behavior by itself. ## Where To Find It Open **Settings**, then choose **Buddy** from the left tab list. ## Controls - Enable switches decide whether Buddy appears in the sidebar, workspace, or desktop overlay. - Open and close overlay buttons control the separate desktop overlay window. - Companion personality changes the tone of Buddy status cues. - Bubble style changes how visual status appears. - Look cards choose a bundled or custom Buddy appearance. - Concept and style notes describe a custom look when you use Generate full Buddy. - Use still only keeps current art without animated motion. - Retry motion rebuilds motion for an existing look. ## Common Workflow 1. Start with the bundled look and sidebar mode. 2. Enable desktop overlay only if you want Buddy outside the main Row-Bot window. 3. Generate a custom look after providers and media models are ready. 4. Use still only if motion generation is unavailable or distracting. ## What Is Saved Buddy preferences and custom Buddy assets are local app data. Generating a custom look may call a configured media provider depending on your setup. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#buddy-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If Buddy does not appear, check the enable switches and refresh the app. - If the overlay is stuck, use Close overlay, then Open overlay again. - If custom generation fails, check provider readiness and try still-only mode.

## Settings: Voice

Route: /docs/settings/voice

Configure dictation, realtime talk, read-aloud, voice models, devices, and diagnostics.

# Settings: Voice Voice gives Row-Bot microphone input and optional spoken output. Dictate turns speech into text for the composer. Talk is a conversation mode. Realtime voice uses a low-latency provider path when configured. ## Where To Find It Open **Settings**, then choose **Voice** from the left tab list. ## Controls - Talk settings decide whether spoken input submits directly to Row-Bot. - Dictate settings decide whether speech is inserted into the composer for review before sending. - Read-aloud settings control spoken assistant responses. - Local voice controls use local speech components where available. - Realtime voice controls use provider-backed low-latency voice models. - Device controls select microphone and output devices. - Voice Models shows runtime defaults and provider voice models. - Diagnostics checks local audio and provider readiness. ## Common Workflow 1. Use Dictate first if you want to review text before sending. 2. Use Talk when you want hands-light conversation and are comfortable with immediate submission. 3. Choose local voice for privacy and offline-style behavior when supported. 4. Choose realtime voice when latency matters and you accept provider requirements, cost, and internet use. ## What Is Saved Voice preferences are global. Transcribed text belongs to the active thread once submitted. Provider-backed voice can send audio or transcript data to the selected provider. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#voice-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If the microphone is silent, check the selected input device and browser/app permissions. - If realtime voice is unavailable, configure a compatible provider in Providers. - If Talk submits too quickly, use Dictate mode instead.

## Settings: System

Route: /docs/settings/system

Configure local access, workspace paths, browser and Computer Use behavior, tunnels, logs, and updates.

# Settings: System System settings describe what the local app may access and how it runs on your machine. This is where you adjust the app window, workspace boundaries, shell behavior, browser automation, opt-in native Computer Use, tunnels, and diagnostics. ## Where To Find It Open **Settings**, then choose **System** from the left tab list. ## Controls - Workspace and filesystem controls define where Row-Bot may read or write when tools need local files. - Shell and command controls affect whether command-running tools are available and how approvals apply. - Browser controls affect page-reading and browser automation features. - Computer Use controls keep native application automation separate, off by default, and gated by platform readiness, telemetry disclosure, and a verified optional runtime. - Window mode chooses whether Row-Bot opens in its own app window, the system browser, or asks at launch. - Tunnel settings are for external callback use cases such as channels that need a public webhook URL. - Log and diagnostic controls help support troubleshooting without changing your model setup. ## Common Workflow 1. Keep workspace access narrow for everyday use. 2. Enable shell or browser automation only when you intend to use those tools. 3. Enable Computer Use only on an interactive Windows or macOS desktop after reviewing its separate setup and safety guide. 4. Use tunnels only for channels or integrations that explicitly require inbound webhooks. 5. Collect logs from this tab when troubleshooting startup or provider issues. ## What Is Saved System settings are global for the local app. Workspace files are not uploaded to Row-Bot; external providers may still receive content when a model or tool request sends it. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#system-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If Row-Bot cannot read a file, check whether it is inside the allowed workspace. - If Computer Use is unavailable, open its setup card and follow the reported runtime or operating-system permission recovery step. - If a tunnel URL is unavailable, check the tunnel provider credentials and whether the tunnel is running. - If the app opens in the wrong place, change Window mode and restart Row-Bot.

## Settings: Tracker

Route: /docs/settings/tracker

Configure recurring activity, habit, symptom, and health tracking surfaces.

# Settings: Tracker Tracker is for structured personal logs such as recurring activities, habits, symptoms, or health events. It gives Row-Bot a more organized way to store and review repeated observations than free-form chat alone. ## Where To Find It Open **Settings**, then choose **Tracker** from the left tab list. ## Controls - Category controls decide what kinds of events can be logged. - View and chart options change how tracker history is summarized. - Import or cleanup actions manage existing tracker data. - Privacy-oriented status text explains that tracker records stay in local app data unless you ask a provider or channel to use them. ## Common Workflow 1. Choose the categories you actually want to track. 2. Log events consistently from Chat or tracker-aware workflows. 3. Review trends in the tracker view before asking Row-Bot to summarize them. 4. Remove categories you no longer use to keep prompts focused. ## What Is Saved Tracker data is local Row-Bot data. It can influence answers only when Row-Bot is allowed to retrieve or summarize it. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#tracker-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a chart is empty, confirm there are saved events in that category. - If a summary seems wrong, inspect the raw tracker entries first. - If privacy matters, do not include tracker details in prompts sent to hosted providers.

## Settings: Documents

Route: /docs/settings/documents

Manage document ingestion, extraction, and vector indexing.

# Settings: Documents Documents let Row-Bot search files you add to its local document library. This is different from attaching a file to one chat: indexed documents become reusable context for future questions. ## Where To Find It Open **Settings**, then choose **Documents** from the left tab list. ## Controls - Upload documents adds files to Row-Bot-managed storage for indexing. - Embedding provider and model controls choose how document chunks become searchable vectors. - Dimension override is for advanced embedding models that need a specific vector size. - Batch size controls how much indexing work happens at once. - Auto-unload local embedding resources releases local model memory after heavy document work. - Indexed Documents lists what Row-Bot has processed and whether each item is ready. - Rebuild document vectors repeats indexing when you change embedding settings. - Rebuild memory vectors refreshes memory search with the current embedding settings. ## Common Workflow 1. Choose an embedding provider before adding a large document library. 2. Upload a small test document and wait until it is indexed. 3. Ask Chat a question that should require the document. 4. Rebuild vectors only when you change embedding model settings or suspect stale search results. ## What Is Saved Uploaded files, extracted text, and vectors are stored in the local Row-Bot data directory. The active chat only sees relevant results when document search is enabled. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#documents-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If search misses obvious content, rebuild vectors and check the embedding provider. - If local indexing is slow, lower batch size or enable auto-unload. - If a document contains private material, remove it from the document library before sharing screenshots or logs.

## Settings: Search

Route: /docs/settings/search

Configure web research, local retrieval, browser automation, and search tools.

# Settings: Search Search controls what information Row-Bot can retrieve beyond the current conversation. Some search is local, such as document and memory retrieval; other search can contact external services or automate a browser. ## Where To Find It Open **Settings**, then choose **Search** from the left tab list. ## Controls - Web search provider choices decide whether Row-Bot can search the internet and which backend it uses. - Browser automation controls decide whether Row-Bot can open pages, inspect them, and interact with them when asked. - Knowledge and document search toggles decide whether local memory and document records can be considered during a response. - Result limits and ranking controls keep search focused when a query could return too much context. - Provider health indicators show whether the selected search path is available. ## Common Workflow 1. Leave web search off if you want local-only work. 2. Enable document and memory search when you want Row-Bot to use your local knowledge. 3. Enable browser automation only when you want Row-Bot to read or operate pages for you. 4. Review approval prompts before actions that submit forms, change state, or use account data. ## What Is Saved Search settings are global defaults. Individual prompts still matter: Row-Bot should only use external research when the request calls for it and the tools are enabled. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#search-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If Row-Bot cannot browse, check browser automation readiness and approvals. - If web results are stale or absent, check the selected search provider. - If local retrieval feels noisy, reduce result limits or disable memory search for the task.

## Settings: Skills

Route: /docs/settings/skills

Enable, disable, pin, browse, and review Smart Skills.

# Settings: Skills Skills are instruction packs that teach Row-Bot how to handle a type of work. They do not run by themselves; they shape how Row-Bot plans, uses tools, and explains a task. ## Where To Find It Open **Settings**, then choose **Skills** from the left tab list. ## Controls - Enable and disable controls decide whether Row-Bot may use a skill. - Pinning keeps useful skills easy to find and can make them more likely to be suggested. - Browse Skills opens Skills Hub for installed, bundled, local, and marketplace-style sources. - Skill details show purpose, source, status, and whether the skill is safe to activate. - Search and filters help find skills by task, source, or installed state. ## Common Workflow 1. Browse or search for a skill that matches the work. 2. Open the detail view before enabling unfamiliar skills. 3. Enable the skill, then start a chat or workflow that names the task. 4. Disable skills you no longer want Row-Bot to consider. ## What Is Saved Skill enablement and pins are local Row-Bot preferences. Some skills may also be selected at the thread level when a task needs them. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#skills-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If Row-Bot ignores a skill, check that it is enabled and relevant to the prompt. - If a skill came from outside the app, review its instructions before enabling it. - If skills make responses too specialized, unpin or disable the extras.

## Settings: Accounts

Route: /docs/settings/accounts

Connect account-level integrations used by tools, setup flows, and channels.

# Settings: Accounts Accounts are service logins Row-Bot can use for tools such as email, calendar, or provider-specific subscription flows. They are separate from ordinary API keys and separate from Row-Bot itself, which does not require a Row-Bot account. ## Where To Find It Open **Settings**, then choose **Accounts** from the left tab list. ## Controls - Connection cards show whether an account is connected, disconnected, or needs attention. - Sign in and reconnect buttons start the provider's account flow. - Disconnect removes Row-Bot's local access to that account. - Status messages explain what a connected account enables. ## Common Workflow 1. Connect only the accounts needed for the tasks you plan to run. 2. Finish the provider sign-in flow in the browser when prompted. 3. Return to Row-Bot and confirm the account shows connected. 4. Review tools and approvals before asking Row-Bot to act through that account. ## What Is Saved Account tokens are stored in the operating system key store when available. Row-Bot keeps local metadata so it can show connection status. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#accounts-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If sign-in loops, disconnect and reconnect the account. - If an account tool is unavailable, confirm the account is connected and the related tool is enabled. - If secure storage is unavailable, you may need to sign in again after restart.

## Settings: Channels

Route: /docs/settings/channels

Configure Telegram, WhatsApp, Discord, Slack, SMS, delivery, and health checks.

# Settings: Channels Channels let Row-Bot receive or send messages through external apps. Use them when you want Row-Bot available outside the desktop window or when workflows should deliver results somewhere specific. ## Where To Find It Open **Settings**, then choose **Channels** from the left tab list. ## Controls - Each channel expands into credential fields, status, and controls. - Save stores that channel's settings. - Start and Stop control the channel runtime. - Tunnel settings connect the channel to an externally reachable webhook when required. - DM Pairing Code helps approve a user before private-message access is allowed. - Paired Users shows who is approved and allows revocation. - Setup Guide explains provider-specific prerequisites. ## Common Workflow 1. Configure tunnel credentials in System if the channel needs a webhook. 2. Add the channel's required token, URL, or account details. 3. Save, then Start the channel. 4. Pair or approve users before trusting inbound private messages. 5. Use workflow delivery defaults to decide where automated results go. ## What Is Saved Channel settings are global. Messages sent through a channel leave the local app and follow that platform's rules. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#channels-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a channel will not start, check required fields and tunnel status. - If messages do not arrive, verify webhook URLs and platform permissions. - If a user should no longer have access, revoke them from Paired Users.

## Settings: Utilities

Route: /docs/settings/utilities

Configure built-in helper tools and productivity utilities.

# Settings: Utilities Utilities are smaller helper tools that support everyday work: calculations, file helpers, media helpers, formatting aids, or local integrations. They are useful when Chat needs a precise operation instead of a pure model answer. ## Where To Find It Open **Settings**, then choose **Utilities** from the left tab list. ## Controls - Tool toggles decide which helper utilities Row-Bot may use. - Configuration fields set defaults such as output locations or preferred formats. - Status labels show whether a utility is ready or needs additional setup. - Test or refresh actions confirm that an optional dependency is working. ## Common Workflow 1. Enable utilities that match your normal tasks. 2. Leave unfamiliar action tools disabled until you understand what they can change. 3. Use approval mode to review file writes, shell actions, or external calls triggered by utilities. ## What Is Saved Utility settings are global. Tool results are shown in the active conversation and may also create files when the approved tool does so. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#utilities-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a utility does not appear in Chat, confirm it is enabled. - If a utility needs a dependency, follow its status message before retrying. - If an output file is missing, check the allowed workspace and approval history.

## Settings: MCP

Route: /docs/settings/mcp

Add, test, import, browse, enable, and troubleshoot external MCP servers.

# Settings: MCP MCP, the Model Context Protocol, lets Row-Bot use tools provided by another local or remote server. Treat MCP servers like extensions: only connect servers you trust and understand. ## Where To Find It Open **Settings**, then choose **MCP** from the left tab list. ## Controls - Enable MCP is the global on/off switch for external MCP tools. - Add Server opens fields for name, transport, command, arguments, or URL. - Import Config accepts a server configuration from another source. - Browse MCP Servers searches directories for server candidates. - Diagnostics opens a health view for troubleshooting. - Per-server enablement decides whether a configured server can provide tools. - Test checks a server before you rely on it. - Edit, refresh, and delete manage saved server definitions. - Approval and advanced options decide how MCP tools interact with Row-Bot's safety policy. ## Common Workflow 1. Leave MCP disabled until at least one trusted server is configured. 2. Add or import a server, then save it disabled first if you are unsure. 3. Test the server and inspect the available tools. 4. Enable the server only when you are comfortable with what those tools can access. ## What Is Saved MCP server definitions are local settings. A server may still access files, accounts, or networks according to its own implementation, so review its command or URL. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#mcp-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a server test fails, check command, arguments, URL, and local dependencies. - If tools do not appear in Chat, confirm the global and server toggles are both enabled. - If a tool asks for risky access, reject the approval and inspect the server config.

## Settings: Plugins

Route: /docs/settings/plugins

Manage installed plugins, marketplace installs, configuration, and promoted Custom Tools.

# Settings: Plugins Plugins add local bundles of tools, skills, apps, or integrations. They can make Row-Bot more capable, but they should be treated as code that runs with local app permissions. ## Where To Find It Open **Settings**, then choose **Plugins** from the left tab list. ## Controls - Installed plugin cards show version, status, and available actions. - Enable and disable controls decide whether plugin capabilities are active. - Configure opens plugin-specific settings when provided. - Update and remove actions manage local plugin installations. - Marketplace opens discovery and install previews. - Custom Tools promotion turns reviewed local tools into reusable plugin-like capabilities. ## Common Workflow 1. Install plugins only from sources you trust. 2. Read the plugin description and requested fields before enabling it. 3. Configure required settings, then test with a low-risk prompt. 4. Disable or remove plugins you no longer use. ## What Is Saved Installed plugins and plugin settings are local files. Plugin secrets should use secret storage when the plugin supports it. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#plugins-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If a plugin does not load, check its manifest and dependency messages. - If plugin tools do not appear, confirm the plugin is enabled and restart if instructed. - If a plugin behaves unexpectedly, disable it first, then inspect its configuration.

## Settings: Preferences

Route: /docs/settings/preferences

Customize assistant identity, launch behavior, background intelligence, updates, and migration.

# Settings: Preferences Preferences are personal choices for how Row-Bot should address you, how it should behave at launch, and which background features should be active. ## Where To Find It Open **Settings**, then choose **Preferences** from the left tab list. ## Controls - Name helps Row-Bot address you naturally. - Personality changes the assistant's default tone. - Launch and window preferences decide how the app opens. - Background intelligence controls affect optional automatic review or organization features. - Dream cycle timing controls when background organization may run. - Update controls decide how Row-Bot checks or reports available versions. - Migration helpers support users moving from earlier app data. ## Common Workflow 1. Set your name and preferred assistant tone first. 2. Choose a launch mode that fits how you use the desktop app. 3. Enable background features only when you want Row-Bot organizing or reviewing local data outside direct chat turns. 4. Use migration helpers only when moving from an older installation or renamed data set. ## What Is Saved Preferences are global local settings. They affect new chats and app behavior, while existing threads can still have their own model, profile, or approval choices. ## Privacy And Safety Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere. ## Control-Level Reference The [generated Settings Controls reference](/docs/reference/generated/settings-controls#preferences-controls) lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations. ## Troubleshooting - If the app opens unexpectedly, adjust launch preferences and restart. - If background activity appears in Monitor, review Preferences and Knowledge settings. - If migration looks incomplete, do not delete old data until you confirm the new app has what you need.

## Extend Row-Bot

Route: /docs/extending/

Choose between built-in tools, Skills, Custom Tools, plugins, MCP servers, channels, and accounts.

# Extend Row-Bot Start with the narrowest extension type that can solve the task. Every extension adds capabilities; some also add code, dependencies, network access, credentials, or external side effects. For the conceptual differences between tools, Skills, plugins, MCP, channels, and accounts, read [Extensions And Trust Boundaries](/docs/concepts/extensions-and-trust). | Extension | Use It For | Review Boundary | | --- | --- | --- | | Built-in tool | A capability already shipped and maintained with Row-Bot. | Enable only the tools a profile needs; consequential operations still use approval policy. | | Skill | Reusable instructions and workflow knowledge. | Read the full skill and bundled files before enabling or pinning it. | | Custom Tool | A reviewed local command or repo-specific helper created in Developer Studio. | Inspect its source, command classification, dependencies, and workspace scope. | | Plugin | A packaged bundle that can provide tools, skills, channels, MCP configuration, or UI. | Review manifest, source, permissions, dependencies, and update path before enabling. | | MCP server | Tools exposed by an external local or remote process. | Add disabled, inspect overlap and risk labels, test, then enable only trusted tools. | | Channel | A messaging adapter for receiving or delivering work. | Verify account, recipients, pairing, tunnel, and delivery defaults before starting. | | Account | Authorisation for GitHub, Google, X, or another service used by tools. | Review requested scopes and disconnect unused accounts. | ## Safe Evaluation Sequence 1. Read the extension description and source. 2. Check requested permissions, credentials, network destinations, commands, and install steps. 3. Install into the local data directory only from a source you trust. 4. Keep it disabled while you inspect configuration and provided capabilities. 5. Test with fictional data and a non-consequential task. 6. Enable the minimum capabilities and keep approval mode at **Ask** until behaviour is familiar. 7. Disable or remove extensions that are no longer maintained or needed. Third-party dependency telemetry is not Row-Bot telemetry. Review and accept any dependency behaviour before installation, and never allow it to receive Row-Bot prompts, files, memories, secrets, screenshots, tool arguments, or channel content unless that transfer is the explicit feature you chose.

## Accounts And Authorisation

Route: /docs/integrations/accounts

Connect and disconnect external accounts while keeping scopes, tokens, and data flow understandable.

# Accounts And Authorisation Accounts let selected tools act through services such as GitHub, Google, or X. A model provider account supplies models; an integration account supplies service access. They are configured separately. ## Connect Safely 1. Open **Settings -> Accounts**. 2. Choose the service and read the status and requested purpose. 3. Prefer the supported OAuth or local CLI flow rather than pasting broad tokens. 4. Verify the service, account, and scopes in the external authorisation page. 5. Return to Row-Bot and refresh status. 6. Test a read-only action before approving writes, posts, email, calendar, or repository changes. ## Tokens And Scopes Secrets use the configured operating-system secret store when available. Settings show status, not the secret value. A service may still retain its own authorisation grant until you revoke it there. Use the narrowest scopes that support the feature and disconnect access you no longer use. ## Troubleshooting - Confirm the system browser returned to the same Row-Bot instance that started the flow. - For GitHub CLI, refresh CLI authorisation after signing in or changing accounts. - If a callback fails, repeat the supported flow instead of copying browser storage. - If an action is denied after connection, review both the service scopes and the Row-Bot approval policy.

## Channels

Route: /docs/integrations/channels

Connect Row-Bot to messaging channels, delivery defaults, pairing, tunnels, and safe external behavior.

# Channels Channels connect Row-Bot to external messaging platforms such as Telegram, WhatsApp, Discord, Slack, and SMS-style providers when configured. Use channels when you want to message Row-Bot outside the desktop app or send workflow results somewhere specific. ## Setup Workflow 1. Open Settings -> Channels. 2. Expand the channel you want. 3. Add the required token, URL, phone/account detail, or provider-specific field. 4. Configure a tunnel in Settings -> System if the channel requires an inbound webhook. 5. Save the channel. 6. Start the channel. 7. Pair or approve users before trusting private messages. 8. Test with a low-risk message. ## Controls - **Save** stores channel settings. - **Start** begins the channel runtime. - **Stop** shuts the channel runtime down. - **Tunnel controls** connect a channel to a public webhook URL when needed. - **DM Pairing Code** approves a user before private-message access. - **Paired Users** lists approved users and lets you revoke access. - **Setup Guide** explains platform-specific prerequisites. ## Safety Messages sent through a channel leave the local app. Do not enable a channel until you understand who can message it, what Row-Bot can send back, and whether workflows may deliver results there. When work starts from a channel and a child agent asks for approval, Row-Bot sends the approval back to that parent channel conversation when the channel supports approval messages. The same approval remains visible in the desktop parent thread and Activity Center. ## Troubleshooting - If a channel cannot start, check required fields and tunnel state. - If inbound messages fail, verify webhook URLs and platform permissions. - If the wrong person has access, revoke them from Paired Users.

## Skills Hub

Route: /docs/skills/

Browse, enable, pin, create, edit, and troubleshoot Row-Bot skills.

# Skills Hub Skills are instruction packs that teach Row-Bot how to approach a category of work. Skills Hub is where you browse installed skills, inspect details, enable or disable them, pin useful ones, and create or edit local skills. ## UI Walkthrough - **Browse/search** finds bundled, installed, local, and external-source skills. - **Filters** narrow by source, installed state, or task type. - **Skill detail** explains purpose, instructions, source, and status. - **Enable/disable** decides whether Row-Bot may use the skill. - **Pin** keeps an important skill easy to reach. - **Create/edit** lets you maintain a local skill for your own workflow. ## Creating A Skill 1. Decide what task the skill should help with. 2. Write concise instructions, examples, and boundaries. 3. Include when the skill should and should not be used. 4. Save it locally. 5. Enable it and test with a small prompt. 6. Revise if Row-Bot overuses or misunderstands it. ## What Skills Change Skills shape Row-Bot's behavior; they do not automatically grant credentials or bypass approvals. A skill can make Row-Bot more consistent for a task, but tools still need to be enabled and approved where appropriate. ## Troubleshooting - If a skill is not used, make your prompt match its purpose and confirm it is enabled. - If a skill is too aggressive, disable or rewrite it with clearer boundaries. - If an external skill is unfamiliar, inspect it before enabling.

## Plugins

Route: /docs/integrations/plugins

Install, enable, configure, update, remove, and troubleshoot Row-Bot plugins.

# Plugins Plugins add optional capabilities to Row-Bot: tools, skills, apps, settings, and integration surfaces. Install them only from sources you trust, because they can run code inside the local app environment. ## Setup Workflow 1. Open Settings -> Plugins. 2. Review installed plugins and marketplace options. 3. Read the plugin description and requested configuration. 4. Install or enable the plugin. 5. Configure required fields. 6. Test with a low-risk prompt. 7. Disable, update, or remove the plugin when needed. ## Controls - **Installed plugin cards** show version and status. - **Enable/disable** controls whether plugin capabilities are active. - **Configure** opens plugin-specific settings. - **Update/remove** manage the local installation. - **Marketplace** opens plugin discovery and install previews. - **Custom Tools** can be promoted after review so they behave like reusable app capabilities. ## Safety Plugins can add tools that read files, call services, or create outputs. Keep approval mode active for risky actions and disable plugins you do not actively use. ## Troubleshooting - If a plugin does not load, inspect its manifest and dependency message. - If plugin tools are missing, confirm the plugin is enabled. - If a plugin causes errors, disable it, restart Row-Bot if needed, then review configuration.

## MCP

Route: /docs/integrations/mcp

Configure external MCP servers, test tool availability, and manage MCP safety.

# MCP MCP lets Row-Bot use tools exposed by external Model Context Protocol servers. An MCP server can be local or remote, simple or powerful. Treat it like an extension with its own access and trust boundary. ## Setup Workflow 1. Open Settings -> MCP. 2. Leave Enable MCP off until a trusted server is configured. 3. Add, import, or browse for a server. 4. Review the command, arguments, URL, transport, and expected tools. 5. Save disabled first if you are unsure. 6. Test the server. 7. Enable the server only after you understand what it can access. ## Controls - **Enable MCP** turns all external MCP tools on or off. - **Add Server** opens the manual server form. - **Import Config** imports server definitions from configuration text. - **Browse MCP Servers** searches available server directories. - **Diagnostics** helps explain connection failures. - **Per-server enablement** decides whether a saved server contributes tools. - **Test, refresh, edit, delete** manage the server row. ## Safety MCP tools can read, write, call APIs, or automate services depending on the server. Row-Bot approvals still matter, but you should also trust the server itself before enabling it. ## Troubleshooting - If a server fails to test, check transport, command, arguments, URL, and dependencies. - If tools are missing, enable both the global MCP switch and the server. - If a prompt asks for unexpected access, reject it and inspect the server configuration.

## Voice And Buddy

Route: /docs/voice-and-buddy/

Configure Dictate, Talk, local voice, realtime voice, read-aloud, devices, and Buddy.

# Voice And Buddy Voice and Buddy make Row-Bot feel less like a text box and more like a desktop companion. Voice handles speech input and optional spoken output. Buddy is the visual companion that reflects app state and can live in the sidebar, workspace, or desktop overlay. ## Voice Modes - **Dictate** turns speech into composer text so you can review it before sending. - **Talk** submits spoken input more directly for conversation. - **Read-aloud** speaks assistant responses when enabled. - **Local voice** uses local speech components where available. - **Realtime voice** uses a compatible provider for lower-latency spoken conversation. ## Choosing A Mode Use Dictate when accuracy and review matter. Use Talk when you want a faster hands-light conversation. Use local voice when privacy and offline-style behavior matter. Use realtime voice when latency matters and you accept internet access, provider requirements, and provider cost. ## Devices And Diagnostics Select the microphone and output device in Settings -> Voice. Run diagnostics when audio is silent, delayed, or routed to the wrong device. ## Buddy Controls - **Enable switches** choose sidebar, workspace, or desktop overlay visibility. - **Open and close overlay** manage the separate desktop companion window. - **Companion personality** changes the tone of Buddy cues. - **Bubble style** changes status presentation. - **Look cards** choose bundled or custom appearances. - **Generate full Buddy**, **Retry motion**, and **Use still only** manage custom looks. ## Privacy And Safety Voice input can become chat text. Realtime voice and provider-backed speech may send audio or transcript data to the selected provider. Buddy preferences and assets are local, but custom generation may call a configured media provider. ## Troubleshooting - If Dictate records nothing, check microphone selection and permissions. - If Talk sends too quickly, use Dictate instead. - If realtime voice is unavailable, check Providers and Voice Models. - If Buddy does not appear, check Buddy enable switches and overlay state.

## Operations, Data, And Recovery

Route: /docs/operations/

Back up, restore, update, repair, and uninstall Row-Bot without losing track of local data and credentials.

# Operations, Data, And Recovery Row-Bot is local-first, so operational safety starts with knowing which data directory and workspace are active. Conversations, settings, memory, Knowledge, workflows, documents, Designer projects, Developer workspace records, skills, plugins, logs, channel state, and MCP configuration can live under that directory. Operating-system key stores may hold credentials separately. ## Back Up 1. Open Settings and note the active data and workspace paths. 2. Stop running workflows, channels, servers, and active generations. 3. Close Row-Bot so databases are not changing during the copy. 4. Copy the whole active data directory to protected storage. 5. Back up external workspaces, exported Designer files, and Wiki vaults separately when they live elsewhere. 6. Record the Row-Bot version used with the backup. ## Restore Restore related databases and files as one set while Row-Bot is closed. Point a test launch at the restored directory first, then check conversations, providers, workflows, Knowledge, documents, Designer, Developer, plugins, MCP, and channels. Reconnect secrets that were stored in an OS keychain and were not included in the file backup. ## Update, Repair, And Uninstall Use the supported package or updater flow for your platform. Back up before a major update. Repair may replace application files but should not be treated as a data backup. Uninstalling the application and deleting the local data directory are separate decisions; review both the application location and the data location before removal. ## Logs And Support Use Monitor and the local log folder to diagnose startup, provider, workflow, channel, and background failures. Before sharing diagnostics, remove names, paths, account identifiers, document content, prompts, message content, tokens, and screenshots that expose private data. ## Release-Specific Manual Checks Installer UX, upgrade, repair, uninstall, Windows signing, macOS notarisation, native file dialogs, OS permissions, and clean-machine behaviour require manual testing on release candidates. A successful docs build does not prove those native flows are release-ready.

## Privacy And Safety

Route: /docs/privacy-safety/

Understand local data, provider calls, credentials, approvals, channels, MCP, plugins, and sharing.

# Privacy And Safety Row-Bot is local-first: the app and its data live on your machine. Local-first does not mean every feature is offline. Hosted models, web search, browser actions, account tools, channels, MCP servers, plugins, realtime voice, and media providers can send data outside the app when you configure and use them. ## Local Data Conversations, memories, documents, workflows, logs, Designer projects, Developer workspaces, skills, plugins, Buddy assets, and settings are stored in the active local Row-Bot data directory. ## External Calls External calls happen when you choose or enable something that needs them: hosted models, subscription providers, API providers, web search, browser automation, account tools, messaging channels, MCP servers, plugin tools, realtime voice, and media generation. Computer Use is a distinct opt-in boundary. Row-Bot downloads the pinned Cua Driver only after an explicit Install or Repair action, verifies the selected archive, and requires a telemetry disclosure before any executable invocation. The reviewed upstream telemetry includes installation and platform metadata but excludes typed content, screenshots, prompts, files, memories, tool arguments, secrets, and channel content. See [Computer Use](/docs/computer-use/) for the full boundary. ## Credentials Enter credentials only in the relevant Settings tab or provider sign-in flow. Row-Bot stores secrets in the operating system key store when available and keeps local metadata for status and diagnostics. ## Approvals Use approvals to review file writes, command execution, browser actions, account actions, channel sends, MCP calls, plugin tools, Developer changes, and other sensitive actions. Reject anything that does not match your request. Approval mode is policy, not a model choice: blocked actions stay blocked, ask-mode actions wait for you, and auto-approved actions follow the configured policy. Some prompts include a short model-written reason for readability, but the underlying approval gate and action details are system-controlled. ## Sharing Logs Or Screenshots Before sharing logs, screenshots, documents, thread exports, or review packages, check for names, file paths, account names, message contents, tokens, private documents, or misleading real data. ## Safer Defaults - Start with local models when privacy matters most. - Keep channels, MCP, and plugins disabled until needed. - Keep Computer Use disabled until a local interactive task needs native application control. - Use narrow workspaces for file tools. - Review approvals before external or destructive actions. - Keep a final human review step before publishing screenshots or docs built from a personal app state.

## Troubleshooting

Route: /docs/troubleshooting/

Resolve setup, model, chat, workflow, Designer, Developer, Knowledge, Monitor, Settings, channel, MCP, plugin, skill, voice, and Buddy issues.

# Troubleshooting Start with the visible status text in Row-Bot. Then check the relevant Settings tab and Monitor. Most issues fall into one of four categories: setup is incomplete, a provider or tool is disabled, the wrong model is selected, or Row-Bot is waiting for approval. ## Setup Problems - Reopen Setup Center if first launch was skipped or incomplete. - Check Settings -> Providers and Settings -> Models before troubleshooting Chat. - Check Settings -> System if local files, browser automation, command execution, or tunnels are involved. - For native application control, open the Computer Use setup card and resolve its driver or operating-system permission status before retrying. ## Model Problems - Refresh Providers, then refresh Models. - Choose a tool-capable model for workflows, Designer, Developer, and multi-step tool use. - For local and custom endpoints, use enough context for Row-Bot's instructions and tool schemas. ## Chat And Tool Problems - Check the model picker, Agent Profile, approval mode, and enabled tools. - If an action is waiting, review the thread approval prompt or open Activity Center. - Ask Row-Bot to explain the last tool result if the transcript is unclear. - If Computer Use is paused, choose Resume only after reviewing the target; if its lease is busy, stop or finish the active native task first. ## Workflow Problems - Confirm the workflow is not paused. - Run it manually once before trusting a schedule. - Check delivery defaults and channel status. ## Designer And Developer Problems - Designer: add a clearer goal, audience, references, or brand details. - Developer: confirm a workspace is open before asking for code actions. - Review commands and patches before approving or importing changes. ## Knowledge And Monitor Problems - If Knowledge is empty, enable memory or index documents. - If a record is wrong, edit or remove it. - Use Monitor logs, extraction journal, dream journal, and View Full Log for background issues. ## Integrations - Channels need credentials, optional tunnel setup, start/stop state, and user pairing. - MCP needs the global switch, a trusted server, and a successful test. - Plugins need installation, enablement, configuration, and sometimes a restart. - Skills need to be enabled and relevant to the prompt. ## Voice And Buddy - Check microphone/output device selection and permissions. - Use Dictate before Talk if you need review. - Check provider readiness for realtime voice. - Toggle Buddy visibility or reopen the overlay if the companion is missing.

## Reference

Route: /docs/reference/

Look up Row-Bot tools, providers, settings, channels, skills, MCP, plugins, data storage, and approvals.

# Reference Use the reference pages when you need a table or lookup after reading the guided docs. These pages are more compact and more technical than the walkthroughs. - [Tools](/docs/reference/generated/tools) - [Providers](/docs/reference/generated/providers) - [Settings](/docs/reference/generated/settings) - [Settings Controls](/docs/reference/generated/settings-controls) - [Home Tabs](/docs/reference/generated/home-tabs) - [Channels](/docs/reference/generated/channels) - [Skills](/docs/reference/generated/skills) - [MCP](/docs/reference/generated/mcp) - [Plugins](/docs/reference/generated/plugins) - [Data Storage](/docs/reference/generated/data-storage) - [Safety And Approvals](/docs/reference/generated/safety-approvals) - [Environment And Config](/docs/reference/generated/environment-and-config) - [CLI](/docs/reference/generated/cli) - [Screenshots](/docs/reference/generated/screenshots)

## Tools

Route: /docs/reference/generated/tools

Generated reference for Row-Bot tools and tool guides.

# Tools

## Providers

Route: /docs/reference/generated/providers

Generated reference for model providers and provider risk labels.

# Providers

## Settings

Route: /docs/reference/generated/settings

Generated reference for settings tabs.

# Settings

## Settings Controls

Route: /docs/reference/generated/settings-controls

Generated control-level settings reference with defaults, effects, dependencies, restart notes, and security notes.

# Settings Controls

## Home Tabs

Route: /docs/reference/generated/home-tabs

Generated reference for Home tab coverage.

# Home Tabs

## Channels

Route: /docs/reference/generated/channels

Generated reference for messaging channels.

# Channels

## Skills

Route: /docs/reference/generated/skills

Generated reference for bundled skills and tool guides.

# Skills

## MCP

Route: /docs/reference/generated/mcp

Generated reference for recommended MCP servers.

# MCP

## Plugins

Route: /docs/reference/generated/plugins

Generated reference for plugin manifest behavior.

# Plugins

## Data Storage

Route: /docs/reference/generated/data-storage

Generated reference for local data paths and storage.

# Data Storage

## Safety And Approvals

Route: /docs/reference/generated/safety-approvals

Generated reference for approval policy and safety modes.

# Safety And Approvals

## Environment And Config

Route: /docs/reference/generated/environment-and-config

Generated reference for important environment variables.

# Environment And Config

## CLI

Route: /docs/reference/generated/cli

Generated reference for launcher and plugin command-line options.

# CLI

## Screenshots

Route: /docs/reference/generated/screenshots

Generated reference for automated screenshot coverage.

# Screenshots

## Agent Profiles

Route: /docs/app-shell/agent-profiles

Choose and manage Agent Profiles for thread behavior, tool access, skills, and specialist work.

# Agent Profiles Agent Profiles are presets for how Row-Bot should act. A profile can change tone, tool availability, skill hints, approval posture, and specialist behavior. Use them when the same app needs to behave differently for research, coding, planning, design, or careful local-only work. ## Where To Find Profiles Open the **Agent profiles** area in the left sidebar, or use the profile control in a chat header when it is visible. The dialog lets you choose a profile for the current thread and inspect available built-in profiles. ## What The Profile Dialog Does - **Profile list** shows available built-in and local profiles. - **Selected profile** is the behavior Row-Bot will use for the current thread or new specialist run. - **Description** explains what the profile is optimized for. - **Tools and skills** indicate which capabilities the profile may prefer or restrict. - **Default behavior** explains whether the profile is meant for general chat, Agent Mode, Developer work, Designer work, or controlled tasks. - **Save or apply** records the choice for the current thread when the dialog offers it. ## Practical Examples - Use a research-style profile for web and document synthesis. - Use a coding profile inside Developer Studio so Row-Bot pays attention to files, commands, tests, and change review. - Use a cautious profile when you want more approvals and less external activity. - Use a design profile when you are working in Designer Studio and want visual output iteration. ## What Is Saved Profile selection can be saved on a thread, so future turns keep the same behavior. Built-in profile definitions are part of Row-Bot; local custom profiles are stored in local app data when supported. ## Privacy And Safety A profile can influence which tools Row-Bot prefers, but it does not bypass approvals. If a profile enables broader tool use, review approval prompts before allowing file writes, browser actions, shell commands, account actions, MCP calls, plugin tools, or channel sends. ## Troubleshooting - If Row-Bot behaves too narrowly, switch back to a general profile. - If a tool is unavailable, check both the profile and the related Settings tab. - If a profile choice does not stick, confirm you applied it to the active thread.

## Channels And Voice Guide

Route: /docs/guides/channels-and-voice

Compatibility page pointing to the current Channels guide.

# Channels And Voice Guide This guide has been split into focused pages so each feature has one authoritative walkthrough. - [Channels](/docs/integrations/channels) - [Plugins](/docs/integrations/plugins) - [MCP](/docs/integrations/mcp) - [Voice And Buddy](/docs/voice-and-buddy/) - [Settings](/docs/settings/)

## Designer Studio Guide

Route: /docs/guides/designer-studio

Compatibility page pointing to the current Designer Studio guide.

# Designer Studio Guide This guide has been split into focused pages so each feature has one authoritative walkthrough. - [Designer Studio](/docs/designer/) - [Plugins](/docs/integrations/plugins) - [MCP](/docs/integrations/mcp) - [Voice And Buddy](/docs/voice-and-buddy/) - [Settings](/docs/settings/)

## Developer Studio Guide

Route: /docs/guides/developer-studio

Compatibility page pointing to the current Developer Studio guide.

# Developer Studio Guide This guide has been split into focused pages so each feature has one authoritative walkthrough. - [Developer Studio](/docs/developer/) - [Plugins](/docs/integrations/plugins) - [MCP](/docs/integrations/mcp) - [Voice And Buddy](/docs/voice-and-buddy/) - [Settings](/docs/settings/)

## Skills, Plugins, And MCP Guide

Route: /docs/guides/skills-plugins-mcp

Compatibility page pointing to the current Skills Hub guide.

# Skills, Plugins, And MCP Guide This guide has been split into focused pages so each feature has one authoritative walkthrough. - [Skills Hub](/docs/skills/) - [Plugins](/docs/integrations/plugins) - [MCP](/docs/integrations/mcp) - [Voice And Buddy](/docs/voice-and-buddy/) - [Settings](/docs/settings/)

## Home: Designer

Route: /docs/home/designer

Use the Home Designer tab as the entry point for Designer Studio projects.

# Home: Designer The Designer tab is a launcher. It helps you start or reopen design projects, then hands off to Designer Studio for the full editor, preview, brand, and export workflow. ## What This Tab Is For Use this Home tab as a quick entry point. It shows current state and launch controls, while the full walkthrough lives in the [Designer Studio guide](/docs/designer/). ## What You Can Launch - New design starts a project from a prompt, template, or goal. - Recent projects reopen saved Designer work. - Brand and import actions prepare assets before you enter the editor. - Open in Designer Studio moves from the Home tab into the full workspace. ## What Is Saved Changes made from this tab apply to the feature it opens: workflows save as local automations, Designer projects save as local design projects, Developer workspaces save as local workspace records, Knowledge changes save to the local knowledge store, and Monitor filters affect the current review view. ## Next Step Open the [Designer Studio guide](/docs/designer/) when you need the control-by-control guide.

## Home: Developer

Route: /docs/home/developer

Use the Home Developer tab as the entry point for code workspaces and Custom Tools.

# Home: Developer The Developer tab is where you choose what code workspace Row-Bot should help with. The full Developer Studio page explains the inspector, chat, sandbox, commands, and review flow. ## What This Tab Is For Use this Home tab as a quick entry point. It shows current state and launch controls, while the full walkthrough lives in the [Developer Studio guide](/docs/developer/). ## What You Can Launch - Open folder connects an existing local project. - Connect repository attaches a Git repository already on the machine. - Clone repository creates a new local checkout from a remote URL. - Custom Tools opens the builder for reviewed, reusable local tools. ## What Is Saved Changes made from this tab apply to the feature it opens: workflows save as local automations, Designer projects save as local design projects, Developer workspaces save as local workspace records, Knowledge changes save to the local knowledge store, and Monitor filters affect the current review view. ## Next Step Open the [Developer Studio guide](/docs/developer/) when you need the control-by-control guide.

## Home

Route: /docs/home/

Use Home tabs as entry points for workflows, Designer, Developer, Knowledge, and Monitor.

# Home Home is the launch area for Row-Bot's major work surfaces. It is not meant to replace the detailed guides. Use Home to see current state and start work quickly, then open the dedicated page when you need a walkthrough. ## Home Tabs - [Workflows](/docs/home/workflows) is the entry point for saved automations. - [Designer](/docs/home/designer) starts design projects and opens Designer Studio. - [Developer](/docs/home/developer) connects code workspaces and opens Developer Studio. - [Knowledge](/docs/home/knowledge) reviews local memory, documents, and graph records. - [Monitor](/docs/home/monitor) shows logs, journals, channel state, and background activity. ## Dedicated Guides - [Workflows guide](/docs/guides/workflows) - [Designer Studio guide](/docs/designer/) - [Developer Studio guide](/docs/developer/) - [Knowledge guide](/docs/knowledge/) - [Monitor guide](/docs/monitor/)

## Home: Knowledge

Route: /docs/home/knowledge

Use the Home Knowledge tab to review memories, documents, and knowledge graph activity.

# Home: Knowledge The Knowledge tab is the review area for information Row-Bot can remember or retrieve. It is useful when you want to check what has been extracted, filter it, or open a detail card before relying on it in chat. ## What This Tab Is For Use this Home tab as a quick entry point. It shows current state and launch controls, while the full walkthrough lives in the [Knowledge guide](/docs/knowledge/). ## What You Can Launch - Filters narrow the list by source, status, or type. - Detail cards show the exact item Row-Bot may use later. - Edit controls let you correct useful records instead of deleting whole history. - Dream cycle controls help review background organization when enabled. ## What Is Saved Changes made from this tab apply to the feature it opens: workflows save as local automations, Designer projects save as local design projects, Developer workspaces save as local workspace records, Knowledge changes save to the local knowledge store, and Monitor filters affect the current review view. ## Next Step Open the [Knowledge guide](/docs/knowledge/) when you need the control-by-control guide.

## Home: Monitor

Route: /docs/home/monitor

Use the Home Monitor tab to inspect logs, journals, channel state, and background activity.

# Home: Monitor The Monitor tab is the place to answer: what is Row-Bot doing, what recently happened, and what needs attention? Use it during setup, workflows, channels, and troubleshooting. ## What This Tab Is For Use this Home tab as a quick entry point. It shows current state and launch controls, while the full walkthrough lives in the [Monitor guide](/docs/monitor/). ## What You Can Launch - Refresh updates status panels and recent logs. - View Journal opens knowledge extraction or dream cycle history. - View Full Log opens a longer diagnostic log view. - Channel status panels show whether external messaging connectors are running. ## What Is Saved Changes made from this tab apply to the feature it opens: workflows save as local automations, Designer projects save as local design projects, Developer workspaces save as local workspace records, Knowledge changes save to the local knowledge store, and Monitor filters affect the current review view. ## Next Step Open the [Monitor guide](/docs/monitor/) when you need the control-by-control guide.

## Home: Workflows

Route: /docs/home/workflows

Use the Home Workflows tab as the entry point for saved automations and background agents.

# Home: Workflows The Workflows tab is the dashboard for repeatable work. Use it to see existing workflows, run one manually, pause or resume schedules, and choose default delivery channels. ## What This Tab Is For Use this Home tab as a quick entry point. It shows current state and launch controls, while the full walkthrough lives in the [Workflows guide](/docs/guides/workflows). ## What You Can Launch - New Workflow opens the workflow builder. - Run starts the selected workflow with the current settings. - Delivery defaults choose where workflow results should appear. - Edit and delete controls appear on each workflow card when workflows exist. ## What Is Saved Changes made from this tab apply to the feature it opens: workflows save as local automations, Designer projects save as local design projects, Developer workspaces save as local workspace records, Knowledge changes save to the local knowledge store, and Monitor filters affect the current review view. ## Next Step Open the [Workflows guide](/docs/guides/workflows) when you need the control-by-control guide.

## Reference Tables

Route: /docs/reference/generated/

Compact lookup tables for Row-Bot features and settings.

# Reference Tables

## UI Tour

Route: /docs/ui-tour/

A short guided tour of the Row-Bot Interface, Chat, Home, Settings, and Activity Center.

# UI Tour Use this short tour if you want the quickest mental map before reading detailed pages. 1. Start in the [Row-Bot Interface](/docs/app-shell/navigation) guide to understand the sidebar, Home tabs, Activity Center, Settings, Buddy, and terminal. 2. Read [Chat](/docs/chat/) to understand threads, composer controls, models, attachments, tool traces, and approvals. 3. Visit [Home](/docs/home/) to see how Workflows, Designer, Developer, Knowledge, and Monitor are split. 4. Open [Settings](/docs/settings/) when you are ready to connect providers, documents, search, skills, system access, accounts, channels, MCP, plugins, Buddy, voice, and preferences. 5. Keep [Privacy And Safety](/docs/privacy-safety/) nearby when enabling external services or action tools.