From ea4a255e7d4c37a0f446a49979fafcdad98b3eed Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Wed, 10 Jun 2026 19:01:49 -0700
Subject: [PATCH 1/6] =?UTF-8?q?docs:=20dissolve=20Mothership=20into=20the?=
 =?UTF-8?q?=20docs=20=E2=80=94=20Sim=20is=20the=20agent,=20the=20surface?=
 =?UTF-8?q?=20is=20Chat?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The Mothership section was a shadow IA: four of its eight pages mirrored the
topic sections one-for-one, organized by interface instead of topic. With the
product retiring the brand (the built-in agent is just Sim, working in Chat),
the section dissolves into the docs proper:

- New Chat section, placed right after Get Started: chat/index (absorbs the
  command-center overview AND the research page), chat/tasks, chat/mailer.
- mothership/workflows -> workflows/building-in-chat, alongside the visual
  builder where it belongs.
- mothership/{tables,knowledge,files} fold into their topic indexes as
  condensed "In chat" sections — the capability lives with the topic.
- Prose voice throughout: "open Chat and ask" — Sim does things, Chat is the
  place. The user-built-agents collision is handled head-on (chat/index points
  at /agents; FAQ disambiguates Chat vs a chat deployment).
- Full reference sweep: homepage, introduction (10 refs), enterprise
  (retention/drains/access-control: "chat data"), costs voice table,
  workflows overview, getting-started FAQ, logs-debugging. App-facing
  literals deliberately kept until the app renames: the trigger enum values
  (mothership, copilot), drain category labels, and the @mothership.sim.ai
  mail domain.
- /mothership/:path* 308s to each new home (workflows/tables/knowledge/files/
  research/tasks/mailer all mapped individually); /copilot and /mailer chains
  retargeted to single hops.
- constitution.md language rules updated: Sim is the agent, "Chat" capitalized
  for the surface, "Mothership" moves to the never-say column.

Verified: all new pages render, every redirect class 308s to the right
target, full-tree link sweep 0 broken.

DO NOT MERGE until the app UI ships the rename — written for the future UI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .claude/rules/constitution.md                 |   6 +-
 apps/docs/content/docs/en/chat/index.mdx      |  91 +++++++++++++
 .../docs/en/{mothership => chat}/mailer.mdx   |   0
 .../docs/en/{mothership => chat}/tasks.mdx    |  36 +++---
 apps/docs/content/docs/en/files/index.mdx     |  10 ++
 .../content/docs/en/getting-started/index.mdx |   2 +-
 apps/docs/content/docs/en/index.mdx           |   2 +-
 .../content/docs/en/introduction/index.mdx    |  18 +--
 .../content/docs/en/knowledgebase/index.mdx   |  10 ++
 .../content/docs/en/logs-debugging/index.mdx  |   2 +-
 apps/docs/content/docs/en/meta.json           |  14 +-
 .../docs/content/docs/en/mothership/files.mdx | 120 ------------------
 .../docs/content/docs/en/mothership/index.mdx |  73 -----------
 .../content/docs/en/mothership/knowledge.mdx  |  85 -------------
 .../docs/content/docs/en/mothership/meta.json |   4 -
 .../content/docs/en/mothership/research.mdx   |  44 -------
 .../content/docs/en/mothership/tables.mdx     |  60 ---------
 apps/docs/content/docs/en/platform/costs.mdx  |   4 +-
 .../en/platform/enterprise/access-control.mdx |  16 +--
 .../en/platform/enterprise/data-drains.mdx    |   6 +-
 .../en/platform/enterprise/data-retention.mdx |   2 +-
 .../docs/en/platform/enterprise/index.mdx     |   4 +-
 apps/docs/content/docs/en/tables/index.mdx    |  11 ++
 .../building-in-chat.mdx}                     |  38 +++---
 apps/docs/content/docs/en/workflows/index.mdx |   4 +-
 apps/docs/next.config.ts                      |  23 +++-
 26 files changed, 217 insertions(+), 468 deletions(-)
 create mode 100644 apps/docs/content/docs/en/chat/index.mdx
 rename apps/docs/content/docs/en/{mothership => chat}/mailer.mdx (100%)
 rename apps/docs/content/docs/en/{mothership => chat}/tasks.mdx (70%)
 delete mode 100644 apps/docs/content/docs/en/mothership/files.mdx
 delete mode 100644 apps/docs/content/docs/en/mothership/index.mdx
 delete mode 100644 apps/docs/content/docs/en/mothership/knowledge.mdx
 delete mode 100644 apps/docs/content/docs/en/mothership/meta.json
 delete mode 100644 apps/docs/content/docs/en/mothership/research.mdx
 delete mode 100644 apps/docs/content/docs/en/mothership/tables.mdx
 rename apps/docs/content/docs/en/{mothership/workflows.mdx => workflows/building-in-chat.mdx} (61%)

diff --git a/.claude/rules/constitution.md b/.claude/rules/constitution.md
index 6881c060ee8..64f9e1eea8c 100644
--- a/.claude/rules/constitution.md
+++ b/.claude/rules/constitution.md
@@ -23,7 +23,7 @@ Sim is the **AI workspace** where teams build and run AI agents. Not a workflow
 | The product | "AI workspace" | "workflow tool", "automation platform", "agent framework" |
 | Building | "build agents", "create agents" | "create workflows" (unless describing the workflow module specifically) |
 | Visual builder | "workflow builder" or "visual builder" | "canvas", "graph editor" |
-| Mothership | "Mothership" (capitalized) | "chat", "AI assistant", "copilot" |
+| The built-in agent | "Sim" — Sim is the agent. The surface is "Chat" (capitalized) | "Mothership", "AI assistant", "copilot" |
 | Deployment | "deploy", "ship" | "publish", "activate" |
 | Audience | "teams", "builders" | "users", "customers" (in marketing copy) |
 | What agents do | "automate real work" | "automate tasks", "automate workflows" |
@@ -50,7 +50,7 @@ When describing Sim, always lead with the most differentiated claim:
 
 | Module | One-liner |
 |--------|-----------|
-| **Mothership** | Your AI command center. Build and manage everything in natural language. |
+| **Chat** | Open Chat and ask. Sim builds and manages everything in natural language. |
 | **Workflows** | The visual builder. Connect blocks, models, and integrations into agent logic. |
 | **Knowledge Base** | Your agents' memory. Upload docs, sync sources, build vector databases. |
 | **Tables** | A database, built in. Store, query, and wire structured data into agent runs. |
@@ -68,4 +68,4 @@ When describing Sim, always lead with the most differentiated claim:
 
 ## Vision
 
