dappnode · Marketen · Jun 30, 2026 · Jun 30, 2026
diff --git a/docs/dev/package-development/agent-assisted-development.md b/docs/dev/package-development/agent-assisted-development.md
@@ -1,39 +1,29 @@
 ---
 title: "Agent-assisted package development"
-llm_description: "Use Dappmanager v0.2.125 Nexus chat and DAppNode MCP tools to develop, validate, upload, and install packages with coding agents."
+llm_description: "Use Dappmanager MCP tools to develop, validate, upload, install, and debug Dappnode packages with external coding agents."
 ---
 
 # Agent-assisted package development
 
-[Dappmanager v0.2.125](https://github.com/dappnode/DNP_DAPPMANAGER/releases/tag/v0.2.125), published on June 29, 2026, added **Nexus chat** and a **DAppNode MCP server**. Together they let operators and developers use AI agents with live Dappnode context: installed packages, logs, diagnostics, docs search, package validation, registry previews, and development-package installation.
+[Dappmanager v0.2.125](https://github.com/dappnode/DNP_DAPPMANAGER/releases/tag/v0.2.125), published on June 29, 2026, added a **DAppNode MCP server**. It lets external MCP-capable coding agents use live Dappnode context for package development: installed packages, logs, diagnostics, docs search, package validation, registry previews, and development-package installation.
 
-Nexus chat is built into the Dappmanager UI. External agent clients can use the same Dappnode tools through the MCP endpoint at `/mcp`.
+External agent clients connect to Dappmanager through the MCP endpoint at `/mcp`.
+
+:::info
+This page is for developers and power users who want to connect an external MCP client to Dappmanager. For the built-in Dappmanager chat, see [Nexus Chat](/docs/user/nexus-chat.md).
+:::
 
 ## Requirements
 
 - Dappmanager `v0.2.125` or newer.
 - Admin access to the Dappmanager UI.
-- A private connection to your Dappnode, such as Wireguar VPN or Tailscale.
-- For Nexus chat, a Nexus API key from [nexus.dappnode.com](https://nexus.dappnode.com).
-- For external MCP clients, a DAppNode MCP API key generated in the Dappmanager UI.
+- A private connection to your Dappnode, such as WireGuard VPN or Tailscale.
+- A DAppNode MCP API key generated in the Dappmanager UI.
 
 :::note
-The Nexus API key and the DAppNode MCP API key are different keys. The Nexus API key lets the built-in chat talk to Nexus. The DAppNode MCP API key lets external MCP clients authenticate to your Dappnode's `/mcp` endpoint.
+The DAppNode MCP API key is different from the Nexus API key used by Nexus Chat. The MCP API key lets external MCP clients authenticate to your Dappnode's `/mcp` endpoint.
 :::
 
-## Use Nexus chat
-
-Open **Nexus** from the Dappmanager sidebar. On first use, paste a Nexus API key. The key is stored on your Dappnode and used by the Dappmanager backend to talk to Nexus.
-
-You can use Nexus chat to:
-
-- Ask questions about your Dappnode using installed-package context.
-- Search and summarize Dappnode docs from the chat.
-- Inspect package status, logs, system info, notifications, updates, disk usage, and ports.
-- Start workflows that need confirmation, such as package changes.
-
-When a chat action can change package state, Dappmanager asks for confirmation before the action runs.
-
 ## Connect an external MCP client
 
 External MCP clients such as coding agents connect to the Dappmanager MCP server with a bearer token.
@@ -57,7 +47,7 @@ External MCP clients such as coding agents connect to the Dappmanager MCP server
 
 Use the same origin you use to access Dappmanager.
 
-Read-only MCP tools are available by default. To let external clients run package-changing tools, enable **Allow mutating MCP tools** in the same **System > Advanced > MCP API key** section. Disable it again when you are done with the agent workflow.
+Read-only MCP tools are available by default. To let external clients run package-changing tools, enable **Allow mutating MCP tools** in the same **System > Advanced > MCP API key** section. Disable it again when you are done with the development workflow.
 
 ## What agents can do
 

diff --git a/docs/dev/package-development/overview.md b/docs/dev/package-development/overview.md
@@ -16,7 +16,7 @@ There are two main types of package repositories:
 
 ### Developing Packages
 
-- **Agent-assisted development**: If you want to use Nexus chat or an external MCP-capable coding agent to validate, upload, install, and debug packages on a Dappnode, follow the guide [here](/docs/dev/package-development/agent-assisted-development.md).
+- **Agent-assisted development**: If you want to use an external MCP-capable coding agent to validate, upload, install, and debug packages on a Dappnode, follow the guide [here](/docs/dev/package-development/agent-assisted-development.md).
 - **Single-Configuration Package**: If you want to develop a package with a single configuration, like [Rotki](https://github.com/dappnode/DAppNodePackage-rotki), follow the instructions [here](/docs/dev/package-development/single-configuration.md).
 - **Multi-Configuration Package**: For packages with multiple configurations, like [Lodestar](https://github.com/dappnode/DAppNodePackage-lodestar-generic), refer to [this guide](/docs/dev/package-development/multi-configuration.md).
 

diff --git a/docs/user/nexus-chat.md b/docs/user/nexus-chat.md
@@ -0,0 +1,46 @@
+---
+title: "Nexus Chat"
+llm_description: "Use Nexus chat in Dappmanager to ask questions, inspect Dappnode status, search docs, review logs, and start confirmed package workflows."
+---
+
+# Nexus Chat
+
+**Nexus chat** is built into the Dappmanager UI. It lets you ask questions about your Dappnode and use live Dappnode context, such as installed packages, logs, diagnostics, updates, disk usage, ports, notifications, and Dappnode docs.
+
+Nexus chat is available in Dappmanager `v0.2.125` and newer.
+
+## Requirements
+
+- Dappmanager `v0.2.125` or newer.
+- Admin access to the Dappmanager UI.
+- A private connection to your Dappnode, such as WireGuard VPN or Tailscale.
+- A Nexus API key from [nexus.dappnode.com](https://nexus.dappnode.com).
+
+## Open Nexus chat
+
+1. Open Dappmanager.
+2. Select **Nexus** from the sidebar.
+3. On first use, paste your Nexus API key.
+
+The Nexus API key is stored on your Dappnode and used by the Dappmanager backend to talk to Nexus.
+
+After setup, Nexus opens to an empty conversation with suggested prompts:
+
+![Nexus chat empty conversation screen after API key setup](/img/nexus-chat.png)
+
+## What you can ask
+
+You can use Nexus chat to:
+
+- Ask questions about your Dappnode using installed-package context.
+- Search and summarize Dappnode docs from the chat.
+- Inspect package status, logs, system information, notifications, updates, disk usage, and ports.
+- Start workflows that need confirmation, such as package changes.
+
+When a chat action can change package state, Dappmanager asks for confirmation before the action runs.
+
+## Nexus API key vs MCP API key
+
+The Nexus API key is only for the built-in chat in Dappmanager.
+
+Developers and power users who want to connect external MCP-capable coding agents to Dappmanager need a separate DAppNode MCP API key. For that workflow, see [Agent-assisted package development](/docs/dev/package-development/agent-assisted-development.md).
diff --git a/sidebars.js b/sidebars.js
@@ -547,6 +547,11 @@ const sidebars = {
         },
       ],
     },
+    {
+      type: "doc",
+      label: "Nexus Chat",
+      id: "user/nexus-chat",
+    },
     {
       type: "doc",
       label: "UI Telemetry",

diff --git a/static/img/nexus-chat.png b/static/img/nexus-chat.png