-Sim becomes the default environment where teams build AI agents — not a tool you visit for one task, but a workspace you live in. Workflows are one module; Mothership is another. The workspace is the constant; the interface adapts.
+Sim becomes the default environment where teams build AI agents — not a tool you visit for one task, but a workspace you live in. Workflows are one module; Chat is another. The workspace is the constant; the interface adapts.
diff --git a/apps/docs/content/docs/en/chat/index.mdx b/apps/docs/content/docs/en/chat/index.mdx
new file mode 100644
index 00000000000..66dcf6f2ddf
--- /dev/null
+++ b/apps/docs/content/docs/en/chat/index.mdx
@@ -0,0 +1,91 @@
+---
+title: Chat
+description: Open Chat and ask. Sim builds workflows, manages data, runs research, and takes action across your workspace.
+pageType: concept
+---
+
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
+import { FAQ } from '@/components/ui/faq'
+
+<Video src="mothership/create-workflow.mp4" width={700} height={450} />
+
+**Chat** is where you work with Sim directly. Describe what you want — build a workflow, run research, generate a presentation, query a table, schedule a recurring job, send a Slack message — and Sim does it. It knows your entire workspace and takes action directly.
+
+Everything Sim builds is a normal workspace resource: a workflow you can open in the builder, a table you can edit, a file you can download. Chat is the fastest way to create and change things; the rest of the docs cover what those things are and how to work them by hand. (Agents *you* build and deploy are a different topic — see [Agents](/agents).)
+
+## What you can ask for
+
+| Area | What to ask |
+|------|-------------|
+| **[Workflows](/workflows/building-in-chat)** | Build, edit, run, debug, deploy, and organize workflows |
+| **[Research](#research)** | Search the web, read pages, crawl sites, produce research reports |
+| **[Files](/files#in-chat)** | Upload, create, edit, and generate documents, presentations, and images |
+| **[Tables](/tables#in-chat)** | Create, query, update, and export workspace tables |
+| **[Scheduled tasks](/chat/tasks)** | Schedule jobs, take immediate actions, connect integrations, manage tools |
+| **[Knowledge bases](/knowledgebase#in-chat)** | Create knowledge bases, add documents, and query content in plain language |
+
+## How it works
+
+Sim receives a snapshot of your entire workspace with every message — all workflows, tables, knowledge bases, files, credentials, jobs, and integrations. That's why you can refer to things by name without specifying IDs or paths:
+
+- "Run the invoice workflow"
+- "Add a row to the leads table"
+- "Deploy the summarizer as a chat"
+
+No configuration, no context-setting. Just describe what you want:
+
+- "Build a lead enrichment workflow that scores inbound signups and writes the results to the leads table"
+- "Research our top 5 competitors and save a battle card for each one"
+- "Schedule a daily job that checks for new high-fit prospects and posts them to #outbound in Slack"
+- "Create a workflow that takes a contract PDF, extracts the key terms, and emails a summary to legal"
+
+For complex tasks, Sim delegates to specialized subagents automatically. You'll see them appear as collapsible sections in the chat while they work — building, researching, writing files, executing actions.
+
+{/* TODO: Screenshot of Chat showing a subagent section expanded mid-task — e.g., the Build or Research subagent actively working, with its collapsible header and steps visible in the thread. */}
+
+## Research [#research]
+
+Ask Sim to research anything and it figures out the best approach — searching the web, reading specific pages, crawling sites, looking up technical docs. It queries live internet data, so results reflect current information, not a training cutoff. (It can only read publicly accessible pages, not ones behind a login.)
+
+<Video src="mothership/research-agent.mp4" width={700} height={450} />
+
+- "What did Salesforce, HubSpot, and Gong each ship in the past 30 days? Summarize the key product updates."
+- "What's Acme Corp's tech stack, recent hires, and open engineering roles?"
+- "What are the current rate limits on the Anthropic API?"
+- "Read [URL] and tell me what changed in this release"
+
+Sim answers directly in the chat. When you need a structured, saved document instead, ask for a report: Sim searches, reads, and cross-references sources until it has enough, then saves the result as a [file](/files) in your workspace and opens it in the resource panel.
+
+- "Research the top 10 AI SDR tools — pricing, features, positioning, and what customers say. Save as a competitive analysis."
+- "Build a battle card for [competitor] — their positioning, pricing, strengths, weaknesses, and how we win against them."
+
+## Adding context
+
+Bring any workspace object into the conversation via the **+** menu, `@`-mentions, or drag-and-drop from the sidebar. Sim also opens resources automatically when it creates or modifies them.
+
+<Video src="mothership/context-menu.mp4" width={700} height={450} />
+
+| What to add | How it appears |
+|-------------|---------------|
+| **Workflow** | Interactive canvas in the resource panel |
+| **Table** | Full table editor in the resource panel |
+| **File** | File viewer with editor, split, and preview modes |
+| **Knowledge Base** | Knowledge base management UI |
+| **Folder** | Folder contents |
+| **Past task** | A previous conversation |
+
+## Layout
+
+Chat has two panes. On the left: the thread, where your messages and Sim's responses appear. On the right: the resource panel, where workflows, tables, files, and knowledge bases open as tabs. The panel is resizable; tabs are draggable and closeable.
+
+<Video src="mothership/split-view.mp4" width={700} height={450} />
+
+<FAQ items={[
+  { question: "Is this the same as a chat deployment?", answer: "No. Chat is where you build and manage your workspace by talking to Sim. A chat deployment publishes one workflow of yours as a chat interface for outside users. See Deployment for the latter." },
+  { question: "What model does Sim use in Chat?", answer: "Chat always uses Claude Opus 4.6. There is no model selector." },
+  { question: "How do I reference an existing workflow or table?", answer: "Type @ followed by the name in the input, use the + menu, or drag the item from the sidebar into the chat." },
+  { question: "How long can a task run?", answer: "Up to one hour. For tasks that exceed that, set up a scheduled job or break the work into steps." },
+  { question: "Can Sim work on multiple things at once?", answer: "Chat processes one message at a time. You can queue messages — they will be processed in order." },
+  { question: "Where are research reports saved?", answer: "Reports are saved as files in your workspace and opened in the resource panel. You can find them in the Files section of the sidebar." },
+]} />
diff --git a/apps/docs/content/docs/en/mothership/mailer.mdx b/apps/docs/content/docs/en/chat/mailer.mdx
similarity index 100%
rename from apps/docs/content/docs/en/mothership/mailer.mdx
rename to apps/docs/content/docs/en/chat/mailer.mdx
diff --git a/apps/docs/content/docs/en/mothership/tasks.mdx b/apps/docs/content/docs/en/chat/tasks.mdx
similarity index 70%
rename from apps/docs/content/docs/en/mothership/tasks.mdx
rename to apps/docs/content/docs/en/chat/tasks.mdx
index dedce2ec84d..22d0f7d6028 100644
--- a/apps/docs/content/docs/en/mothership/tasks.mdx
+++ b/apps/docs/content/docs/en/chat/tasks.mdx
@@ -1,5 +1,5 @@
 ---
-title: Automation & configuration
+title: Tasks & automation
 description: Schedule recurring jobs, take immediate actions, connect integrations, and configure your workspace.
 ---
 
@@ -10,11 +10,11 @@ import { FAQ } from '@/components/ui/faq'
 
 <Video src="mothership/job-create.mp4" width={700} height={450} />
 
-Mothership can act on your behalf right now — send a message, create an issue, call an API — or on a schedule, running a prompt automatically every hour, day, or week. It can also connect integrations, set environment variables, add MCP servers, and create custom tools.
+Sim can act on your behalf right now — send a message, create an issue, call an API — or on a schedule, running a prompt automatically every hour, day, or week. It can also connect integrations, set environment variables, add MCP servers, and create custom tools.
 
 ## Scheduled Jobs
 
-A scheduled job is a Mothership task that runs on a cron schedule. On each run, Mothership reads the current workspace state and executes the job's prompt as if you had just sent it.
+A scheduled job is a Sim task that runs on a cron schedule. On each run, Sim reads the current workspace state and executes the job's prompt as if you had just sent it.
 
 ### Creating a Job
 
@@ -28,7 +28,7 @@ Describe the recurring task and how often it should run:
 - "Every Sunday night, run the lead enrichment workflow on all prospects added in the past week and update their scores in the table"
 - "Daily at 6am, pull the previous day's workflow errors, summarize the top issues, and post to #eng-alerts"
 
-Mothership sets the cron expression and stores the job prompt. The first run happens at the next scheduled time.
+Sim sets the cron expression and stores the job prompt. The first run happens at the next scheduled time.
 
 ### Viewing Job Logs
 
@@ -47,9 +47,9 @@ Logs show run time, status (completed, failed), and a summary of what the agent
 
 ## Taking Direct Action
 
-For requests that should happen right now — without building a workflow — just ask. Mothership acts immediately using the credentials connected to your workspace.
+For requests that should happen right now — without building a workflow — just ask. Sim acts immediately using the credentials connected to your workspace.
 
-{/* TODO: Screenshot of Mothership chat showing the "Taking action" subagent label active during a direct action — e.g., posting to Slack or sending an email. Shows the subagent inline in the chat thread. */}
+{/* TODO: Screenshot of Sim chat showing the "Taking action" subagent label active during a direct action — e.g., posting to Slack or sending an email. Shows the subagent inline in the chat thread. */}
 
 | Request | What happens |
 |---------|-------------|
@@ -59,19 +59,19 @@ For requests that should happen right now — without building a workflow — ju
 | "Add a contact to HubSpot: Acme Corp, ceo@acme.com" | Creates the contact via HubSpot API |
 | "Call the webhook at [URL] with this JSON payload" | Makes the HTTP request |
 
-If an integration isn't connected, Mothership walks you through connecting it.
+If an integration isn't connected, Sim walks you through connecting it.
 
 ## Connecting Integrations
 
-Mothership can connect new OAuth integrations and API credentials on demand:
+Sim can connect new OAuth integrations and API credentials on demand:
 
 - "Connect my Google account"
 - "Add the Slack workspace for our team"
 - "Set up GitHub with my personal access token"
 
-{/* TODO: Screenshot of Mothership walking through connecting an integration — e.g., the Integration subagent active with an OAuth prompt or confirmation that a credential was connected. */}
+{/* TODO: Screenshot of Sim walking through connecting an integration — e.g., the Integration subagent active with an OAuth prompt or confirmation that a credential was connected. */}
 
-Once connected, credentials are available to Mothership for direct actions and scheduled jobs, and to all workflows in the workspace.
+Once connected, credentials are available to Sim for direct actions and scheduled jobs, and to all workflows in the workspace.
 
 <Callout type="info">
   Connected credentials are shared across the workspace. Any workflow that uses the same integration will automatically use the same credential.
@@ -89,13 +89,13 @@ Environment variables are workspace-scoped values — API keys, connection strin
 - "Update the SCORING_API_URL variable to point to the new endpoint"
 - "What environment variables are currently set?"
 
-{/* TODO: Screenshot of Mothership confirming an environment variable was set — e.g., a response message showing the variable name was saved. */}
+{/* TODO: Screenshot of Sim confirming an environment variable was set — e.g., a response message showing the variable name was saved. */}
 
 ## MCP Servers
 
 MCP (Model Context Protocol) servers expose tools from external services that Agent blocks can call inside workflows. Connecting an MCP server makes all of its tools available in the workflow editor's tool picker — no custom integration code required.
 
-Mothership can add and manage MCP servers connected to your workspace:
+Sim can add and manage MCP servers connected to your workspace:
 
 - "Add the Stripe MCP server using my API key"
 - "Remove the old analytics MCP server"
@@ -104,13 +104,13 @@ Mothership can add and manage MCP servers connected to your workspace:
 
 Once added, MCP tools appear in the workflow editor's tool picker and can be called from any Agent block.
 
-{/* TODO: Screenshot of Mothership confirming an MCP server was added or updated — showing the server name and its status. */}
+{/* TODO: Screenshot of Sim confirming an MCP server was added or updated — showing the server name and its status. */}
 
 ## Custom Tools
 
 Custom tools are single HTTP endpoints you define manually — useful for internal APIs and services that don't have a built-in Sim integration or an MCP server. Once created, they appear in the workflow editor alongside built-in tools and can be called from any Agent block.
 
-Mothership can build custom tools from a description:
+Sim can build custom tools from a description:
 
 - "Create a custom tool that calls our internal scoring API at [URL] with a POST request and returns the score field"
 - "Build a tool for our Zendesk instance that creates a ticket with a subject and body"
@@ -119,13 +119,13 @@ Mothership can build custom tools from a description:
 
 Custom tools appear in the workflow editor and are callable from any Agent block alongside built-in tools.
 
-{/* TODO: Screenshot of Mothership with the Custom Tool subagent active — showing it building a tool definition. */}
+{/* TODO: Screenshot of Sim with the Custom Tool subagent active — showing it building a tool definition. */}
 
 <FAQ items={[
-  { question: "What's the difference between a scheduled job and a deployed workflow?", answer: "A scheduled job runs a Mothership prompt on a cron schedule — Mothership decides what to do each time based on current workspace state. A deployed workflow runs a fixed, deterministic graph of blocks. Use jobs when you want Mothership to reason and adapt; use workflows when you want predictable, auditable execution." },
+  { question: "What's the difference between a scheduled job and a deployed workflow?", answer: "A scheduled job runs a Sim prompt on a cron schedule — Sim decides what to do each time based on current workspace state. A deployed workflow runs a fixed, deterministic graph of blocks. Use jobs when you want Sim to reason and adapt; use workflows when you want predictable, auditable execution." },
   { question: "Can a scheduled job trigger a workflow?", answer: "Yes. Include it in the job prompt: 'Run the invoice sync workflow and then post the results to Slack.'" },
-  { question: "How do I know what integrations are connected?", answer: "Ask Mothership: 'What integrations are connected to this workspace?' or check the Integrations page." },
-  { question: "Can direct actions be undone?", answer: "No. Actions like sending emails, posting to Slack, or creating records are immediate and irreversible. Confirm the details before asking Mothership to act." },
+  { question: "How do I know what integrations are connected?", answer: "ask Sim: 'What integrations are connected to this workspace?' or check the Integrations page." },
+  { question: "Can direct actions be undone?", answer: "No. Actions like sending emails, posting to Slack, or creating records are immediate and irreversible. Confirm the details before asking Sim to act." },
   { question: "Are environment variables visible to all workflows?", answer: "Yes. Environment variables are workspace-scoped and available to every workflow via {{ENV_VAR}} syntax." },
   { question: "What's the difference between MCP servers and custom tools?", answer: "MCP servers expose a set of tools from an external service over the MCP protocol — you connect an existing MCP-compatible server. Custom tools are single HTTP endpoints you define manually — useful for internal APIs that don't have an MCP server." },
 ]} />
diff --git a/apps/docs/content/docs/en/files/index.mdx b/apps/docs/content/docs/en/files/index.mdx
index 52e9470a6bc..6e2813758c8 100644
--- a/apps/docs/content/docs/en/files/index.mdx
+++ b/apps/docs/content/docs/en/files/index.mdx
@@ -18,6 +18,16 @@ Any [workflow](/workflows) can read a file or produce one. You might upload a co
 
 Use a file when the document or media itself is what matters. Use a [table](/tables) when you need structured rows and fields, and a [knowledge base](/knowledgebase) when an agent needs to search across many documents.
 
+## In chat [#in-chat]
+
+You can also work with files by asking Sim in [Chat](/chat): upload a document and ask questions about it, create or edit one, or generate a new document, presentation, or image from a description.
+
+- "Turn these notes into a one-page brief" *(attach file)*
+- "Generate a slide deck summarizing Q2 pipeline from the deals table"
+- "Edit proposal.md — make the pricing section match the new tiers"
+
+Files Sim creates land in your workspace [Files](/files), the same as an upload, ready for workflows or download.
+
 <Cards>
   <Card title="Using files in workflows" href="/files/using-in-workflows" description="Read a file into a workflow and produce one from a run." />
   <Card title="Passing files" href="/files/passing-files" description="Provide files to a workflow and receive generated files back." />
diff --git a/apps/docs/content/docs/en/getting-started/index.mdx b/apps/docs/content/docs/en/getting-started/index.mdx
index 12f4b76249b..79c7f8fb0ea 100644
--- a/apps/docs/content/docs/en/getting-started/index.mdx
+++ b/apps/docs/content/docs/en/getting-started/index.mdx
@@ -101,6 +101,6 @@ Build a people research agent in 10 minutes. It takes a name through a chat inte
   { question: "Do I need API keys to follow this tutorial?", answer: "No. On hosted Sim, the model and the search tools run on Sim's hosted keys, included with your plan credits. You can bring your own provider keys if you prefer." },
   { question: "Do I need coding experience to complete this tutorial?", answer: "No. The whole tutorial uses the visual builder and the chat panel — no code." },
   { question: "Can I use a different model?", answer: "Yes. The Agent block supports models from OpenAI, Anthropic, Google, Groq, Cerebras, DeepSeek, xAI, and more, plus local models through Ollama if you self-host." },
-  { question: "Can I import workflows from other tools?", answer: "Not directly. But you can describe what you want to Mothership in natural language and have it build the workflow for you, which is usually faster than manual recreation." },
+  { question: "Can I import workflows from other tools?", answer: "Not directly. But you can describe what you want in Chat and have Sim build the workflow for you, which is usually faster than manual recreation." },
   { question: "What if my workflow does not produce the expected output?", answer: "Test iteratively in the Chat panel and inspect each block's output from the dropdown to pinpoint where things go wrong. The Logs page records every run, block by block, with inputs, outputs, timing, and cost." },
 ]} />
diff --git a/apps/docs/content/docs/en/index.mdx b/apps/docs/content/docs/en/index.mdx
index e4e6ca4f453..c7360ed0398 100644
--- a/apps/docs/content/docs/en/index.mdx
+++ b/apps/docs/content/docs/en/index.mdx
@@ -6,7 +6,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card'
 
 # Sim Documentation
 
-Welcome to Sim, the open-source AI workspace where teams build, deploy, and manage AI agents. Create agents visually with the workflow builder, conversationally through Mothership, or programmatically with the API — connected to 1,000+ integrations and every major LLM.
+Welcome to Sim, the open-source AI workspace where teams build, deploy, and manage AI agents. Create agents visually with the workflow builder, conversationally in Chat, or programmatically with the API — connected to 1,000+ integrations and every major LLM.
 
 ## Quick Start
 
diff --git a/apps/docs/content/docs/en/introduction/index.mdx b/apps/docs/content/docs/en/introduction/index.mdx
index 3a8f3ec1795..10d566e93b1 100644
--- a/apps/docs/content/docs/en/introduction/index.mdx
+++ b/apps/docs/content/docs/en/introduction/index.mdx
@@ -9,7 +9,7 @@ import { Image } from '@/components/ui/image'
 import { Video } from '@/components/ui/video'
 import { FAQ } from '@/components/ui/faq'
 
-Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. You build by describing what you want to **Mothership**, the natural-language control plane, or visually in the workflow builder, or programmatically with the API. Connect AI models, databases, APIs, and 1,000+ business tools to build agents that automate real work.
+Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. You build by describing what you want in **Chat**, visually in the workflow builder, or programmatically with the API. Connect AI models, databases, APIs, and 1,000+ business tools to build agents that automate real work.
 
 <div className="mx-auto w-full overflow-hidden rounded-lg my-6">
   <Image
@@ -23,23 +23,23 @@ Sim is the open-source AI workspace where teams build, deploy, and manage AI age
 
 ## How you build
 
-When you open Sim, the first thing you meet is **Mothership**, a chat box over your whole workspace. You describe the system you want, and Mothership scaffolds it: workflows, tables, knowledge bases, and the wiring between them. You then open what it built, run it, and refine it.
+When you open Sim, the first thing you meet is **Chat**, a conversation over your whole workspace. You describe the system you want, and Sim scaffolds it: workflows, tables, knowledge bases, and the wiring between them. You then open what it built, run it, and refine it.
 
-- **Mothership.** Describe a system in natural language and it creates and edits the resources for you. The fastest way to start.
+- **Chat.** Describe a system in natural language and Sim creates and edits the resources for you. The fastest way to start.
 - **Workflow builder.** Design agent logic visually by connecting blocks in the builder. The clearest way to see and fine-tune what runs.
 - **API and SDK.** Build and trigger agents programmatically.
 
-You can mix these on one system, scaffolding with Mothership and then fine-tuning in the builder.
+You can mix these on one system, scaffolding in Chat and then fine-tuning in the builder.
 
 <Callout type="info">
-Mothership generates the architecture, and you verify the execution. Even when you build conversationally, it helps to understand the resources Mothership creates, so you can inspect, run, and improve them.
+Sim generates the architecture, and you verify the execution. Even when you build conversationally, it helps to understand the resources Sim creates, so you can inspect, run, and improve them.
 </Callout>
 
 ## The anatomy of a workspace
 
 A Sim system is not a single chat response. It is a set of resources that live in a **workspace** and connect to each other. The sidebar mirrors that anatomy, and these are its parts.
 
-- **[Mothership](/mothership)** is the natural-language control plane. You describe what you want, and it builds and edits the resources for you.
+- **[Chat](/chat)** is where you build conversationally. You describe what you want, and Sim builds and edits the resources for you.
 - **[Workflows](/workflows)** are visual programs made of blocks, where your logic runs. Most other resources become useful through a workflow.
 - **[Agents and tools](/agents)** are how a workflow acts. An agent reasons with a model, and tools let it take actions like sending an email or querying an API.
 - **[Tables](/tables)** hold structured rows your workflows read, write, and process.
@@ -83,7 +83,7 @@ For anything not built in, [MCP support](/agents/mcp) connects any external serv
   <Card title="Quickstart" href="/getting-started">
     Build your first agent in 10 minutes
   </Card>
-  <Card title="Building with Mothership" href="/mothership">
+  <Card title="Chat" href="/chat">
     Create and operate your workspace in natural language
   </Card>
   <Card title="Workflows" href="/workflows">
@@ -98,9 +98,9 @@ For anything not built in, [MCP support](/agents/mcp) connects any external serv
   { question: "Is Sim free to use?", answer: "Sim offers a free Community plan with 1,000 one-time credits to get started. Paid plans start at $25/month (Pro) with 5,000 credits and go up to $100/month (Max) with 20,000 credits. Annual billing is available at a 15% discount. You can also self-host Sim for free on your own infrastructure." },
   { question: "Is Sim open source?", answer: "Yes. Sim is open source under the Apache 2.0 license. The full source code is available on GitHub and you can self-host it, contribute to development, or modify it for your own needs. Enterprise features (SSO, access control) have a separate license that requires a subscription for production use." },
   { question: "Which AI models and providers are supported?", answer: "Sim supports 15+ providers including OpenAI, Anthropic, Google Gemini, Groq, Cerebras, DeepSeek, Mistral, xAI, and OpenRouter. You can also run local models through Ollama or VLLM at no API cost. Bring Your Own Key (BYOK) is supported so you can use your own API keys at base provider pricing with no markup." },
-  { question: "Do I need coding experience to use Sim?", answer: "No. Sim lets you build agents conversationally through Mothership using natural language, or visually by connecting blocks in the workflow builder. For advanced use cases, the Function block lets you write custom JavaScript, and the full API/SDK is available for programmatic access." },
+  { question: "Do I need coding experience to use Sim?", answer: "No. Sim lets you build agents conversationally in Chat using natural language, or visually by connecting blocks in the workflow builder. For advanced use cases, the Function block lets you write custom JavaScript, and the full API/SDK is available for programmatic access." },
   { question: "Can I self-host Sim?", answer: "Yes. Sim provides Docker Compose configurations for self-hosted deployments. The stack includes the Sim application, a PostgreSQL database with pgvector, and a realtime collaboration server. You can also integrate local AI models via Ollama for a fully offline setup." },
   { question: "Is there a limit on how many workflows I can create?", answer: "There is no limit on the number of workflows you can create on any plan. Usage limits apply to execution credits, rate limits, and file storage, which vary by plan tier." },
   { question: "What integrations are available?", answer: "Sim offers 1,000+ native integrations across categories including AI models, communication tools (Gmail, Slack, Teams, Telegram), productivity apps (Notion, Google Workspace, Airtable), development tools (GitHub, Jira, Linear), search services (Google Search, Perplexity, Exa), and databases (PostgreSQL, Supabase, Pinecone). For anything not built in, you can use the MCP (Model Context Protocol) support to connect custom services." },
-  { question: "How does Sim compare to other AI agent builders?", answer: "Sim is an AI workspace, not just a workflow tool or an agent framework. It combines Mothership for natural-language agent creation, a visual workflow builder, knowledge bases, tables, and full observability in one environment. Teams build agents visually, conversationally, or with code, then deploy and manage them with enterprise governance, real-time collaboration, and staging-to-production workflows." },
+  { question: "How does Sim compare to other AI agent builders?", answer: "Sim is an AI workspace, not just a workflow tool or an agent framework. It combines natural-language building in Chat, a visual workflow builder, knowledge bases, tables, and full observability in one environment. Teams build agents visually, conversationally, or with code, then deploy and manage them with enterprise governance, real-time collaboration, and staging-to-production workflows." },
 ]} />
diff --git a/apps/docs/content/docs/en/knowledgebase/index.mdx b/apps/docs/content/docs/en/knowledgebase/index.mdx
index f0d14803755..ca8731a8d2c 100644
--- a/apps/docs/content/docs/en/knowledgebase/index.mdx
+++ b/apps/docs/content/docs/en/knowledgebase/index.mdx
@@ -37,6 +37,16 @@ Two things control retrieval quality, and each has its own page:
 
 To keep a base in sync with an outside source like Google Drive, use a [connector](/knowledgebase/connectors).
 
+## In chat [#in-chat]
+
+You can also build and query a knowledge base by asking Sim in [Chat](/chat): create one, add documents to it, and ask questions against its content in plain language.
+
+- "Create a knowledge base from these PDFs" *(attach files)*
+- "Add the pricing docs folder to the support knowledge base"
+- "What does our refund policy say about annual plans?"
+
+Sim runs the same indexing and search described on this page, so anything it creates is immediately usable from the [Knowledge block](/knowledgebase/using-in-workflows) in a workflow.
+
 ## Next
 
 <Cards>
diff --git a/apps/docs/content/docs/en/logs-debugging/index.mdx b/apps/docs/content/docs/en/logs-debugging/index.mdx
index bc111469978..db139996381 100644
--- a/apps/docs/content/docs/en/logs-debugging/index.mdx
+++ b/apps/docs/content/docs/en/logs-debugging/index.mdx
@@ -90,7 +90,7 @@ When a value is the wrong shape, reshape it in a [Function](/workflows/blocks/fu
 
 ## AI-assisted debugging
 
-Mothership and Copilot can read a run's logs and propose a fix from the trace: the error message, the input the block received, and the output the upstream block produced. The logs stay the ground truth. You confirm a proposed fix the same way you confirm your own: rerun the workflow and compare the new trace against the failed one.
+Ask Sim in Chat to read a run's logs and it can propose a fix from the trace: the error message, the input the block received, and the output the upstream block produced. The logs stay the ground truth. You confirm a proposed fix the same way you confirm your own: rerun the workflow and compare the new trace against the failed one.
 
 ## Retention
 
diff --git a/apps/docs/content/docs/en/meta.json b/apps/docs/content/docs/en/meta.json
index 5d11bb02c2a..7e4e74f0309 100644
--- a/apps/docs/content/docs/en/meta.json
+++ b/apps/docs/content/docs/en/meta.json
@@ -4,12 +4,17 @@
     "---Get Started---",
     "./introduction/index",
     "./getting-started/index",
+    "---Chat---",
+    "./chat/index",
+    "./chat/tasks",
+    "./chat/mailer",
     "---Workflows---",
     "./workflows/index",
     "./workflows/how-it-runs",
     "./workflows/data-flow",
     "./workflows/connections",
     "./workflows/variables",
+    "./workflows/building-in-chat",
     "workflows/deployment",
     "workflows/triggers",
     "workflows/blocks",
@@ -41,15 +46,6 @@
     "./logs-debugging/index",
     "./logs-debugging/logging",
     "./logs-debugging/alerts",
-    "---Mothership---",
-    "./mothership/index",
-    "./mothership/workflows",
-    "./mothership/research",
-    "./mothership/files",
-    "./mothership/tables",
-    "./mothership/tasks",
-    "./mothership/knowledge",
-    "./mothership/mailer",
     "---Platform---",
     "./platform/workspaces",
     "./platform/organization",
diff --git a/apps/docs/content/docs/en/mothership/files.mdx b/apps/docs/content/docs/en/mothership/files.mdx
deleted file mode 100644
index 64eb36960e1..00000000000
--- a/apps/docs/content/docs/en/mothership/files.mdx
+++ /dev/null
@@ -1,120 +0,0 @@
----
-title: Files & documents
-description: Upload, create, edit, and generate files — documents, presentations, images, and more.
----
-
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-import { FAQ } from '@/components/ui/faq'
-
-<Video src="mothership/files-pipeline-deals-summarizer.mp4" width={700} height={450} />
-
-Describe a document, presentation, image, or visualization and Mothership creates it — streaming the content live into the resource panel as it writes. Attach any file to your message and Mothership reads it, processes it, and saves it to your workspace.
-
-## Uploading Files to the Workspace
-
-Attach any file directly to your Mothership message — drag it into the input, paste it, or click the attachment icon. Mothership reads the file as context and saves it to your workspace.
-
-Use this to:
-- Hand Mothership a document and ask it to process, summarize, or extract data from it
-- Upload a CSV and have it create a table from it
-- Drop in a PDF and ask Mothership to turn it into a knowledge base document
-- Attach a design mockup and ask Mothership to describe it or generate code from it
-
-Uploaded files appear in the Files panel in the sidebar and are accessible to all workflows in the workspace. Mothership can also fetch a file directly from a URL and save it for you: "Download the JSON at [URL] and save it to the workspace."
-
-## Creating Documents
-
-Mothership can write any text-based file — markdown, plain text, code files, CSV, JSON, or any other format:
-
-- "Write a technical spec for the new auth system as a markdown file"
-- "Create a CSV of our test accounts with columns for name, email, and plan tier"
-- "Write a Python script that calls our workflow API and processes the response"
-- "Draft a postmortem for the outage last Tuesday and save it as a markdown file"
-- "Write a personalized outbound email for Acme Corp based on their recent funding announcement"
-- "Draft a weekly ops digest summarizing workflow run counts, errors, and top failures for the past 7 days"
-
-Files are saved to your workspace and accessible from the Files panel in the sidebar.
-
-## Editing Existing Files
-
-Open a file using `@filename` or the **+** menu, then describe the change:
-
-- "Update the pricing section to reflect the new tiers"
-- "Refactor this Python script to use async/await"
-- "Add a section on error handling to this spec"
-- "Rewrite the introduction of this report to be more concise"
-
-## Presentations
-
-<Image src="/static/mothership/pptx-example.png" alt="Mothership resource panel showing a generated Mothership-Use-Cases.pptx file open with the title slide and first use case slide visible" width={900} height={500} />
-
-Mothership can generate `.pptx` files:
-
-- "Create a pitch deck for Q3 review — 8 slides covering growth, retention, and roadmap"
-- "Turn this research report into a 10-slide presentation"
-- "Build a deck that walks through our API onboarding flow"
-- "Build a battle card deck for our top 3 competitors — one slide each covering positioning, pricing, and how we win"
-- "Create an account plan for Acme Corp — their priorities, our solution fit, and proposed next steps"
-
-The file is saved to your workspace and can be downloaded.
-
-## Images
-
-Mothership can generate images using AI, and can use an existing image as a reference to guide the output:
-
-**Generating images:**
-- "Generate a banner image for the new feature announcement — dark background, clean typography"
-- "Create a diagram showing the data flow through our webhook pipeline"
-- "Make a social card for the blog post with the title and author name"
-
-**Using a reference image:**
-- Attach an existing image to your message, then describe what you want: "Generate a new version of this banner with a blue color scheme instead of green"
-- "Create a variation of this diagram with the boxes rearranged horizontally [attach image]"
-
-<Image src="/static/mothership/image-example.png" alt="Mothership resource panel showing a generated hero image of a Mothership-branded blimp flying over San Francisco at golden hour, alongside the chat response linking the file" width={900} height={500} />
-
-Generated images are saved as workspace files.
-
-## Charts and Visualizations
-
-Mothership can generate charts and data visualizations from data you describe or reference:
-
-- "Plot the workflow run counts from the metrics table as a bar chart grouped by week"
-- "Create a line chart of token usage over the past 30 days from this data [paste data]"
-- "Generate a pie chart showing the distribution of lead sources from the leads table"
-
-<Image src="/static/mothership/chart-example.png" alt="Mothership resource panel showing a generated chart file with bar charts for backend 5xx errors and error rate over time" width={900} height={500} />
-
-Visualizations are saved as files and rendered in the resource panel.
-
-## Calculations & Data Processing
-
-For one-off calculations and data transformations, describe what you need and Mothership runs it directly in the chat:
-
-- "Parse this JSON and extract all records where status is 'failed'"
-- "Calculate the p95 latency from these timing values: [paste values]"
-- "Convert these Unix timestamps to ISO 8601"
-- "Deduplicate this list of emails, case-insensitive"
-
-Results come back directly in the chat. Ask Mothership to save the output as a file if you need it.
-
-## File Viewer Modes
-
-When a file opens in the resource panel, you can switch between three views:
-
-<Video src="mothership/toggle-file-view.mp4" width={700} height={450} />
-
-| Mode | What it shows |
-|------|--------------|
-| **Editor** | Raw editable text |
-| **Preview** | Rendered output (markdown, HTML) |
-| **Split** | Editor and preview side by side |
-
-<FAQ items={[
-  { question: "Where are uploaded and generated files stored?", answer: "All files — uploaded, created, or generated — go to your workspace's Files section. They're accessible from the sidebar and can be referenced in any workflow." },
-  { question: "Can I use files created in Mothership in workflows?", answer: "Yes. Workspace files can be referenced in workflows using the File block or by passing them as inputs." },
-  { question: "What file types can I upload to Mothership?", answer: "You can attach images, PDFs, text files, JSON, XML, and other document formats directly to a Mothership message." },
-  { question: "What can Mothership calculate or process?", answer: "Anything expressible as a short script — parsing JSON, number crunching, string transformations, deduplication, format conversions. Results come back in the chat." },
-  { question: "Is there a file size limit for generated files?", answer: "There is no hard limit on generated file size, but very large files may take longer to stream." },
-]} />
diff --git a/apps/docs/content/docs/en/mothership/index.mdx b/apps/docs/content/docs/en/mothership/index.mdx
deleted file mode 100644
index 3f61f20df5a..00000000000
--- a/apps/docs/content/docs/en/mothership/index.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Building with Mothership
-description: Your AI command center. Build and manage your entire workspace in natural language.
----
-
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-import { FAQ } from '@/components/ui/faq'
-
-<Video src="mothership/create-workflow.mp4" width={700} height={450} />
-
-Describe what you want and Mothership handles it. Build a workflow, run research, generate a presentation, query a table, schedule a recurring job, send a Slack message — Mothership knows your entire workspace and takes action directly.
-
-## What You Can Do
-
-| Area | What Mothership can do |
-|------|-----------------------|
-| **[Workflows](/mothership/workflows)** | Build, edit, run, debug, deploy, and organize workflows |
-| **[Research](/mothership/research)** | Search the web, read pages, crawl sites, produce research reports |
-| **[Files & Documents](/mothership/files)** | Upload, create, edit, and generate documents, presentations, and images |
-| **[Tables](/mothership/tables)** | Create, query, update, and export workspace tables |
-| **[Automation & Configuration](/mothership/tasks)** | Schedule jobs, take immediate actions, connect integrations, manage tools |
-| **[Knowledge Bases](/mothership/knowledge)** | Create knowledge bases, add documents, and query content in plain language |
-
-## How It Works
-
-Mothership receives a snapshot of your entire workspace with every message — all workflows, tables, knowledge bases, files, credentials, jobs, and integrations. This is why you can refer to things by name without specifying IDs or paths:
-
-- "Run the invoice workflow"
-- "Add a row to the leads table"
-- "Deploy the summarizer as a chat"
-
-No configuration, no context-setting. Just describe what you want:
-
-- "Build a lead enrichment workflow that scores inbound signups and writes the results to the leads table"
-- "Research our top 5 competitors and save a battle card for each one"
-- "Schedule a daily job that checks for new high-fit prospects and posts them to #outbound in Slack"
-- "Create a workflow that takes a contract PDF, extracts the key terms, and emails a summary to legal"
-
-For complex tasks, Mothership delegates to specialized subagents automatically. You'll see them appear as collapsible sections in the chat while they work — building, researching, writing files, executing actions.
-
-{/* TODO: Screenshot of the Mothership chat showing a subagent section expanded mid-task — e.g., the Build or Research subagent actively working, with its collapsible header and steps visible in the thread. */}
-
-## Adding Context
-
-Bring any workspace object into the conversation via the **+** menu, `@`-mentions, or drag-and-drop from the sidebar. Mothership also opens resources automatically when it creates or modifies them.
-
-<Video src="mothership/context-menu.mp4" width={700} height={450} />
-
-{/* TODO: Screenshot of the resource panel with multiple tabs open — a workflow tab, a table tab, and a file tab — showing different resource types side by side. */}
-
-| What to add | How it appears |
-|-------------|---------------|
-| **Workflow** | Interactive canvas in the resource panel |
-| **Table** | Full table editor in the resource panel |
-| **File** | File viewer with editor, split, and preview modes |
-| **Knowledge Base** | Knowledge base management UI |
-| **Folder** | Folder contents |
-| **Past task** | A previous Mothership conversation |
-
-## Layout
-
-Mothership has two panes. On the left: the chat thread, where your messages and Mothership's responses appear. On the right: the resource panel, where workflows, tables, files, and knowledge bases open as tabs. The panel is resizable; tabs are draggable and closeable.
-
-<Video src="mothership/split-view.mp4" width={700} height={450} />
-
-<FAQ items={[
-  { question: "How is Mothership different from Copilot?", answer: "Copilot is scoped to a single workflow — it helps you build and edit that workflow. Mothership has access to your entire workspace and can build workflows, manage data, run research, schedule jobs, take actions across integrations, and more." },
-  { question: "What model does Mothership use?", answer: "Mothership always uses Claude Opus 4.6. There is no model selector." },
-  { question: "How do I reference an existing workflow or table?", answer: "Type @ followed by the name in the input, use the + menu, or drag the item from the sidebar into the chat." },
-  { question: "How long can a Mothership task run?", answer: "Up to one hour. For tasks that exceed that, set up a scheduled job or break the work into steps." },
-  { question: "Can Mothership work on multiple things at once?", answer: "Mothership processes one message at a time. You can queue messages — they will be processed in order." },
-]} />
diff --git a/apps/docs/content/docs/en/mothership/knowledge.mdx b/apps/docs/content/docs/en/mothership/knowledge.mdx
deleted file mode 100644
index 41c1edbb5d8..00000000000
--- a/apps/docs/content/docs/en/mothership/knowledge.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Knowledge bases
-description: Create, populate, and query knowledge bases from Mothership.
----
-
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-import { FAQ } from '@/components/ui/faq'
-
-<Video src="mothership/kb.mp4" width={700} height={450} />
-
-Create a knowledge base, add documents to it, and query it in plain language — all through conversation. Knowledge bases you create in Mothership are immediately available to Agent blocks in any workflow.
-
-## Creating Knowledge Bases
-
-Describe the knowledge base and Mothership creates it:
-
-- "Create a knowledge base called 'Product Docs'"
-- "Set up a knowledge base for our support team — call it 'Support KB'"
-- "Create a competitive intelligence knowledge base"
-- "Create a knowledge base from our sales playbook and attach it to the outbound agent workflow"
-- "Set up a customer success knowledge base — I'll add our onboarding guides and past case studies to it"
-
-## Adding Documents
-
-Add documents by attaching files to your message, pasting text, or pointing Mothership at a URL:
-
-- "Add this PDF to the Product Docs knowledge base [attach file]"
-- "Add the following text to the Support KB as a new document: [paste content]"
-- "Fetch the page at [URL] and add it to the competitive intelligence knowledge base"
-- "Add these three uploaded case studies to the customer success knowledge base"
-
-Mothership processes and indexes each document automatically. Once indexed, the content is searchable by any Agent block that has the knowledge base attached.
-
-{/* TODO: Screenshot of Mothership confirming a document was added and indexed — showing the document name and its indexed status in the knowledge base. */}
-
-## Querying Knowledge Bases
-
-Ask Mothership a question and it searches the specified knowledge base to answer:
-
-- "What does the Product Docs knowledge base say about our refund policy?"
-- "Search the Support KB for anything related to SSO setup errors"
-- "What are the key differences between our Pro and Enterprise plans, based on the product docs?"
-- "Find everything in the competitive intelligence knowledge base about [competitor]'s pricing"
-
-## Connectors
-
-For knowledge bases that should stay current automatically, connectors sync content from external services on a schedule — no manual uploads needed. New content is added, changed content is re-processed, and deleted content is removed on every run.
-
-Connectors are configured through the knowledge base settings, not through Mothership chat. Once connected, all synced content is immediately searchable by Mothership and by any Agent block with the knowledge base attached.
-
-Sim ships with 49 built-in connectors, including Notion, Google Drive, Slack, GitHub, Confluence, HubSpot, Salesforce, Gmail, and more.
-
-Examples of what you can sync:
-
-- **Notion** — sync a workspace, a database, or a specific page tree
-- **Google Drive / Dropbox / OneDrive** — sync documents from cloud storage
-- **GitHub** — sync a repository's markdown and code files
-- **Slack** — sync channel history
-- **Confluence / Jira** — sync your internal wiki or issue tracker
-- **HubSpot / Salesforce** — sync CRM records into a searchable knowledge base
-
-See [Connectors](/knowledgebase/connectors) for setup steps, sync frequency options, and managing connector status.
-
-## Managing Knowledge Bases
-
-List, inspect, and clean up knowledge bases in plain language:
-
-- "What knowledge bases are in this workspace?"
-- "How many documents are in the Support KB?"
-- "Remove the outdated pricing doc from the Product Docs knowledge base"
-- "Delete the old-competitive-intel knowledge base"
-
-## Using Knowledge Bases in Workflows
-
-Knowledge bases created in Mothership are immediately available to Agent blocks in any workflow. Attach a knowledge base to an Agent block and it will use semantic search to retrieve relevant content at runtime.
-
-See [Knowledge Base](/knowledgebase) for full details on document processing settings, search configuration, and connector syncing.
-
-<FAQ items={[
-  { question: "How do I attach a knowledge base to a workflow?", answer: "Open the Agent block in the workflow editor, find the Knowledge Base setting, and select the knowledge base by name. Mothership can also do this for you: 'Attach the Product Docs knowledge base to the research agent block in the content pipeline workflow.'" },
-  { question: "What file types can I add to a knowledge base?", answer: "PDFs, markdown files, plain text, and web pages fetched from URLs. Mothership handles the parsing and indexing automatically." },
-  { question: "Can I add documents to a knowledge base from a workflow run?", answer: "Yes. The Knowledge Base write tool is available to Agent blocks and can be used to add documents programmatically during a workflow run." },
-  { question: "How do I keep a knowledge base up to date?", answer: "Set up a connector to sync from an external source automatically — see Connectors above. For one-off updates, ask Mothership to add or replace the document directly." },
-]} />
diff --git a/apps/docs/content/docs/en/mothership/meta.json b/apps/docs/content/docs/en/mothership/meta.json
deleted file mode 100644
index 767005e2f25..00000000000
--- a/apps/docs/content/docs/en/mothership/meta.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-  "title": "Mothership",
-  "pages": ["index", "workflows", "research", "files", "tables", "tasks", "knowledge"]
-}
diff --git a/apps/docs/content/docs/en/mothership/research.mdx b/apps/docs/content/docs/en/mothership/research.mdx
deleted file mode 100644
index 19fd72c5bd0..00000000000
--- a/apps/docs/content/docs/en/mothership/research.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Research
-description: Ask Mothership to research anything — it searches, reads, and synthesizes from the web.
----
-
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-import { FAQ } from '@/components/ui/faq'
-
-<Video src="mothership/research-agent.mp4" width={700} height={450} />
-
-Ask Mothership to research anything and it figures out the best approach — searching the web, reading specific pages, crawling sites, looking up technical docs. Just describe what you want to know.
-
-## Asking Questions
-
-Ask anything — about a company, a competitor, a market, a technical question, or a specific URL:
-
-- "What did Salesforce, HubSpot, and Gong each ship in the past 30 days? Summarize the key product updates."
-- "What's Acme Corp's tech stack, recent hires, and open engineering roles?"
-- "Find everything published about [competitor] in the past 90 days — press, product changes, job postings."
-- "What are the current rate limits on the Anthropic API?"
-- "Read [URL] and tell me what changed in this release"
-- "What does Stripe's API say about handling webhooks with idempotency keys?"
-- "Who are the main players in AI-powered revenue operations, and how do they differentiate?"
-
-Mothership returns an answer directly in the chat. For anything that needs a longer written output, ask it to save the result as a file.
-
-## Research Reports
-
-When you need a structured, saved document rather than a chat answer, ask Mothership to write it up. It searches, reads, and cross-references multiple sources until it has enough to produce a full report. The output is saved as a file in your workspace and opened in the resource panel.
-
-{/* TODO: Screenshot of a completed research report open in the resource panel as a file — showing a structured markdown document with sections, findings, and citations. */}
-
-- "Research the top 10 AI SDR tools — pricing, features, positioning, and what customers say. Save as a competitive analysis."
-- "Do a full market landscape for AI in healthcare diagnostics — major players, funding, use cases, and regulatory environment."
-- "Research how our top 5 competitors handle multi-tenant auth — pricing, architecture, and any known vulnerabilities. Write it up as a report."
-- "Find every public case study on AI agents in financial compliance from the past 2 years. Summarize the key outcomes and save as a markdown file."
-- "Build a battle card for [competitor] — their positioning, pricing, strengths, weaknesses, and how we win against them."
-
-<FAQ items={[
-  { question: "Does Mothership have access to real-time information?", answer: "Yes. Mothership queries live internet data. Results reflect current information, not a training cutoff." },
-  { question: "Can Mothership read pages that require login?", answer: "No. Mothership can only read publicly accessible pages." },
-  { question: "Where are research reports saved?", answer: "Reports are saved as files in your workspace and opened in the resource panel. You can find them in the Files section of the sidebar." },
-]} />
diff --git a/apps/docs/content/docs/en/mothership/tables.mdx b/apps/docs/content/docs/en/mothership/tables.mdx
deleted file mode 100644
index dfe97a7f2a6..00000000000
--- a/apps/docs/content/docs/en/mothership/tables.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Tables
-description: Create, query, and manage workspace tables from Mothership.
----
-
-import { Image } from '@/components/ui/image'
-import { FAQ } from '@/components/ui/faq'
-
-<Image src="/static/mothership/table-example.png" alt="Mothership resource panel showing the pipeline_deals table with company, deal_owner, stage, and amount columns, alongside a chat summary of total pipeline value and breakdown by stage" width={900} height={500} />
-
-Create a table from a description or a CSV, query it in plain language, add or update rows, and export the results — all through conversation. Tables open in the resource panel as soon as they're created or referenced.
-
-## Creating Tables
-
-Describe the schema and Mothership creates the table:
-
-- "Create a leads table with columns for name, email, company, status, and created date"
-- "Create a table that matches the structure of this CSV [attach file]"
-- "Set up an errors table with: id (text), message (text), workflow (text), timestamp (date), resolved (boolean)"
-- "Create a prospect table for outbound — company, domain, employee count, industry, ICP score, and last contacted date"
-- "Set up an enrichment results table to store output from the lead enrichment workflow: email, company, title, LinkedIn URL, fit score"
-
-## Querying Data
-
-Ask questions about table contents in plain language:
-
-- "How many rows in the leads table have status 'qualified'?"
-- "Show me all records from the past 7 days where score is above 0.8"
-- "What are the top 5 most common error messages in the failures table?"
-- "Are there any duplicate emails in the contacts table?"
-- "How many prospects have an ICP score above 0.75 and haven't been contacted in the past 30 days?"
-- "What's the conversion rate from 'contacted' to 'meeting booked' in the pipeline table this month?"
-
-Mothership translates the question into a structured query and returns the results.
-
-## Adding and Updating Rows
-
-Add individual rows, bulk-update based on a condition, or delete records — all in plain language:
-
-- "Add a row to the leads table: Acme Corp, jane@acme.com, status pending"
-- "Mark all rows in the queue table as processed where created_at is before today"
-- "Update the price column for all rows where tier is 'pro' to 49"
-- "Delete all rows in the test_events table"
-
-## Exporting
-
-Export a full table or a filtered subset as a CSV. The file is saved to your workspace and can be downloaded or referenced in other workflows:
-
-- "Export the leads table to a CSV"
-- "Export all rows where status is 'closed' and save as a file"
-
-## Using Tables in Workflows
-
-Tables created in Mothership are immediately available in workflows via the [Table tool](/integrations/table). Reference a table by name — no additional configuration needed.
-
-<FAQ items={[
-  { question: "Can Mothership join or combine data from multiple tables?", answer: "Yes. Describe the relationship and what you want — Mothership will query both tables and combine the results." },
-  { question: "Is there a row limit?", answer: "There is no hard row limit set by Mothership. Performance for very large tables may vary." },
-  { question: "Can I use a table created in Mothership as a workflow data source?", answer: "Yes. All workspace tables are accessible to the Table block in any workflow." },
-]} />
diff --git a/apps/docs/content/docs/en/platform/costs.mdx b/apps/docs/content/docs/en/platform/costs.mdx
index 8a360e5a2e1..330d42c5567 100644
--- a/apps/docs/content/docs/en/platform/costs.mdx
+++ b/apps/docs/content/docs/en/platform/costs.mdx
@@ -246,11 +246,11 @@ When configured, workflows use your key instead of Sim's hosted keys. If removed
 
 ## Voice Input
 
-Voice input uses ElevenLabs Scribe v2 Realtime for speech-to-text transcription. It is available in the Mothership chat and in deployed chat voice mode.
+Voice input uses ElevenLabs Scribe v2 Realtime for speech-to-text transcription. It is available in Chat and in deployed chat voice mode.
 
 | Context | Cost per session | Max duration |
 |---------|-----------------|--------------|
-| Mothership (workspace) | ~5 credits ($0.024) | 3 minutes |
+| Chat (workspace) | ~5 credits ($0.024) | 3 minutes |
 | Deployed chat (voice mode) | ~2 credits ($0.008) | 1 minute |
 
 Each voice session is billed when it starts. In deployed chat voice mode, each conversation turn (speak → agent responds → speak again) is a separate session. Multi-turn conversations are billed per turn.
diff --git a/apps/docs/content/docs/en/platform/enterprise/access-control.mdx b/apps/docs/content/docs/en/platform/enterprise/access-control.mdx
index 38aa1ec8dac..dc21ccf5ca4 100644
--- a/apps/docs/content/docs/en/platform/enterprise/access-control.mdx
+++ b/apps/docs/content/docs/en/platform/enterprise/access-control.mdx
@@ -7,7 +7,7 @@ import { Callout } from 'fumadocs-ui/components/callout'
 import { FAQ } from '@/components/ui/faq'
 import { Image } from '@/components/ui/image'
 
-Access Control lets workspace admins define permission groups that restrict what each set of workspace members can do — which AI model providers they can use, which workflow blocks they can place, and which platform features are visible to them. Permission groups are scoped to a single workspace: a user can be in different groups (or no group) in different workspaces. Restrictions are enforced both in the workflow executor and in Mothership, based on the workflow's workspace.
+Access Control lets workspace admins define permission groups that restrict what each set of workspace members can do — which AI model providers they can use, which workflow blocks they can place, and which platform features are visible to them. Permission groups are scoped to a single workspace: a user can be in different groups (or no group) in different workspaces. Restrictions are enforced both in the workflow executor and in Chat, based on the workflow's workspace.
 
 ---
 
@@ -15,10 +15,10 @@ Access Control lets workspace admins define permission groups that restrict what
 
 Access control is built around **permission groups**. Each group belongs to a specific workspace and has a name, an optional description, and a configuration that defines what its members can and cannot do. A user can belong to at most one permission group **per workspace**, but can belong to different groups in different workspaces.
 
-When a user runs a workflow or uses Mothership, Sim reads their group's configuration and applies it:
+When a user runs a workflow or uses Chat, Sim reads their group's configuration and applies it:
 
 - **In the executor:** If a workflow uses a disallowed block type or model provider, execution halts immediately with an error. This applies to both manual runs and scheduled or API-triggered deployments.
-- **In Mothership:** Disallowed blocks are filtered out of the block list so they cannot be added to a workflow. Disallowed tool types (MCP, custom tools, skills) are skipped if Mothership attempts to use them.
+- **In Chat:** Disallowed blocks are filtered out of the block list so they cannot be added to a workflow. Disallowed tool types (MCP, custom tools, skills) are skipped if Sim attempts to use them.
 
 ---
 
@@ -146,12 +146,12 @@ Restrictions are enforced at the point of execution, not at save time. If a grou
 
 This applies regardless of how the workflow is triggered — manually, via API, via schedule, or via webhook.
 
-### Mothership
+### Chat
 
-When a user opens Mothership, their permission group is read before any block or tool suggestions are made:
+When a user opens Chat, their permission group is read before any block or tool suggestions are made:
 
 - Blocks not in the allowed list are filtered out of the block picker entirely — they do not appear as options.
-- If Mothership generates a workflow step that would use a disallowed tool (MCP, custom, or skills), that step is skipped and the reason is noted.
+- If Sim generates a workflow step that would use a disallowed tool (MCP, custom, or skills), that step is skipped and the reason is noted.
 
 ---
 
@@ -183,8 +183,8 @@ When a user opens Mothership, their permission group is read before any block or
     answer: "Users with no group in a given workspace have no restrictions in that workspace. All blocks, model providers, and platform features are fully available to them there. Restrictions only apply in the specific workspaces where they are assigned to a group."
   },
   {
-    question: "Does Mothership respect the same restrictions as the executor?",
-    answer: "Yes. Mothership reads the user's permission group for the active workspace before suggesting blocks or tools. Disallowed blocks are filtered out of the block picker, and disallowed tool types are skipped during workflow generation."
+    question: "Does Chat respect the same restrictions as the executor?",
+    answer: "Yes. Sim reads the user's permission group for the active workspace before suggesting blocks or tools. Disallowed blocks are filtered out of the block picker, and disallowed tool types are skipped during workflow generation."
   },
   {
     question: "Can I restrict access to specific workflows or workspaces?",
diff --git a/apps/docs/content/docs/en/platform/enterprise/data-drains.mdx b/apps/docs/content/docs/en/platform/enterprise/data-drains.mdx
index 8a55a28f449..1cea1446a1c 100644
--- a/apps/docs/content/docs/en/platform/enterprise/data-drains.mdx
+++ b/apps/docs/content/docs/en/platform/enterprise/data-drains.mdx
@@ -1,6 +1,6 @@
 ---
 title: Data Drains
-description: Continuously export workflow logs, audit logs, and Mothership data to your own object store, data warehouse, observability platform, or HTTPS endpoint on a schedule
+description: Continuously export workflow logs, audit logs, and chat data to your own object store, data warehouse, observability platform, or HTTPS endpoint on a schedule
 ---
 
 import { FAQ } from '@/components/ui/faq'
@@ -37,8 +37,8 @@ A drain exports exactly one source. To export multiple sources, create multiple
 | **Workflow logs** | Workflow execution records (one row per execution, only after the run reaches a terminal state). |
 | **Job logs** | Background job records (deployed APIs, schedules, webhooks). Only terminal-state rows are exported. |
 | **Audit logs** | Organization- and workspace-scoped audit events — logins, permission changes, resource creation/deletion, drain configuration changes. |
-| **Copilot chats** | Mothership chat history. |
-| **Copilot runs** | Mothership run records (terminal state only). |
+| **Copilot chats** | Chat history. |
+| **Copilot runs** | Chat run records (terminal state only). |
 
 Each row is delivered as a single line of NDJSON. The shape of each row is part of the public schema and stable across versions; every row carries an `id` field that downstream consumers can use to dedupe.
 
diff --git a/apps/docs/content/docs/en/platform/enterprise/data-retention.mdx b/apps/docs/content/docs/en/platform/enterprise/data-retention.mdx
index ecd4c4321d4..b8ef0f298ba 100644
--- a/apps/docs/content/docs/en/platform/enterprise/data-retention.mdx
+++ b/apps/docs/content/docs/en/platform/enterprise/data-retention.mdx
@@ -48,7 +48,7 @@ Resources covered:
 
 ### Task cleanup
 
-Controls how long **Mothership data** is kept, including:
+Controls how long **chat data** is kept, including:
 
 - Copilot chats and run history
 - Run checkpoints and async tool calls
diff --git a/apps/docs/content/docs/en/platform/enterprise/index.mdx b/apps/docs/content/docs/en/platform/enterprise/index.mdx
index 6544acddfd8..6b74bac7c2a 100644
--- a/apps/docs/content/docs/en/platform/enterprise/index.mdx
+++ b/apps/docs/content/docs/en/platform/enterprise/index.mdx
@@ -55,13 +55,13 @@ Track configuration and security-relevant actions across your organization for c
 
 ## Data Retention
 
-Configure how long execution logs, soft-deleted resources, and Mothership data are kept before permanent deletion. See the [data retention guide](/platform/enterprise/data-retention).
+Configure how long execution logs, soft-deleted resources, and chat data are kept before permanent deletion. See the [data retention guide](/platform/enterprise/data-retention).
 
 ---
 
 ## Data Drains
 
-Continuously export workflow logs, audit logs, and Mothership data to a customer-owned S3 bucket or HTTPS webhook on a schedule. See the [data drains guide](/platform/enterprise/data-drains).
+Continuously export workflow logs, audit logs, and chat data to a customer-owned S3 bucket or HTTPS webhook on a schedule. See the [data drains guide](/platform/enterprise/data-drains).
 
 ---
 
diff --git a/apps/docs/content/docs/en/tables/index.mdx b/apps/docs/content/docs/en/tables/index.mdx
index ae70683af65..63d188f441f 100644
--- a/apps/docs/content/docs/en/tables/index.mdx
+++ b/apps/docs/content/docs/en/tables/index.mdx
@@ -36,6 +36,17 @@ Open the **Tables** section in the sidebar and click **New table** to create one
 
 A [Table block](/tables/using-in-workflows) reads and writes rows from inside a workflow: query rows for reference data, write results back, or process a batch. A [workflow column](/tables/workflow-columns) goes a step further and runs a workflow against each row on its own. Everything in a table is also available over the [REST API](/api-reference/getting-started).
 
+## In chat [#in-chat]
+
+Everything on this page can be done by asking Sim in [Chat](/chat): create a table from a description or a CSV, query it in plain language, add or update rows, and export results.
+
+- "Create a leads table with columns for name, email, company, status, and created date"
+- "How many rows in the leads table have status 'qualified'?"
+- "Mark all rows in the queue table as processed where created_at is before today"
+- "Export all rows where status is 'closed' and save as a file"
+
+Sim translates the request into the same operations described above; tables it creates are immediately available to the [Table block](/integrations/table) in any workflow.
+
 ## Next
 
 <Cards>
diff --git a/apps/docs/content/docs/en/mothership/workflows.mdx b/apps/docs/content/docs/en/workflows/building-in-chat.mdx
similarity index 61%
rename from apps/docs/content/docs/en/mothership/workflows.mdx
rename to apps/docs/content/docs/en/workflows/building-in-chat.mdx
index 44ea4e33961..04a4967e394 100644
--- a/apps/docs/content/docs/en/mothership/workflows.mdx
+++ b/apps/docs/content/docs/en/workflows/building-in-chat.mdx
@@ -1,6 +1,6 @@
 ---
-title: Workflows
-description: Create, edit, run, debug, deploy, and organize workflows from Mothership.
+title: Building in chat
+description: Create, edit, run, debug, deploy, and organize workflows from Chat.
 ---
 
 import { Image } from '@/components/ui/image'
@@ -9,11 +9,11 @@ import { FAQ } from '@/components/ui/faq'
 
 <Video src="mothership/create-workflow.mp4" width={700} height={450} />
 
-Describe a workflow and Mothership builds it. Reference an existing one by name and it edits it. No canvas navigation required — every change appears in the resource panel in real time.
+Describe a workflow and Sim builds it. Reference an existing one by name and it edits it. No canvas navigation required — every change appears in the resource panel in real time.
 
 ## Creating Workflows
 
-Describe what the workflow should do — what triggers it, what it should do, which integrations it needs, and what it should return. Mothership builds it and opens the canvas in the resource panel.
+Describe what the workflow should do — what triggers it, what it should do, which integrations it needs, and what it should return. Sim builds it and opens the canvas in the resource panel.
 
 - "Build a workflow that takes a URL, scrapes the page, summarizes it with Claude, and sends the summary to a Slack channel"
 - "Create a workflow triggered by a webhook that extracts invoice data from a PDF and writes it to the billing table"
@@ -23,9 +23,9 @@ Describe what the workflow should do — what triggers it, what it should do, wh
 
 ## Editing Workflows
 
-{/* TODO: Screenshot of Mothership with the Edit subagent active and a change applied to an open workflow — e.g., a new block added or a configuration updated, visible on the canvas in the resource panel. */}
+{/* TODO: Screenshot of Sim with the Edit subagent active and a change applied to an open workflow — e.g., a new block added or a configuration updated, visible on the canvas in the resource panel. */}
 
-Open an existing workflow with `@workflow-name` or the **+** menu, then describe the change. Mothership reads the current structure before modifying it — you don't need to explain what already exists.
+Open an existing workflow with `@workflow-name` or the **+** menu, then describe the change. Sim reads the current structure before modifying it — you don't need to explain what already exists.
 
 - "Add a condition that routes to a different branch if the confidence score is below 0.7"
 - "Replace the GPT-4o model with Claude Opus 4.6 on the summarizer block"
@@ -35,7 +35,7 @@ Open an existing workflow with `@workflow-name` or the **+** menu, then describe
 
 <Video src="mothership/run-workflow.mp4" width={700} height={450} />
 
-Ask Mothership to run a workflow and it handles the execution:
+ask Sim to run a workflow and it handles the execution:
 
 - "Run the data sync workflow"
 - "Run the invoice processor with this PDF [attach file]"
@@ -45,7 +45,7 @@ Execution streams back to the chat. The workflow in the resource panel shows liv
 
 ## Reading Logs
 
-Mothership can retrieve and interpret execution logs for any workflow in the workspace:
+Sim can retrieve and interpret execution logs for any workflow in the workspace:
 
 - "Show me the last 10 runs of the pipeline workflow"
 - "Why did the invoice workflow fail yesterday?"
@@ -55,18 +55,18 @@ Logs include per-block execution state, outputs, errors, and timing.
 
 ## Debugging
 
-When a workflow fails, tell Mothership to debug it:
+When a workflow fails, tell Sim to debug it:
 
 - "Debug the last failed run of the content pipeline"
 - "The summarizer block is returning empty output — figure out why"
 
-Mothership reads the failure logs, identifies the cause, applies a fix, and can re-run to confirm.
+Sim reads the failure logs, identifies the cause, applies a fix, and can re-run to confirm.
 
-{/* TODO: Screenshot of the Debug subagent section in the Mothership chat showing it reading logs and applying a fix. */}
+{/* TODO: Screenshot of the Debug subagent section in the Sim chat showing it reading logs and applying a fix. */}
 
 ## Deploying
 
-Mothership can deploy a workflow as any of the three deployment types:
+Sim can deploy a workflow as any of the three deployment types:
 
 | Deployment type | What it creates |
 |----------------|----------------|
@@ -76,13 +76,13 @@ Mothership can deploy a workflow as any of the three deployment types:
 
 Ask: "Deploy the invoice workflow as an API and generate an API key."
 
-Mothership can also roll back: "Revert the billing workflow to the version from last Tuesday."
+Sim can also roll back: "Revert the billing workflow to the version from last Tuesday."
 
 See [API Deployment](/workflows/deployment/api) and [Chat Deployment](/workflows/deployment/chat) for full details on each deployment type.
 
 ## Organizing Workflows
 
-Mothership can create and manage folders to keep your workspace organized.
+Sim can create and manage folders to keep your workspace organized.
 
 **Folders:**
 - "Create a folder called 'Data Pipelines'"
@@ -94,11 +94,11 @@ Mothership can create and manage folders to keep your workspace organized.
 - "Rename the 'test_v2' workflow to 'lead-scorer'"
 - "Move the summarizer workflow to the research folder"
 
-{/* TODO: Screenshot showing Mothership confirming a folder or workflow organization action — e.g., a message confirming "Moved 'invoice-processor' into 'billing' folder" with the resource panel showing the folder open. */}
+{/* TODO: Screenshot showing Sim confirming a folder or workflow organization action — e.g., a message confirming "Moved 'invoice-processor' into 'billing' folder" with the resource panel showing the folder open. */}
 
 ## Workflow Variables
 
-Mothership can set global variables on a workflow — values accessible across all blocks in that workflow at runtime:
+Sim can set global variables on a workflow — values accessible across all blocks in that workflow at runtime:
 
 - "Set the API_ENDPOINT variable on the sync workflow to 'https://api.example.com/v2'"
 - "Update the MAX_RETRIES variable on the pipeline workflow to 5"
@@ -111,8 +111,8 @@ Variables set this way are available via `<variable.VARIABLE_NAME>` syntax insid
 - "Delete all workflows in the deprecated folder"
 
 <FAQ items={[
-  { question: "Can Mothership edit a workflow while it's deployed?", answer: "Yes. Editing a workflow does not affect the live deployment. The deployed version is a snapshot — you need to ask Mothership to redeploy to push changes to production." },
-  { question: "Can I run a workflow with specific inputs from Mothership?", answer: "Yes. Describe the inputs in your message and Mothership passes them to the workflow's start block." },
-  { question: "How does Mothership know what my workflow does?", answer: "When you reference a workflow, Mothership loads its full structure — every block, connection, and configuration — before acting on it." },
+  { question: "Can Sim edit a workflow while it's deployed?", answer: "Yes. Editing a workflow does not affect the live deployment. The deployed version is a snapshot — you need to ask Sim to redeploy to push changes to production." },
+  { question: "Can I run a workflow with specific inputs from Chat?", answer: "Yes. Describe the inputs in your message and Sim passes them to the workflow's start block." },
+  { question: "How does Sim know what my workflow does?", answer: "When you reference a workflow, Sim loads its full structure — every block, connection, and configuration — before acting on it." },
   { question: "What happens to a workflow's deployment when I delete it?", answer: "The workflow and all its deployments are permanently removed. Any API endpoints, chat URLs, or MCP tools that pointed to that workflow will stop working." },
 ]} />
diff --git a/apps/docs/content/docs/en/workflows/index.mdx b/apps/docs/content/docs/en/workflows/index.mdx
index 5cb1b0c72a5..b39d25aa9a8 100644
--- a/apps/docs/content/docs/en/workflows/index.mdx
+++ b/apps/docs/content/docs/en/workflows/index.mdx
@@ -84,9 +84,9 @@ When a workflow runs, blocks execute in dependency order: a block runs as soon a
 
 A workflow is where the rest of the workspace becomes behavior. On their own, tables, knowledge bases, files, and integrations are just resources. Workflows are where they *do* something.
 
-{/* VISUAL: system-context diagram. Mothership builds; tables/KBs/files/integrations feed; deployments expose; logs verify. */}
+{/* VISUAL: system-context diagram. Chat builds; tables/KBs/files/integrations feed; deployments expose; logs verify. */}
 
-- **Mothership** builds and edits workflows in natural language.
+- **[Chat](/chat)** — ask Sim to build and edit workflows in natural language.
 - **Tables, knowledge bases, files, and integrations** feed data, memory, artifacts, and actions into a workflow.
 - **Deployments** expose a workflow as an API, chat, or MCP server.
 - **Logs** record every run so you can verify what happened, step by step.
diff --git a/apps/docs/next.config.ts b/apps/docs/next.config.ts
index 5c91879d91f..59fa2dd3cd0 100644
--- a/apps/docs/next.config.ts
+++ b/apps/docs/next.config.ts
@@ -24,8 +24,8 @@ const config: NextConfig = {
       // form deployment removed
       { source: '/deployment/form', destination: '/workflows/deployment', permanent: true },
       // copilot deprecated and removed
-      { source: '/copilot', destination: '/mothership', permanent: true },
-      { source: '/copilot/:path*', destination: '/mothership', permanent: true },
+      { source: '/copilot', destination: '/chat', permanent: true },
+      { source: '/copilot/:path*', destination: '/chat', permanent: true },
       // connections/* and variables/* collapsed into single pages under workflows/
       { source: '/connections', destination: '/workflows/connections', permanent: true },
       { source: '/connections/:path*', destination: '/workflows/connections', permanent: true },
@@ -122,7 +122,24 @@ const config: NextConfig = {
         destination: '/workflows/deployment/:path*',
         permanent: true,
       },
-      { source: '/mailer', destination: '/mothership/mailer', permanent: true },
+      { source: '/mailer', destination: '/chat/mailer', permanent: true },
+      // Mothership section dissolved: the agent is Sim, the surface is Chat.
+      { source: '/mothership', destination: '/chat', permanent: true },
+      { source: '/mothership/research', destination: '/chat#research', permanent: true },
+      { source: '/mothership/tasks', destination: '/chat/tasks', permanent: true },
+      { source: '/mothership/mailer', destination: '/chat/mailer', permanent: true },
+      {
+        source: '/mothership/workflows',
+        destination: '/workflows/building-in-chat',
+        permanent: true,
+      },
+      { source: '/mothership/tables', destination: '/tables#in-chat', permanent: true },
+      {
+        source: '/mothership/knowledge',
+        destination: '/knowledgebase#in-chat',
+        permanent: true,
+      },
+      { source: '/mothership/files', destination: '/files#in-chat', permanent: true },
       { source: '/credentials', destination: '/platform/credentials', permanent: true },
       {
         source: '/credentials/:path*',

From 55353f6cd5be8437d126988313c7615887ee4d6e Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Wed, 10 Jun 2026 19:12:19 -0700
Subject: [PATCH 2/6] docs: TryInChat prompt component + fixes from a
 three-persona confusion test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

New TryInChat component (apps/docs/components/ui/try-in-chat.tsx): a titled,
click-to-copy prompt list that teaches the prompting patterns for the
surrounding page's topic. 23 instances replace the plain bullet example lists
across chat/index, chat/tasks, workflows/building-in-chat, and the In-chat
sections on tables/knowledgebase/files.

Three subagent readers (brand-new user, returning Mothership user, deep
builder) tested the renamed prose for confusion. Fixes from their confirmed
findings:

- chat/index: the agents-you-build and chat-deployment disambiguations move
  from a parenthetical and a buried FAQ into the body's second paragraph;
  subagents are marked as internal helpers, not agents you build.
- agents/index: "an agent in a chat" was ambiguous between an Agent block in
  a deployed chat and Sim's Chat — now "deployed as a chat"; and the missing
  statement that agents ship like any workflow (deploy as API/chat/MCP) is
  added, since chat/index pointed readers here for deployment.
- deployment/index: "an A2A agent" is a surface, not an agent — now "an A2A
  endpoint other AI agents can call".
- introduction: the agents bullet states the you-build vs Sim-in-Chat split at
  the first co-occurrence of both concepts.
- getting-started: <start.input> gets a reference-syntax gloss; "Chat panel"
  is pinned to the editor to avoid colliding with Chat.
- workflows overview: Start's entry points are "manual runs, API calls, and
  deployed chats" — the bare "chat" collided with three other meanings.
- logs: the mothership/copilot trigger values are labeled as legacy names for
  what is now Chat.
- building-in-chat: adds a build-an-agent prompt — the page never said Chat
  builds agents too.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 apps/docs/components/ui/try-in-chat.tsx       | 73 ++++++++++++++++++
 apps/docs/content/docs/en/agents/index.mdx    |  4 +-
 apps/docs/content/docs/en/chat/index.mdx      | 39 ++++++----
 apps/docs/content/docs/en/chat/tasks.mdx      | 75 +++++++++++--------
 apps/docs/content/docs/en/files/index.mdx     |  9 ++-
 .../content/docs/en/getting-started/index.mdx |  4 +-
 .../content/docs/en/introduction/index.mdx    |  2 +-
 .../content/docs/en/knowledgebase/index.mdx   |  9 ++-
 .../content/docs/en/logs-debugging/index.mdx  |  2 +-
 apps/docs/content/docs/en/tables/index.mdx    | 11 ++-
 .../docs/en/workflows/building-in-chat.mdx    | 72 +++++++++++-------
 .../docs/en/workflows/deployment/index.mdx    |  2 +-
 apps/docs/content/docs/en/workflows/index.mdx |  2 +-
 13 files changed, 215 insertions(+), 89 deletions(-)
 create mode 100644 apps/docs/components/ui/try-in-chat.tsx

diff --git a/apps/docs/components/ui/try-in-chat.tsx b/apps/docs/components/ui/try-in-chat.tsx
new file mode 100644
index 00000000000..a549ab19247
--- /dev/null
+++ b/apps/docs/components/ui/try-in-chat.tsx
@@ -0,0 +1,73 @@
+'use client'
+
+import { useState } from 'react'
+import { Check, Copy, MessageCircle } from 'lucide-react'
+import { cn } from '@/lib/utils'
+
+interface TryInChatProps {
+  prompts: string[]
+  /** Heading above the prompt list. Defaults to "Try in Chat". */
+  title?: string
+}
+
+function PromptRow({ prompt, isLast }: { prompt: string; isLast: boolean }) {
+  const [copied, setCopied] = useState(false)
+
+  const copy = async () => {
+    try {
+      await navigator.clipboard.writeText(prompt)
+      setCopied(true)
+      setTimeout(() => setCopied(false), 1500)
+    } catch {
+      // Clipboard unavailable (e.g. insecure context) — the text is still selectable.
+    }
+  }
+
+  return (
+    <button
+      type='button'
+      onClick={copy}
+      title='Copy prompt'
+      className={cn(
+        'group flex w-full cursor-pointer items-start gap-3 px-4 py-2.5 text-left transition-colors hover:bg-[rgba(0,0,0,0.02)] dark:hover:bg-[rgba(255,255,255,0.03)]',
+        !isLast && 'border-[rgba(0,0,0,0.08)] border-b dark:border-[rgba(255,255,255,0.08)]'
+      )}
+    >
+      <span className='flex-1 text-[0.875rem] text-[rgba(0,0,0,0.7)] leading-relaxed dark:text-[rgba(255,255,255,0.7)]'>
+        &ldquo;{prompt}&rdquo;
+      </span>
+      {copied ? (
+        <Check className='mt-1 h-3.5 w-3.5 shrink-0 text-emerald-600 dark:text-emerald-400' />
+      ) : (
+        <Copy className='mt-1 h-3.5 w-3.5 shrink-0 text-[rgba(0,0,0,0.25)] opacity-0 transition-opacity group-hover:opacity-100 dark:text-[rgba(255,255,255,0.3)]' />
+      )}
+    </button>
+  )
+}
+
+/**
+ * A list of copyable prompts the reader can paste into Chat, teaching the
+ * prompting patterns for the surrounding page's topic. Click a row to copy.
+ *
+ * @example
+ * <TryInChat prompts={[
+ *   "Create a leads table with columns for name, email, company, and status",
+ * ]} />
+ */
+export function TryInChat({ prompts, title = 'Try in Chat' }: TryInChatProps) {
+  return (
+    <div className='my-6 overflow-hidden rounded-xl border border-[rgba(0,0,0,0.08)] dark:border-[rgba(255,255,255,0.08)]'>
+      <div className='flex items-center gap-2 border-[rgba(0,0,0,0.08)] border-b bg-[rgba(0,0,0,0.02)] px-4 py-2 dark:border-[rgba(255,255,255,0.08)] dark:bg-[rgba(255,255,255,0.03)]'>
+        <MessageCircle className='h-3.5 w-3.5 text-[rgba(0,0,0,0.4)] dark:text-[rgba(255,255,255,0.4)]' />
+        <span className='font-[470] text-[0.8125rem] text-[rgba(0,0,0,0.6)] dark:text-[rgba(255,255,255,0.6)]'>
+          {title}
+        </span>
+      </div>
+      <div>
+        {prompts.map((prompt, index) => (
+          <PromptRow key={prompt} prompt={prompt} isLast={index === prompts.length - 1} />
+        ))}
+      </div>
+    </div>
+  )
+}
diff --git a/apps/docs/content/docs/en/agents/index.mdx b/apps/docs/content/docs/en/agents/index.mdx
index 73069186092..38509305925 100644
--- a/apps/docs/content/docs/en/agents/index.mdx
+++ b/apps/docs/content/docs/en/agents/index.mdx
@@ -51,7 +51,7 @@ To let an agent answer from your own content, connect a [knowledge base](/knowle
 
 ### Remember across runs: memory
 
-To let an agent reuse information from one run to the next, give it [memory](/integrations/memory), which stores and recalls values keyed to a conversation. Without it, each run starts fresh; with it, an agent in a chat carries what was said earlier into later messages.
+To let an agent reuse information from one run to the next, give it [memory](/integrations/memory), which stores and recalls values keyed to a conversation. Without it, each run starts fresh; with it, an agent [deployed as a chat](/workflows/deployment/chat) carries what was said earlier into later messages.
 
 ### Return a usable result: structured output
 
@@ -59,7 +59,7 @@ To make an agent's result something later blocks can act on, give it a **structu
 
 ## Choosing what to use
 
-Start with one Agent block and a prompt, then add only what the task needs: a tool when the agent should act, a skill when it needs written guidance, a knowledge base when it should answer from your documents, memory when it should remember, and a structured output when a later block has to read its result.
+Start with one Agent block and a prompt, then add only what the task needs: a tool when the agent should act, a skill when it needs written guidance, a knowledge base when it should answer from your documents, memory when it should remember, and a structured output when a later block has to read its result. An agent ships like any workflow — [deploy it](/workflows/deployment) as an API, a chat, or an MCP server.
 
 <Card title="Choosing what to use" href="/agents/choosing" description="A side-by-side guide to tools, skills, knowledge, and the rest, with one worked example." />
 
diff --git a/apps/docs/content/docs/en/chat/index.mdx b/apps/docs/content/docs/en/chat/index.mdx
index 66dcf6f2ddf..08623a0782b 100644
--- a/apps/docs/content/docs/en/chat/index.mdx
+++ b/apps/docs/content/docs/en/chat/index.mdx
@@ -7,12 +7,13 @@ pageType: concept
 import { Image } from '@/components/ui/image'
 import { Video } from '@/components/ui/video'
 import { FAQ } from '@/components/ui/faq'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 <Video src="mothership/create-workflow.mp4" width={700} height={450} />
 
 **Chat** is where you work with Sim directly. Describe what you want — build a workflow, run research, generate a presentation, query a table, schedule a recurring job, send a Slack message — and Sim does it. It knows your entire workspace and takes action directly.
 
-Everything Sim builds is a normal workspace resource: a workflow you can open in the builder, a table you can edit, a file you can download. Chat is the fastest way to create and change things; the rest of the docs cover what those things are and how to work them by hand. (Agents *you* build and deploy are a different topic — see [Agents](/agents).)
+Everything Sim builds is a normal workspace resource: a workflow you can open in the builder, a table you can edit, a file you can download. Chat is the fastest way to create and change things; the rest of the docs cover what those things are and how to work them by hand. Two nearby terms mean something else: an **agent** is a workflow *you* build that reasons and acts (see [Agents](/agents)), and a **[chat deployment](/workflows/deployment/chat)** publishes one of your workflows as a chat for outside users.
 
 ## What you can ask for
 
@@ -29,18 +30,22 @@ Everything Sim builds is a normal workspace resource: a workflow you can open in
 
 Sim receives a snapshot of your entire workspace with every message — all workflows, tables, knowledge bases, files, credentials, jobs, and integrations. That's why you can refer to things by name without specifying IDs or paths:
 
-- "Run the invoice workflow"
-- "Add a row to the leads table"
-- "Deploy the summarizer as a chat"
+<TryInChat prompts={[
+  "Run the invoice workflow",
+  "Add a row to the leads table",
+  "Deploy the summarizer as a chat",
+]} />
 
 No configuration, no context-setting. Just describe what you want:
 
-- "Build a lead enrichment workflow that scores inbound signups and writes the results to the leads table"
-- "Research our top 5 competitors and save a battle card for each one"
-- "Schedule a daily job that checks for new high-fit prospects and posts them to #outbound in Slack"
-- "Create a workflow that takes a contract PDF, extracts the key terms, and emails a summary to legal"
+<TryInChat prompts={[
+  "Build a lead enrichment workflow that scores inbound signups and writes the results to the leads table",
+  "Research our top 5 competitors and save a battle card for each one",
+  "Schedule a daily job that checks for new high-fit prospects and posts them to #outbound in Slack",
+  "Create a workflow that takes a contract PDF, extracts the key terms, and emails a summary to legal",
+]} />
 
-For complex tasks, Sim delegates to specialized subagents automatically. You'll see them appear as collapsible sections in the chat while they work — building, researching, writing files, executing actions.
+For complex tasks, Sim delegates to specialized subagents automatically — internal helpers, not the agents you build. You'll see them appear as collapsible sections in the chat while they work — building, researching, writing files, executing actions.
 
 {/* TODO: Screenshot of Chat showing a subagent section expanded mid-task — e.g., the Build or Research subagent actively working, with its collapsible header and steps visible in the thread. */}
 
@@ -50,15 +55,19 @@ Ask Sim to research anything and it figures out the best approach — searching
 
 <Video src="mothership/research-agent.mp4" width={700} height={450} />
 
-- "What did Salesforce, HubSpot, and Gong each ship in the past 30 days? Summarize the key product updates."
-- "What's Acme Corp's tech stack, recent hires, and open engineering roles?"
-- "What are the current rate limits on the Anthropic API?"
-- "Read [URL] and tell me what changed in this release"
+<TryInChat prompts={[
+  "What did Salesforce, HubSpot, and Gong each ship in the past 30 days? Summarize the key product updates.",
+  "What's Acme Corp's tech stack, recent hires, and open engineering roles?",
+  "What are the current rate limits on the Anthropic API?",
+  "Read [URL] and tell me what changed in this release",
+]} />
 
 Sim answers directly in the chat. When you need a structured, saved document instead, ask for a report: Sim searches, reads, and cross-references sources until it has enough, then saves the result as a [file](/files) in your workspace and opens it in the resource panel.
 
-- "Research the top 10 AI SDR tools — pricing, features, positioning, and what customers say. Save as a competitive analysis."
-- "Build a battle card for [competitor] — their positioning, pricing, strengths, weaknesses, and how we win against them."
+<TryInChat prompts={[
+  "Research the top 10 AI SDR tools — pricing, features, positioning, and what customers say. Save as a competitive analysis.",
+  "Build a battle card for [competitor] — their positioning, pricing, strengths, weaknesses, and how we win against them.",
+]} />
 
 ## Adding context
 
diff --git a/apps/docs/content/docs/en/chat/tasks.mdx b/apps/docs/content/docs/en/chat/tasks.mdx
index 22d0f7d6028..c53b2746915 100644
--- a/apps/docs/content/docs/en/chat/tasks.mdx
+++ b/apps/docs/content/docs/en/chat/tasks.mdx
@@ -7,6 +7,7 @@ import { Callout } from 'fumadocs-ui/components/callout'
 import { Image } from '@/components/ui/image'
 import { Video } from '@/components/ui/video'
 import { FAQ } from '@/components/ui/faq'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 <Video src="mothership/job-create.mp4" width={700} height={450} />
 
@@ -20,30 +21,36 @@ A scheduled job is a Sim task that runs on a cron schedule. On each run, Sim rea
 
 Describe the recurring task and how often it should run:
 
-- "Every morning at 8am, check the leads table for new entries and post a summary to #sales in Slack"
-- "Every Monday at 9am, pull last week's workflow run counts and write a report to the workspace"
-- "Run the data sync workflow every 6 hours"
-- "On the first of every month, export the billing table to CSV and email it to finance@example.com"
-- "Every weekday at 7am, check for new funding announcements from companies in our ICP and post the top 5 to #market-intel in Slack"
-- "Every Sunday night, run the lead enrichment workflow on all prospects added in the past week and update their scores in the table"
-- "Daily at 6am, pull the previous day's workflow errors, summarize the top issues, and post to #eng-alerts"
+<TryInChat prompts={[
+  "Every morning at 8am, check the leads table for new entries and post a summary to #sales in Slack",
+  "Every Monday at 9am, pull last week's workflow run counts and write a report to the workspace",
+  "Run the data sync workflow every 6 hours",
+  "On the first of every month, export the billing table to CSV and email it to finance@example.com",
+  "Every weekday at 7am, check for new funding announcements from companies in our ICP and post the top 5 to #market-intel in Slack",
+  "Every Sunday night, run the lead enrichment workflow on all prospects added in the past week and update their scores in the table",
+  "Daily at 6am, pull the previous day's workflow errors, summarize the top issues, and post to #eng-alerts",
+]} />
 
 Sim sets the cron expression and stores the job prompt. The first run happens at the next scheduled time.
 
 ### Viewing Job Logs
 
-- "Show me the last 5 runs of the weekly report job"
-- "Did the sync job run successfully this morning?"
-- "What did the Monday digest job do last week?"
+<TryInChat prompts={[
+  "Show me the last 5 runs of the weekly report job",
+  "Did the sync job run successfully this morning?",
+  "What did the Monday digest job do last week?",
+]} />
 
 Logs show run time, status (completed, failed), and a summary of what the agent did.
 
 ### Managing Jobs
 
-- "Pause the morning summary job"
-- "Change the sync job to run every 3 hours instead of 6"
-- "Delete the onboarding digest job"
-- "What scheduled jobs are currently active?"
+<TryInChat prompts={[
+  "Pause the morning summary job",
+  "Change the sync job to run every 3 hours instead of 6",
+  "Delete the onboarding digest job",
+  "What scheduled jobs are currently active?",
+]} />
 
 ## Taking Direct Action
 
@@ -65,9 +72,11 @@ If an integration isn't connected, Sim walks you through connecting it.
 
 Sim can connect new OAuth integrations and API credentials on demand:
 
-- "Connect my Google account"
-- "Add the Slack workspace for our team"
-- "Set up GitHub with my personal access token"
+<TryInChat prompts={[
+  "Connect my Google account",
+  "Add the Slack workspace for our team",
+  "Set up GitHub with my personal access token",
+]} />
 
 {/* TODO: Screenshot of Sim walking through connecting an integration — e.g., the Integration subagent active with an OAuth prompt or confirmation that a credential was connected. */}
 
@@ -83,11 +92,13 @@ See [Credentials](/platform/credentials) for managing connected accounts.
 
 Environment variables are workspace-scoped values — API keys, connection strings, and configuration that workflows reference via `{{ENV_VAR}}` syntax rather than hardcoding. Set them once and every workflow in the workspace can use them.
 
-- "Set the DATABASE_URL environment variable to 'postgres://...'"
-- "Add an OPENAI_API_KEY environment variable"
-- "Add a WEBHOOK_SECRET variable for the inbound webhook workflow"
-- "Update the SCORING_API_URL variable to point to the new endpoint"
-- "What environment variables are currently set?"
+<TryInChat prompts={[
+  "Set the DATABASE_URL environment variable to 'postgres://...'",
+  "Add an OPENAI_API_KEY environment variable",
+  "Add a WEBHOOK_SECRET variable for the inbound webhook workflow",
+  "Update the SCORING_API_URL variable to point to the new endpoint",
+  "What environment variables are currently set?",
+]} />
 
 {/* TODO: Screenshot of Sim confirming an environment variable was set — e.g., a response message showing the variable name was saved. */}
 
@@ -97,10 +108,12 @@ MCP (Model Context Protocol) servers expose tools from external services that Ag
 
 Sim can add and manage MCP servers connected to your workspace:
 
-- "Add the Stripe MCP server using my API key"
-- "Remove the old analytics MCP server"
-- "What MCP servers are connected to this workspace?"
-- "Update the endpoint for the internal tools MCP server to [URL]"
+<TryInChat prompts={[
+  "Add the Stripe MCP server using my API key",
+  "Remove the old analytics MCP server",
+  "What MCP servers are connected to this workspace?",
+  "Update the endpoint for the internal tools MCP server to [URL]",
+]} />
 
 Once added, MCP tools appear in the workflow editor's tool picker and can be called from any Agent block.
 
@@ -112,10 +125,12 @@ Custom tools are single HTTP endpoints you define manually — useful for intern
 
 Sim can build custom tools from a description:
 
-- "Create a custom tool that calls our internal scoring API at [URL] with a POST request and returns the score field"
-- "Build a tool for our Zendesk instance that creates a ticket with a subject and body"
-- "Create a tool that hits our internal enrichment API with a domain and returns company size, industry, and funding stage"
-- "Add a tool that calls our CRM's REST API to look up a contact by email and return their account owner"
+<TryInChat prompts={[
+  "Create a custom tool that calls our internal scoring API at [URL] with a POST request and returns the score field",
+  "Build a tool for our Zendesk instance that creates a ticket with a subject and body",
+  "Create a tool that hits our internal enrichment API with a domain and returns company size, industry, and funding stage",
+  "Add a tool that calls our CRM's REST API to look up a contact by email and return their account owner",
+]} />
 
 Custom tools appear in the workflow editor and are callable from any Agent block alongside built-in tools.
 
diff --git a/apps/docs/content/docs/en/files/index.mdx b/apps/docs/content/docs/en/files/index.mdx
index 6e2813758c8..6c6c9fb932c 100644
--- a/apps/docs/content/docs/en/files/index.mdx
+++ b/apps/docs/content/docs/en/files/index.mdx
@@ -5,6 +5,7 @@ pageType: concept
 ---
 
 import { Card, Cards } from 'fumadocs-ui/components/card'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 A **file** is a document, image, spreadsheet, or PDF in your workspace. Files are how documents and media move into and out of your agents. Your team uploads them, you create them in the editor, or a workflow produces them, and they all live in one store shared across the workspace.
 
@@ -22,9 +23,11 @@ Use a file when the document or media itself is what matters. Use a [table](/tab
 
 You can also work with files by asking Sim in [Chat](/chat): upload a document and ask questions about it, create or edit one, or generate a new document, presentation, or image from a description.
 
-- "Turn these notes into a one-page brief" *(attach file)*
-- "Generate a slide deck summarizing Q2 pipeline from the deals table"
-- "Edit proposal.md — make the pricing section match the new tiers"
+<TryInChat prompts={[
+  "Turn these notes into a one-page brief (attach the file)",
+  "Generate a slide deck summarizing Q2 pipeline from the deals table",
+  "Edit proposal.md — make the pricing section match the new tiers",
+]} />
 
 Files Sim creates land in your workspace [Files](/files), the same as an upload, ready for workflows or download.
 
diff --git a/apps/docs/content/docs/en/getting-started/index.mdx b/apps/docs/content/docs/en/getting-started/index.mdx
index 79c7f8fb0ea..dd1d7d2e73b 100644
--- a/apps/docs/content/docs/en/getting-started/index.mdx
+++ b/apps/docs/content/docs/en/getting-started/index.mdx
@@ -28,7 +28,7 @@ Build a people research agent in 10 minutes. It takes a name through a chat inte
 
     Drag an **Agent block** onto the canvas and configure its **Messages**:
     - **System**: "You are a people research agent. When given a person's name, use your search tools to find their location, profession, educational background, and other relevant details."
-    - **User**: insert `<start.input>` so the agent reads whatever the chat receives.
+    - **User**: insert `<start.input>` — a reference to the Start block's input, in the `<blockName.field>` syntax used everywhere in Sim — so the agent reads whatever the chat receives.
 
     Leave the **Model** on the default (`claude-sonnet-4-6`), or pick any other.
 
@@ -46,7 +46,7 @@ Build a people research agent in 10 minutes. It takes a name through a chat inte
   </Step>
 
   <Step title="Test it">
-    Open the **Chat panel**, select `agent1.content` as the output to display, and send: *"John is a software engineer from San Francisco who studied Computer Science at Stanford University."*
+    Open the editor's **Chat panel**, select `agent1.content` as the output to display, and send: *"John is a software engineer from San Francisco who studied Computer Science at Stanford University."*
 
     The agent searches, then returns what it found.
 
diff --git a/apps/docs/content/docs/en/introduction/index.mdx b/apps/docs/content/docs/en/introduction/index.mdx
index 10d566e93b1..85dcdca2e2c 100644
--- a/apps/docs/content/docs/en/introduction/index.mdx
+++ b/apps/docs/content/docs/en/introduction/index.mdx
@@ -41,7 +41,7 @@ A Sim system is not a single chat response. It is a set of resources that live i
 
 - **[Chat](/chat)** is where you build conversationally. You describe what you want, and Sim builds and edits the resources for you.
 - **[Workflows](/workflows)** are visual programs made of blocks, where your logic runs. Most other resources become useful through a workflow.
-- **[Agents and tools](/agents)** are how a workflow acts. An agent reasons with a model, and tools let it take actions like sending an email or querying an API.
+- **[Agents and tools](/agents)** are how a workflow acts. An agent reasons with a model, and tools let it take actions like sending an email or querying an API. These are agents *you* build — distinct from Sim itself working for you in Chat.
 - **[Tables](/tables)** hold structured rows your workflows read, write, and process.
 - **[Knowledge bases](/knowledgebase)** are searchable memory. An agent retrieves relevant passages from your documents to ground its answers.
 - **[Files](/files)** are the documents and media your workflows store, read, and produce.
diff --git a/apps/docs/content/docs/en/knowledgebase/index.mdx b/apps/docs/content/docs/en/knowledgebase/index.mdx
index ca8731a8d2c..56da0f53215 100644
--- a/apps/docs/content/docs/en/knowledgebase/index.mdx
+++ b/apps/docs/content/docs/en/knowledgebase/index.mdx
@@ -7,6 +7,7 @@ pageType: concept
 import { Video } from '@/components/ui/video'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { FAQ } from '@/components/ui/faq'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 A **knowledge base** is a store of documents your agents can search by meaning. You upload files, Sim splits them into chunks and indexes them, and a [Knowledge block](/knowledgebase/using-in-workflows) retrieves the chunks most relevant to a query. This is how an agent answers from your own content instead of the model's general training.
 
@@ -41,9 +42,11 @@ To keep a base in sync with an outside source like Google Drive, use a [connecto
 
 You can also build and query a knowledge base by asking Sim in [Chat](/chat): create one, add documents to it, and ask questions against its content in plain language.
 
-- "Create a knowledge base from these PDFs" *(attach files)*
-- "Add the pricing docs folder to the support knowledge base"
-- "What does our refund policy say about annual plans?"
+<TryInChat prompts={[
+  "Create a knowledge base from these PDFs (attach the files)",
+  "Add the pricing docs folder to the support knowledge base",
+  "What does our refund policy say about annual plans?",
+]} />
 
 Sim runs the same indexing and search described on this page, so anything it creates is immediately usable from the [Knowledge block](/knowledgebase/using-in-workflows) in a workflow.
 
diff --git a/apps/docs/content/docs/en/logs-debugging/index.mdx b/apps/docs/content/docs/en/logs-debugging/index.mdx
index db139996381..810bef52cd1 100644
--- a/apps/docs/content/docs/en/logs-debugging/index.mdx
+++ b/apps/docs/content/docs/en/logs-debugging/index.mdx
@@ -24,7 +24,7 @@ The **Logs page** lists every run across your workspace, one row per run. The [L
 
 ### The run
 
-Each row on the Logs page is one **run**. It records the **trigger** that started it (manual, api, schedule, chat, webhook, mcp, mothership, copilot, workflow, or a2a), a **status**, a **duration**, and the **cost** in credits. It also carries an **execution ID** that uniquely names the run.
+Each row on the Logs page is one **run**. It records the **trigger** that started it (manual, api, schedule, chat, webhook, mcp, mothership, copilot, workflow, or a2a — `mothership` and `copilot` are legacy values for what is now Chat), a **status**, a **duration**, and the **cost** in credits. It also carries an **execution ID** that uniquely names the run.
 
 The status shows the run's outcome at a glance, with failed runs badged **Error**. When you are hunting a failure, you filter the list to the errors and start there.
 
diff --git a/apps/docs/content/docs/en/tables/index.mdx b/apps/docs/content/docs/en/tables/index.mdx
index 63d188f441f..4738b37eeb7 100644
--- a/apps/docs/content/docs/en/tables/index.mdx
+++ b/apps/docs/content/docs/en/tables/index.mdx
@@ -7,6 +7,7 @@ pageType: concept
 import { Image } from '@/components/ui/image'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { FAQ } from '@/components/ui/faq'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 A **table** is a grid of typed columns in your workspace, like a spreadsheet with a schema. Use one to hold reference data, collect what your workflows produce, or store the structured records your agents read and write.
 
@@ -40,10 +41,12 @@ A [Table block](/tables/using-in-workflows) reads and writes rows from inside a
 
 Everything on this page can be done by asking Sim in [Chat](/chat): create a table from a description or a CSV, query it in plain language, add or update rows, and export results.
 
-- "Create a leads table with columns for name, email, company, status, and created date"
-- "How many rows in the leads table have status 'qualified'?"
-- "Mark all rows in the queue table as processed where created_at is before today"
-- "Export all rows where status is 'closed' and save as a file"
+<TryInChat prompts={[
+  "Create a leads table with columns for name, email, company, status, and created date",
+  "How many rows in the leads table have status 'qualified'?",
+  "Mark all rows in the queue table as processed where created_at is before today",
+  "Export all rows where status is 'closed' and save as a file",
+]} />
 
 Sim translates the request into the same operations described above; tables it creates are immediately available to the [Table block](/integrations/table) in any workflow.
 
diff --git a/apps/docs/content/docs/en/workflows/building-in-chat.mdx b/apps/docs/content/docs/en/workflows/building-in-chat.mdx
index 04a4967e394..c7f0121d1f9 100644
--- a/apps/docs/content/docs/en/workflows/building-in-chat.mdx
+++ b/apps/docs/content/docs/en/workflows/building-in-chat.mdx
@@ -6,6 +6,7 @@ description: Create, edit, run, debug, deploy, and organize workflows from Chat.
 import { Image } from '@/components/ui/image'
 import { Video } from '@/components/ui/video'
 import { FAQ } from '@/components/ui/faq'
+import { TryInChat } from '@/components/ui/try-in-chat'
 
 <Video src="mothership/create-workflow.mp4" width={700} height={450} />
 
@@ -15,11 +16,14 @@ Describe a workflow and Sim builds it. Reference an existing one by name and it
 
 Describe what the workflow should do — what triggers it, what it should do, which integrations it needs, and what it should return. Sim builds it and opens the canvas in the resource panel.
 
-- "Build a workflow that takes a URL, scrapes the page, summarizes it with Claude, and sends the summary to a Slack channel"
-- "Create a workflow triggered by a webhook that extracts invoice data from a PDF and writes it to the billing table"
-- "Build an outbound workflow: take a company name and domain, enrich it with firmographic data, score the fit, and draft a personalized cold email"
-- "Create a lead enrichment workflow that takes an email from a form submission, looks up the company, and writes the enriched record to the leads table"
-- "Build a customer onboarding workflow: when a new user signs up, send a welcome email, create a HubSpot contact, and post a notification to #new-customers in Slack"
+<TryInChat prompts={[
+  "Build a workflow that takes a URL, scrapes the page, summarizes it with Claude, and sends the summary to a Slack channel",
+  "Build an agent that reads incoming support emails and routes each one to the right team",
+  "Create a workflow triggered by a webhook that extracts invoice data from a PDF and writes it to the billing table",
+  "Build an outbound workflow: take a company name and domain, enrich it with firmographic data, score the fit, and draft a personalized cold email",
+  "Create a lead enrichment workflow that takes an email from a form submission, looks up the company, and writes the enriched record to the leads table",
+  "Build a customer onboarding workflow: when a new user signs up, send a welcome email, create a HubSpot contact, and post a notification to #new-customers in Slack",
+]} />
 
 ## Editing Workflows
 
@@ -27,9 +31,11 @@ Describe what the workflow should do — what triggers it, what it should do, wh
 
 Open an existing workflow with `@workflow-name` or the **+** menu, then describe the change. Sim reads the current structure before modifying it — you don't need to explain what already exists.
 
-- "Add a condition that routes to a different branch if the confidence score is below 0.7"
-- "Replace the GPT-4o model with Claude Opus 4.6 on the summarizer block"
-- "Add a Slack notification at the end that includes the output"
+<TryInChat prompts={[
+  "Add a condition that routes to a different branch if the confidence score is below 0.7",
+  "Replace the GPT-4o model with Claude Opus 4.6 on the summarizer block",
+  "Add a Slack notification at the end that includes the output",
+]} />
 
 ## Running Workflows
 
@@ -37,9 +43,11 @@ Open an existing workflow with `@workflow-name` or the **+** menu, then describe
 
 ask Sim to run a workflow and it handles the execution:
 
-- "Run the data sync workflow"
-- "Run the invoice processor with this PDF [attach file]"
-- "Test the lead scoring workflow with these inputs: name=Acme, score=0.4"
+<TryInChat prompts={[
+  "Run the data sync workflow",
+  "Run the invoice processor with this PDF [attach file]",
+  "Test the lead scoring workflow with these inputs: name=Acme, score=0.4",
+]} />
 
 Execution streams back to the chat. The workflow in the resource panel shows live block-by-block state.
 
@@ -47,9 +55,11 @@ Execution streams back to the chat. The workflow in the resource panel shows liv
 
 Sim can retrieve and interpret execution logs for any workflow in the workspace:
 
-- "Show me the last 10 runs of the pipeline workflow"
-- "Why did the invoice workflow fail yesterday?"
-- "What did the extractor block return in the most recent run?"
+<TryInChat prompts={[
+  "Show me the last 10 runs of the pipeline workflow",
+  "Why did the invoice workflow fail yesterday?",
+  "What did the extractor block return in the most recent run?",
+]} />
 
 Logs include per-block execution state, outputs, errors, and timing.
 
@@ -57,8 +67,10 @@ Logs include per-block execution state, outputs, errors, and timing.
 
 When a workflow fails, tell Sim to debug it:
 
-- "Debug the last failed run of the content pipeline"
-- "The summarizer block is returning empty output — figure out why"
+<TryInChat prompts={[
+  "Debug the last failed run of the content pipeline",
+  "The summarizer block is returning empty output — figure out why",
+]} />
 
 Sim reads the failure logs, identifies the cause, applies a fix, and can re-run to confirm.
 
@@ -85,14 +97,18 @@ See [API Deployment](/workflows/deployment/api) and [Chat Deployment](/workflows
 Sim can create and manage folders to keep your workspace organized.
 
 **Folders:**
-- "Create a folder called 'Data Pipelines'"
-- "Move the invoice workflow into the billing folder"
-- "Move the billing folder inside the finance folder"
-- "Delete the old-experiments folder"
+<TryInChat prompts={[
+  "Create a folder called 'Data Pipelines'",
+  "Move the invoice workflow into the billing folder",
+  "Move the billing folder inside the finance folder",
+  "Delete the old-experiments folder",
+]} />
 
 **Renaming and moving:**
-- "Rename the 'test_v2' workflow to 'lead-scorer'"
-- "Move the summarizer workflow to the research folder"
+<TryInChat prompts={[
+  "Rename the 'test_v2' workflow to 'lead-scorer'",
+  "Move the summarizer workflow to the research folder",
+]} />
 
 {/* TODO: Screenshot showing Sim confirming a folder or workflow organization action — e.g., a message confirming "Moved 'invoice-processor' into 'billing' folder" with the resource panel showing the folder open. */}
 
@@ -100,15 +116,19 @@ Sim can create and manage folders to keep your workspace organized.
 
 Sim can set global variables on a workflow — values accessible across all blocks in that workflow at runtime:
 
-- "Set the API_ENDPOINT variable on the sync workflow to 'https://api.example.com/v2'"
-- "Update the MAX_RETRIES variable on the pipeline workflow to 5"
+<TryInChat prompts={[
+  "Set the API_ENDPOINT variable on the sync workflow to 'https://api.example.com/v2'",
+  "Update the MAX_RETRIES variable on the pipeline workflow to 5",
+]} />
 
 Variables set this way are available via `<variable.VARIABLE_NAME>` syntax inside any block in the workflow.
 
 ## Deleting Workflows
 
-- "Delete the old_api_prototype workflow"
-- "Delete all workflows in the deprecated folder"
+<TryInChat prompts={[
+  "Delete the old_api_prototype workflow",
+  "Delete all workflows in the deprecated folder",
+]} />
 
 <FAQ items={[
   { question: "Can Sim edit a workflow while it's deployed?", answer: "Yes. Editing a workflow does not affect the live deployment. The deployed version is a snapshot — you need to ask Sim to redeploy to push changes to production." },
diff --git a/apps/docs/content/docs/en/workflows/deployment/index.mdx b/apps/docs/content/docs/en/workflows/deployment/index.mdx
index 92bf4121d02..12cb255c4d7 100644
--- a/apps/docs/content/docs/en/workflows/deployment/index.mdx
+++ b/apps/docs/content/docs/en/workflows/deployment/index.mdx
@@ -7,7 +7,7 @@ pageType: concept
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 
-A deployment is a published version of a [workflow](/workflows) that outside callers can run. While you build, a workflow lives on your canvas as a draft only you can run. Deploying publishes a fixed copy of that draft and gives it an address: a REST endpoint, a chat page, a set of [MCP](/workflows/deployment/mcp) tools, or an [A2A](/workflows/deployment/api) agent. Each is a **surface**, a channel callers reach the same published workflow through.
+A deployment is a published version of a [workflow](/workflows) that outside callers can run. While you build, a workflow lives on your canvas as a draft only you can run. Deploying publishes a fixed copy of that draft and gives it an address: a REST endpoint, a chat page, a set of [MCP](/workflows/deployment/mcp) tools, or an [A2A](/workflows/deployment/api) endpoint other AI agents can call. Each is a **surface**, a channel callers reach the same published workflow through.
 
 Like publishing a book, building and deploying are separate acts. You draft and revise freely on the canvas. When you click **Deploy**, Sim prints a fixed edition. Readers get that edition, not your latest draft, until you publish a new one. You can always go back to an earlier printing.
 
diff --git a/apps/docs/content/docs/en/workflows/index.mdx b/apps/docs/content/docs/en/workflows/index.mdx
index b39d25aa9a8..ffe3f69efbf 100644
--- a/apps/docs/content/docs/en/workflows/index.mdx
+++ b/apps/docs/content/docs/en/workflows/index.mdx
@@ -68,7 +68,7 @@ Two larger families do more specific jobs:
 
 ## How a workflow starts [#triggers]
 
-A trigger decides what starts the run and what input it receives. **Native triggers** need no connected account: [Start](/workflows/triggers/start) (manual, API, or chat), [Schedule](/workflows/triggers/schedule) (a timer), [Webhook](/workflows/triggers/webhook) (any inbound HTTP request), [RSS](/workflows/triggers/rss) (a new feed item), and [Table](/workflows/triggers/table) (a row change in a Sim table). **Integration triggers** fire on an event in a connected service — a GitHub push, a new email — and hand it to the workflow.
+A trigger decides what starts the run and what input it receives. **Native triggers** need no connected account: [Start](/workflows/triggers/start) (manual runs, API calls, and deployed chats), [Schedule](/workflows/triggers/schedule) (a timer), [Webhook](/workflows/triggers/webhook) (any inbound HTTP request), [RSS](/workflows/triggers/rss) (a new feed item), and [Table](/workflows/triggers/table) (a row change in a Sim table). **Integration triggers** fire on an event in a connected service — a GitHub push, a new email — and hand it to the workflow.
 
 <Callout type="info">
 Every trigger runs the active [deployment](/workflows/deployment), so redeploy after changing a workflow for it to pick up the new version.

From 80b7c5fe1e8a6c49dd46e649a4ae8df3b369ef94 Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Wed, 10 Jun 2026 19:23:02 -0700
Subject: [PATCH 3/6] docs: restore the full prompt collections, grouped on
 their topic pages
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The old Mothership pages were prompt showcases — the dissolution kept the
structure but over-condensed them (~50 prompts down to ~10). The collections
are back, recovered from the pre-dissolution pages and integrated where they
teach: tables gets creating/querying/updating/exporting groups, knowledge
bases gets creating/adding/querying/managing, files gets documents/editing/
presentations/images/charts — each as a titled TryInChat block, click-to-copy.
Near-duplicates trimmed; the cross-table query capability folded into prose.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 apps/docs/content/docs/en/files/index.mdx     | 29 +++++++++++++++++--
 .../content/docs/en/knowledgebase/index.mdx   | 24 ++++++++++++---
 apps/docs/content/docs/en/tables/index.mdx    | 21 ++++++++++++--
 3 files changed, 65 insertions(+), 9 deletions(-)

diff --git a/apps/docs/content/docs/en/files/index.mdx b/apps/docs/content/docs/en/files/index.mdx
index 6c6c9fb932c..780bdbdc3d8 100644
--- a/apps/docs/content/docs/en/files/index.mdx
+++ b/apps/docs/content/docs/en/files/index.mdx
@@ -23,10 +23,33 @@ Use a file when the document or media itself is what matters. Use a [table](/tab
 
 You can also work with files by asking Sim in [Chat](/chat): upload a document and ask questions about it, create or edit one, or generate a new document, presentation, or image from a description.
 
-<TryInChat prompts={[
-  "Turn these notes into a one-page brief (attach the file)",
-  "Generate a slide deck summarizing Q2 pipeline from the deals table",
+<TryInChat title="Try in Chat — documents" prompts={[
+  "Write a technical spec for the new auth system as a markdown file",
+  "Draft a postmortem for the outage last Tuesday and save it as a markdown file",
+  "Create a CSV of our test accounts with columns for name, email, and plan tier",
+]} />
+
+<TryInChat title="Try in Chat — editing" prompts={[
   "Edit proposal.md — make the pricing section match the new tiers",
+  "Add a section on error handling to this spec",
+  "Rewrite the introduction of this report to be more concise",
+]} />
+
+<TryInChat title="Try in Chat — presentations" prompts={[
+  "Create a pitch deck for Q3 review — 8 slides covering growth, retention, and roadmap",
+  "Turn this research report into a 10-slide presentation",
+  "Build a battle card deck for our top 3 competitors — one slide each covering positioning, pricing, and how we win",
+]} />
+
+<TryInChat title="Try in Chat — images" prompts={[
+  "Generate a banner image for the new feature announcement — dark background, clean typography",
+  "Create a diagram showing the data flow through our webhook pipeline",
+  "Make a social card for the blog post with the title and author name",
+]} />
+
+<TryInChat title="Try in Chat — charts" prompts={[
+  "Plot the workflow run counts from the metrics table as a bar chart grouped by week",
+  "Generate a pie chart showing the distribution of lead sources from the leads table",
 ]} />
 
 Files Sim creates land in your workspace [Files](/files), the same as an upload, ready for workflows or download.
diff --git a/apps/docs/content/docs/en/knowledgebase/index.mdx b/apps/docs/content/docs/en/knowledgebase/index.mdx
index 56da0f53215..cc881ba72e3 100644
--- a/apps/docs/content/docs/en/knowledgebase/index.mdx
+++ b/apps/docs/content/docs/en/knowledgebase/index.mdx
@@ -42,10 +42,26 @@ To keep a base in sync with an outside source like Google Drive, use a [connecto
 
 You can also build and query a knowledge base by asking Sim in [Chat](/chat): create one, add documents to it, and ask questions against its content in plain language.
 
-<TryInChat prompts={[
-  "Create a knowledge base from these PDFs (attach the files)",
-  "Add the pricing docs folder to the support knowledge base",
-  "What does our refund policy say about annual plans?",
+<TryInChat title="Try in Chat — creating" prompts={[
+  "Set up a knowledge base for our support team — call it 'Support KB'",
+  "Create a knowledge base from our sales playbook and attach it to the outbound agent workflow",
+]} />
+
+<TryInChat title="Try in Chat — adding documents" prompts={[
+  "Add this PDF to the Product Docs knowledge base (attach the file)",
+  "Fetch the page at [URL] and add it to the competitive intelligence knowledge base",
+  "Add these three uploaded case studies to the customer success knowledge base",
+]} />
+
+<TryInChat title="Try in Chat — querying" prompts={[
+  "What does the Product Docs knowledge base say about our refund policy?",
+  "Search the Support KB for anything related to SSO setup errors",
+  "Find everything in the competitive intelligence knowledge base about [competitor]'s pricing",
+]} />
+
+<TryInChat title="Try in Chat — managing" prompts={[
+  "How many documents are in the Support KB?",
+  "Remove the outdated pricing doc from the Product Docs knowledge base",
 ]} />
 
 Sim runs the same indexing and search described on this page, so anything it creates is immediately usable from the [Knowledge block](/knowledgebase/using-in-workflows) in a workflow.
diff --git a/apps/docs/content/docs/en/tables/index.mdx b/apps/docs/content/docs/en/tables/index.mdx
index 4738b37eeb7..d9db25850c3 100644
--- a/apps/docs/content/docs/en/tables/index.mdx
+++ b/apps/docs/content/docs/en/tables/index.mdx
@@ -41,14 +41,31 @@ A [Table block](/tables/using-in-workflows) reads and writes rows from inside a
 
 Everything on this page can be done by asking Sim in [Chat](/chat): create a table from a description or a CSV, query it in plain language, add or update rows, and export results.
 
-<TryInChat prompts={[
+<TryInChat title="Try in Chat — creating" prompts={[
   "Create a leads table with columns for name, email, company, status, and created date",
+  "Create a table that matches the structure of this CSV (attach the file)",
+  "Set up an enrichment results table to store output from the lead enrichment workflow: email, company, title, LinkedIn URL, fit score",
+]} />
+
+<TryInChat title="Try in Chat — querying" prompts={[
   "How many rows in the leads table have status 'qualified'?",
+  "Show me all records from the past 7 days where score is above 0.8",
+  "Are there any duplicate emails in the contacts table?",
+  "What's the conversion rate from 'contacted' to 'meeting booked' in the pipeline table this month?",
+]} />
+
+<TryInChat title="Try in Chat — updating" prompts={[
+  "Add a row to the leads table: Acme Corp, jane@acme.com, status pending",
   "Mark all rows in the queue table as processed where created_at is before today",
+  "Update the price column for all rows where tier is 'pro' to 49",
+]} />
+
+<TryInChat title="Try in Chat — exporting" prompts={[
+  "Export the leads table to a CSV",
   "Export all rows where status is 'closed' and save as a file",
 ]} />
 
-Sim translates the request into the same operations described above; tables it creates are immediately available to the [Table block](/integrations/table) in any workflow.
+Sim translates each request into the same operations described above, and can query across tables — describe the relationship and what you want. Tables it creates are immediately available to the [Table block](/integrations/table) in any workflow.
 
 ## Next
 

From e2cc50a348920a85aa6c7dac85308fd196ece5ef Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Thu, 11 Jun 2026 11:02:38 -0700
Subject: [PATCH 4/6] docs(introduction): clarity pass on the rewritten intro

Five fixes beneath the rename: the How-you-build callout restated the lead
paragraph and the bullets a third time (cut); the anatomy section opened with
a negative strawman and claimed the sidebar mirrors a list containing
non-sidebar items (positive framing, claim dropped); the Integrations section
was a 25-name prose catalog duplicating the FAQ (now two sentences + the
catalog link; the FAQ keeps the list as its single home); 'Deployment options'
collided with Deployments-the-feature defined a section earlier (now
'Hosting'); the What-you-can-build bullets traded generic categories for
concrete examples.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 apps/docs/content/docs/en/.source/browser.ts  | 24 ++++++++++++++
 apps/docs/content/docs/en/.source/dynamic.ts  | 15 +++++++++
 apps/docs/content/docs/en/.source/server.ts   | 31 +++++++++++++++++++
 .../content/docs/en/.source/source.config.mjs | 19 ++++++++++++
 .../content/docs/en/introduction/index.mdx    | 24 +++++---------
 5 files changed, 96 insertions(+), 17 deletions(-)
 create mode 100644 apps/docs/content/docs/en/.source/browser.ts
 create mode 100644 apps/docs/content/docs/en/.source/dynamic.ts
 create mode 100644 apps/docs/content/docs/en/.source/server.ts
 create mode 100644 apps/docs/content/docs/en/.source/source.config.mjs

diff --git a/apps/docs/content/docs/en/.source/browser.ts b/apps/docs/content/docs/en/.source/browser.ts
new file mode 100644
index 00000000000..858d535642e
--- /dev/null
+++ b/apps/docs/content/docs/en/.source/browser.ts
@@ -0,0 +1,24 @@
+// @ts-nocheck
+/// <reference types="vite/client" />
+import { browser } from 'fumadocs-mdx/runtime/browser'
+import type * as Config from '../source.config'
+
+const create = browser<
+  typeof Config,
+  import('fumadocs-mdx/runtime/types').InternalTypeConfig & {
+    DocData: {}
+  }
+>()
+const browserCollections = {
+  docs: create.doc(
+    'docs',
+    import.meta.glob(['./**/*.{mdx,md}'], {
+      base: './../content/docs',
+      query: {
+        collection: 'docs',
+      },
+      eager: false,
+    })
+  ),
+}
+export default browserCollections
diff --git a/apps/docs/content/docs/en/.source/dynamic.ts b/apps/docs/content/docs/en/.source/dynamic.ts
new file mode 100644
index 00000000000..0bec4e5d379
--- /dev/null
+++ b/apps/docs/content/docs/en/.source/dynamic.ts
@@ -0,0 +1,15 @@
+// @ts-nocheck
+/// <reference types="vite/client" />
+import { dynamic } from 'fumadocs-mdx/runtime/dynamic'
+import * as Config from '../source.config'
+
+const create = await dynamic<
+  typeof Config,
+  import('fumadocs-mdx/runtime/types').InternalTypeConfig & {
+    DocData: {}
+  }
+>(
+  Config,
+  { configPath: 'source.config.ts', environment: 'vite', outDir: '.source' },
+  { doc: { passthroughs: ['extractedReferences'] } }
+)
diff --git a/apps/docs/content/docs/en/.source/server.ts b/apps/docs/content/docs/en/.source/server.ts
new file mode 100644
index 00000000000..94fc2698d8a
--- /dev/null
+++ b/apps/docs/content/docs/en/.source/server.ts
@@ -0,0 +1,31 @@
+// @ts-nocheck
+/// <reference types="vite/client" />
+import { server } from 'fumadocs-mdx/runtime/server'
+import type * as Config from '../source.config'
+
+const create = server<
+  typeof Config,
+  import('fumadocs-mdx/runtime/types').InternalTypeConfig & {
+    DocData: {}
+  }
+>({ doc: { passthroughs: ['extractedReferences'] } })
+
+export const docs = await create.docs(
+  'docs',
+  'content/docs',
+  import.meta.glob(['./**/*.{json,yaml}'], {
+    base: './../content/docs',
+    query: {
+      collection: 'docs',
+    },
+    import: 'default',
+    eager: true,
+  }),
+  import.meta.glob(['./**/*.{mdx,md}'], {
+    base: './../content/docs',
+    query: {
+      collection: 'docs',
+    },
+    eager: true,
+  })
+)
diff --git a/apps/docs/content/docs/en/.source/source.config.mjs b/apps/docs/content/docs/en/.source/source.config.mjs
new file mode 100644
index 00000000000..2e49033207e
--- /dev/null
+++ b/apps/docs/content/docs/en/.source/source.config.mjs
@@ -0,0 +1,19 @@
+// ../../../source.config.ts
+import { defineConfig, defineDocs, frontmatterSchema } from "fumadocs-mdx/config";
+import { z } from "zod";
+var docs = defineDocs({
+  dir: "content/docs",
+  docs: {
+    schema: frontmatterSchema.extend({
+      pageType: z.enum(["tutorial", "guide", "reference", "concept"]).optional()
+    }),
+    postprocess: {
+      includeProcessedMarkdown: true
+    }
+  }
+});
+var source_config_default = defineConfig();
+export {
+  source_config_default as default,
+  docs
+};
diff --git a/apps/docs/content/docs/en/introduction/index.mdx b/apps/docs/content/docs/en/introduction/index.mdx
index 85dcdca2e2c..b953b86665b 100644
--- a/apps/docs/content/docs/en/introduction/index.mdx
+++ b/apps/docs/content/docs/en/introduction/index.mdx
@@ -31,13 +31,10 @@ When you open Sim, the first thing you meet is **Chat**, a conversation over you
 
 You can mix these on one system, scaffolding in Chat and then fine-tuning in the builder.
 
-<Callout type="info">
-Sim generates the architecture, and you verify the execution. Even when you build conversationally, it helps to understand the resources Sim creates, so you can inspect, run, and improve them.
-</Callout>
 
 ## The anatomy of a workspace
 
-A Sim system is not a single chat response. It is a set of resources that live in a **workspace** and connect to each other. The sidebar mirrors that anatomy, and these are its parts.
+A Sim system is a set of resources that live in a **workspace** and connect to each other. These are its parts:
 
 - **[Chat](/chat)** is where you build conversationally. You describe what you want, and Sim builds and edits the resources for you.
 - **[Workflows](/workflows)** are visual programs made of blocks, where your logic runs. Most other resources become useful through a workflow.
@@ -54,25 +51,18 @@ A Sim system is not a single chat response. It is a set of resources that live i
 
 ## What you can build
 
-- **AI assistants and chatbots.** Conversational agents that search the web, manage calendars, send email, and act on your business systems.
-- **Business process automation.** Data entry, report generation, customer responses, and content workflows.
-- **Data processing and analysis.** Extract from documents, analyze datasets, and sync data across platforms.
-- **API integration workflows.** Unified endpoints that orchestrate multi-service logic and event-driven automation.
+- **Assistants and chatbots.** A support agent that answers from your docs, or a Slack bot that searches the web and acts on your systems.
+- **Process automation.** Invoice extraction into a billing table, lead scoring and outreach, weekly report generation.
+- **Data pipelines.** Pull from a CRM, enrich each record with an agent, and write the results back to a table.
+- **Unified APIs.** One endpoint that orchestrates several services and models behind a single call.
 
 ## Integrations
 
-Sim provides native integrations with 1,000+ services:
-
-- **AI models.** OpenAI, Anthropic, Google Gemini, Groq, Cerebras, and local models via Ollama or VLLM.
-- **Communication.** Gmail, Slack, Microsoft Teams, Telegram, WhatsApp.
-- **Productivity.** Notion, Google Workspace, Airtable.
-- **Development.** GitHub, Jira, Linear, automated browser testing.
-- **Search and data.** Google Search, Perplexity, Firecrawl, Exa AI.
-- **Databases.** PostgreSQL, MySQL, Supabase, Pinecone, Qdrant.
+Sim has native integrations with 1,000+ services — every major AI model provider, and the communication, productivity, development, search, and database tools your work already runs on. Browse the full catalog at [Integrations](/integrations).
 
 For anything not built in, [MCP support](/agents/mcp) connects any external service or tool.
 
-## Deployment options
+## Hosting
 
 - **Cloud-hosted.** Launch immediately at [sim.ai](https://sim.ai) with managed infrastructure, scaling, and observability.
 - **Self-hosted.** Deploy on your own infrastructure with Docker Compose or Kubernetes, with support for local models.

From 1997988da2b5be075010b9e2298c95cb0899dac5 Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Thu, 11 Jun 2026 16:54:49 -0700
Subject: [PATCH 5/6] docs(platform): organization page sized to the feature;
 Workspaces titled plainly
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The folders page documented Name, Color, Nesting, and Order as individual
sections — reference-grade taxonomy for self-evident desktop-folder behavior.
Now one paragraph covers the basics, the two actions that genuinely do
something (locking, archiving) keep their substance, conventions compress to
one sentence-group, and the folders-vs-workspaces decision — the page's
actually useful part — stays intact. 78 lines -> 38.

/platform/workspaces was titled 'Workspace fundamentals'; it's 'Workspaces'.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .../content/docs/en/platform/organization.mdx | 65 ++++---------------
 .../content/docs/en/platform/workspaces.mdx   |  2 +-
 2 files changed, 12 insertions(+), 55 deletions(-)

diff --git a/apps/docs/content/docs/en/platform/organization.mdx b/apps/docs/content/docs/en/platform/organization.mdx
index cbf534bf533..e829311f50a 100644
--- a/apps/docs/content/docs/en/platform/organization.mdx
+++ b/apps/docs/content/docs/en/platform/organization.mdx
@@ -1,78 +1,35 @@
 ---
 title: Organizing a workspace
-description: Folders, colors, and naming conventions for keeping a growing workspace understandable.
+description: Folders group workflows in the sidebar; a separate workspace draws a hard boundary.
 pageType: concept
 ---
 
 import { Card, Cards } from 'fumadocs-ui/components/card'
 
-A **folder** is a container in the sidebar that groups workflows. It is the primary way you organize a [workspace](/platform/workspaces) once it holds more than a handful of workflows. Folders work like folders in a desktop file system: they nest, they collapse, and you arrange them by convention so the structure tells you where things live.
+A **folder** groups workflows in the sidebar. Folders work like folders anywhere: they nest, they collapse, you drag them to reorder or to move one inside another, and each has a name and a color dot for at-a-glance grouping. A flat list of twenty workflows is hard to scan; the same twenty under three or four top-level folders is a map.
 
-A flat list of twenty workflows is hard to scan, but grouping the same twenty under three or four top-level folders gives you a map of where everything lives.
+{/* VISUAL: before/after sidebar. Left: a flat list of ~20 workflows. Right: the same workflows under 3-4 color-coded top-level folders, one expanded to show a subfolder. */}
 
-{/* VISUAL: before/after sidebar. Left: a flat list of ~20 workflows, no grouping. Right: the same workflows under 3-4 top-level color-coded folders ("Internal", "Customer-Facing", "Ops"), some expanded to show nested subfolders. */}
+Two folder actions do more than tidy up:
 
-## The parts of a folder
+- **Locking** makes a folder read-only — its workflows can be viewed and run but not edited, and locking a parent locks everything inside it. Lock `Production` so nobody edits a live workflow by accident. Who can lock follows [roles and permissions](/platform/permissions).
+- **Archiving** removes a folder from the sidebar without deleting it, and you can restore it later. There is no hard-delete in the folder menu, so archiving is the safe way to retire a finished engagement or an old experiment.
 
-Here's an example: a folder named **Customer Deployments**, colored red, holding five workflows and two subfolders.
+{/* VISUAL: the folder context menu open on a folder row: rename, change color, lock, duplicate, export, new subfolder, delete. */}
 
-### Name
-
-A **name** is the label you give a folder. It is plain text with no enforced format, so the convention is yours to set. Pick names that read as categories, not as one-off labels: `Internal`, `Customer-Facing`, `Ops`. Our example folder is named `Customer Deployments`. Naming is covered in [Conventions](#conventions) below.
-
-{/* VISUAL: a single sidebar folder row showing the expand chevron, color dot, and name "Customer Deployments". */}
-
-### Color
-
-A **color** is a hex value assigned to a folder for visual grouping, shown as a dot next to the name. It defaults to gray (`#6B7280`) and you can change it from the folder's menu. Color is the fastest way to read the sidebar at a glance. Reserve one color per top-level category (red for production, gray for scratch work) so you can find the right branch before reading a single name. Our example is red (`#EF4444`).
-
-{/* VISUAL: a short vertical stack of folders with distinct color dots: red "Production", gray "Internal", another color for "Customer-Facing", showing color as the grouping signal. */}
-
-### Nesting
-
-A folder can sit inside another folder. The inner one is a **subfolder**, and the structure is a tree: a top-level folder has no parent, a subfolder points at the folder that contains it, and that chain can go as deep as you need. Our example, `Customer Deployments`, holds two subfolders and itself sits under a `Production` folder.
-
-Lead with shallow trees. Two or three levels (`Production` > `Customer A` > `Deployments`) stay readable. Go deeper than that and you end up scrolling the sidebar instead of scanning it.
-
-{/* VISUAL: a three-level nested tree: "Production" (red, top level) > "Customer A" (yellow) > "Deployments" (purple), each row indented one step, showing the parent-to-child chain. */}
-
-### Order
-
-Folders display in a set **order**, top to bottom, that you control by dragging them in the sidebar. Drag a folder up or down to reorder it within its level, or drag it onto another folder to move it inside as a subfolder. Order is a convention too: put the folders a team touches daily at the top.
-
-### Locking
-
-A **locked** folder is read-only: its workflows can be viewed but not edited. Locking is off by default. Lock a `Production` folder so members can open and run its workflows without changing them by accident. Locking a folder also locks everything inside it, so a locked parent protects its subfolders and their workflows in one move. Who can lock and unlock follows the workspace [roles and permissions](/platform/permissions).
-
-{/* VISUAL: the folder context menu open on a folder row, showing the options: rename, change color, lock, duplicate, export, new subfolder, delete. */}
-
-### Archiving
-
-**Archiving** a folder removes it from your active sidebar without deleting it. An archived folder drops out of the normal view, and you restore it when you need it again. Use archiving for cleanup: a finished customer engagement or a retired experiment leaves the sidebar but stays recoverable. There is no permanent hard-delete in the folder menu, so archiving is the safe way to get something out of the way.
-
-## Conventions
-
-Naming conventions make the structure legible to someone who did not build it. Nothing here is enforced, so the value comes from applying one rule consistently across the workspace.
-
-- **Group by audience or function at the top level.** A common split is `Internal`, `Customer-Facing`, and `Ops`. Someone new can find the right branch from the top-level names alone.
-- **Name folders as categories, workflows as actions.** A folder is a noun (`Billing`); a workflow is a thing it does (`Send overdue reminder`). The folder path plus the workflow name should read as a sentence.
-- **Use color for the top level, names for everything below.** Color carries the coarse grouping; names carry the detail. Mixing both at every level turns into noise.
-- **Mirror the convention everywhere.** The same category words you use for folders are worth reusing for [tables](/platform/workspaces), [secrets](/platform/credentials), and [integrations](/integrations), so a team learns one vocabulary instead of three.
+Keep the structure legible: name folders as categories (`Internal`, `Customer-Facing`, `Ops`) and workflows as actions (`Send overdue reminder`), keep nesting to two or three levels, and reuse the same category words across tables, secrets, and integrations so the team learns one vocabulary.
 
 ## One workspace or several
 
-Folders organize within a workspace. A separate workspace draws a hard boundary: resources never cross it, and access is granted per workspace. Reach for a new workspace when you need that boundary, not just tidier grouping.
+Folders organize within a workspace. A separate [workspace](/platform/workspaces) draws a hard boundary: resources never cross it, and access is granted per workspace.
 
 - **Group in folders** when everything belongs to the same team and the same access rules, and you only want it easier to navigate.
-- **Split into workspaces** when a set of work needs its own members, its own integrations and secrets, or its own isolation. The classic case is one workspace per customer, where the workspace itself is the deliverable the customer owns.
-
-See [Workspace fundamentals](/platform/workspaces) for what the boundary scopes and [Roles and permissions](/platform/permissions) for how members and seats work across workspaces.
+- **Split into workspaces** when a set of work needs its own members, integrations, secrets, or isolation. The classic case is one workspace per customer, where the workspace itself is the deliverable the customer owns.
 
 ## Next
 
 <Cards>
-  <Card title="Workspace fundamentals" href="/platform/workspaces" description="What a workspace holds and the boundary it scopes." />
+  <Card title="Workspaces" href="/platform/workspaces" description="What a workspace holds and the boundary it scopes." />
   <Card title="Roles and permissions" href="/platform/permissions" description="Permission levels, members, and seat rules." />
   <Card title="Secrets" href="/platform/credentials" description="Workspace and personal API keys and variables." />
-  <Card title="Integrations" href="/integrations" description="Connect third-party accounts to a workspace." />
 </Cards>
diff --git a/apps/docs/content/docs/en/platform/workspaces.mdx b/apps/docs/content/docs/en/platform/workspaces.mdx
index bdb3529eae9..3209d0ff64f 100644
--- a/apps/docs/content/docs/en/platform/workspaces.mdx
+++ b/apps/docs/content/docs/en/platform/workspaces.mdx
@@ -1,5 +1,5 @@
 ---
-title: Workspace fundamentals
+title: Workspaces
 description: A workspace holds your workflows and resources and decides who can access them.
 pageType: concept
 ---

From 661112da2c31e852fc4a8dcbfbfbe9e2037ae84a Mon Sep 17 00:00:00 2001
From: William Chen <wchen298@gmail.com>
Date: Thu, 11 Jun 2026 17:00:56 -0700
Subject: [PATCH 6/6] =?UTF-8?q?docs(files):=20generating.mdx=20accuracy=20?=
 =?UTF-8?q?=E2=80=94=20operation=20names=20and=20cards?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Same V5-operation slip as using-in-workflows had (fixed in #4896): there is no
'Get' operation — Read returns workspace file objects (not 'parsed files'),
Get Content returns text. Cards fixed: 'Using files in workflows' pointed at
passing-files, 'File block' pointed at the /files overview with the wrong
operation set — now /integrations/file with the real five. Verified accurate
while auditing: ElevenLabs audioFile output, write-time content-type detection
(manage/route.ts:351), Files panel categories, dedup suffix behavior.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 apps/docs/content/docs/en/files/generating.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/apps/docs/content/docs/en/files/generating.mdx b/apps/docs/content/docs/en/files/generating.mdx
index 9fdb8fe1284..9bff3c3e3e7 100644
--- a/apps/docs/content/docs/en/files/generating.mdx
+++ b/apps/docs/content/docs/en/files/generating.mdx
@@ -19,7 +19,7 @@ Most generated files start as the output of an earlier block. Two patterns are c
 
 A block returns **text content** you want to keep. An [Agent](/workflows/blocks/agent) writes an analysis or summary; a [Function](/workflows/blocks/function) builds a CSV or formats a report. That text is part of the block's output, read by reference as `<agent.content>` or `<function.result>`. To make it a file, you pass that value into a File block set to Write.
 
-A block returns a **file object** directly. ElevenLabs text-to-speech returns an `audioFile`; an image generator returns a generated image; the File block's own Read operation returns parsed files. These are already [UserFile](/files/passing-files) objects (an object with `id`, `name`, `url`, `size`, and `type`), so they appear in the output panel as files with no Write step. You can hand one to a downstream block, or write its content to the Files store to persist it.
+A block returns a **file object** directly. ElevenLabs text-to-speech returns an `audioFile`; an image generator returns a generated image; the File block's own Read operation returns workspace file objects. These are already [UserFile](/files/passing-files) objects (an object with `id`, `name`, `url`, `size`, and `type`), so they appear in the output panel as files with no Write step. You can hand one to a downstream block, or write its content to the Files store to persist it.
 
 <Callout type="info">
 A block's output is remembered under the block's name for the rest of the run, and a later block reads it by key, like `<elevenlabs.audioFile>` or `<agent.content>`. Producing content and saving it are two separate steps: the producing block holds the value, the File block persists it.
@@ -48,7 +48,7 @@ A saved file lands in the workspace [Files](/files) store, the same place upload
 
 {/* VISUAL: Files panel UI: generated files listed with name, size, type icon, owner, modified date, folder */}
 
-Files are scoped to the workspace, not to one workflow. A file written by one workflow is visible to every other workflow in the same workspace. Any later run can read it back with the File block's Read or Get operation, or by selecting it in a file picker.
+Files are scoped to the workspace, not to one workflow. A file written by one workflow is visible to every other workflow in the same workspace. Any later run can read it back with the File block — Read for the file object, Get Content for its text — or by selecting it in a file picker.
 
 During a run, the file also appears in the output panel as the File block's output, shown as a structured object with its `id`, `name`, `url`, and `size`. The output panel shows you one run as it happens, while the Files store is where the file stays afterward.
 
@@ -62,7 +62,7 @@ When a workflow is deployed as an [API](/workflows/deployment/api), a generated
 
 <Cards>
   <Card title="Files overview" href="/files" description="The artifact layer of your workspace." />
-  <Card title="Using files in workflows" href="/files/passing-files" description="Provide files to a workflow and receive files back." />
-  <Card title="File block" href="/files" description="Read, Get, Write, and Append operations in full." />
+  <Card title="Using files in workflows" href="/files/using-in-workflows" description="Read a file's contents, pass files between blocks, and write results." />
+  <Card title="File block reference" href="/integrations/file" description="Read, Get Content, Fetch, Write, and Append in full." />
   <Card title="API deployment" href="/workflows/deployment/api" description="Expose a workflow as an API and return file references." />
 </Cards>