From b29e7af0b88826435e43fe4d0c415bd0b0d2daac Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:36:55 -0400 Subject: [PATCH 1/9] docs: explain saved MCP servers in web chat --- .../connections-and-mcp.mdx | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index f7120fb..a8cf277 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -14,11 +14,27 @@ Select **Connections** in the app sidebar. The page lives at `//connections` and has two tabs: - **Integrations** contains service presets, saved connections, the custom connection form, and Slack setup. -- **MCP Servers** manages server definitions that sync with the Mogplex CLI. +- **MCP Servers** manages saved servers for web chat and the Mogplex CLI. The MCP Servers tab uses `//connections?tab=mcp`. Reloads and browser Back preserve the selected tab. +### Use a saved server in web chat + +Choose **Add server** and leave **Streamable HTTP** selected. Enter the server URL and any required headers. +Save the server with **Enabled** on. Its tools become available on the next web chat or Control turn without a separate Integration. +The server must support Streamable HTTP and have a public URL. Saved secret headers stay on the server. + +**Local (CLI only)** uses stdio to start a process on your computer. +Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. + +Disable or delete a saved server to exclude its tools from subsequent turns. +Team capability checks still apply. Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. +Tools with an explicit `prompt` approval mode require Control, which can ask before a call. Other chat surfaces withhold them. + +Without an explicit approval mode, saved tools run automatically, like Integrations in web chat. +CLI approval defaults remain unchanged. Other CLI-specific extra options do not configure web chat. + Connections belong to your personal account. Shared team connections are not available yet. In a team scope, select **Open personal connections** to manage your own services. From 1e0fd57f5ced84a3f30d1ac50bc5aa66eac78834 Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:41:50 -0400 Subject: [PATCH 2/9] docs: clarify saved catalog scope across agent surfaces --- content/docs/configure-and-extend/connections-and-mcp.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index a8cf277..eda9124 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -158,6 +158,9 @@ or REST APIs that do not have a preset yet. The Control row is the coordinator, the agent you talk to. A worker it delegates to is a sandbox run, so it follows the row for its harness. +Enabled public HTTP servers from **MCP Servers** also load in Control, workspace chat, the Slack agent, and native-harness runs. +These saved servers belong to the user and apply across repos. Integration scope exclusions do not apply to this separate catalog. + Control waits up to eight seconds for remote MCP servers when a turn starts. If one is slow or down, the turn runs without connection tools instead of hanging. @@ -195,7 +198,8 @@ for the full operating model. ## MCP limits -Mogplex caps enabled MCP server connections at five per resolved scope. +Mogplex caps enabled MCP server connections from **Integrations** at five per resolved scope. +This existing cap does not apply to the **MCP Servers** catalog. The cap protects runs from receiving an oversized or noisy tool surface. If a repo reaches the cap, decide whether to: From 150f61902c5342e80f850924621daacc255399c8 Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:43:19 -0400 Subject: [PATCH 3/9] docs: align settings guidance with MCP web chat support --- .../connections-and-mcp.mdx | 32 +++++++++++-------- content/docs/web/settings.mdx | 4 +-- 2 files changed, 20 insertions(+), 16 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index eda9124..07e370d 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -1,6 +1,6 @@ --- title: External connections -description: Configure external REST and MCP connections, understand scope resolution, sync saved server definitions, and distinguish them from the Mogplex MCP endpoint. +description: Configure external tools, use saved MCP servers in web chat and the CLI, and understand connection scope and permissions. --- Connections are how Mogplex agents reach external systems. @@ -19,7 +19,16 @@ Select **Connections** in the app sidebar. The page lives at The MCP Servers tab uses `//connections?tab=mcp`. Reloads and browser Back preserve the selected tab. -### Use a saved server in web chat +Connections belong to your personal account. Shared team connections are not +available yet. In a team scope, select **Open personal connections** to manage +your own services. + +Old Settings links with `?tab=connections` or `#connections` still work. +OAuth and Slack return messages follow the redirect to the new page. +The old `//settings/mcp` page and Settings links with `?tab=mcp` or +`#mcp` open the MCP Servers tab. + +## Use a saved server in web chat Choose **Add server** and leave **Streamable HTTP** selected. Enter the server URL and any required headers. Save the server with **Enabled** on. Its tools become available on the next web chat or Control turn without a separate Integration. @@ -29,21 +38,16 @@ The server must support Streamable HTTP and have a public URL. Saved secret head Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. Disable or delete a saved server to exclude its tools from subsequent turns. -Team capability checks still apply. Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. -Tools with an explicit `prompt` approval mode require Control, which can ask before a call. Other chat surfaces withhold them. +The team's `connections.create` capability still controls access to these tools. +Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. +Tools with an explicit `prompt` approval mode require Control, which can ask before a call. +Workspace chat, the Slack agent, and native-harness runs withhold these tools because they cannot ask. + +The **Integrations** approval menu applies only to Integration entries. Saved servers use their own **Extra JSON** settings. Without an explicit approval mode, saved tools run automatically, like Integrations in web chat. CLI approval defaults remain unchanged. Other CLI-specific extra options do not configure web chat. -Connections belong to your personal account. Shared team connections are not -available yet. In a team scope, select **Open personal connections** to manage -your own services. - -Old Settings links with `?tab=connections` or `#connections` still work. -OAuth and Slack return messages follow the redirect to the new page. -The old `//settings/mcp` page and Settings links with `?tab=mcp` or -`#mcp` open the MCP Servers tab. - ## Direction matters There are three MCP-related surfaces with different directionality: @@ -161,7 +165,7 @@ to is a sandbox run, so it follows the row for its harness. Enabled public HTTP servers from **MCP Servers** also load in Control, workspace chat, the Slack agent, and native-harness runs. These saved servers belong to the user and apply across repos. Integration scope exclusions do not apply to this separate catalog. -Control waits up to eight seconds for remote MCP servers when a turn starts. If +Control waits up to eight seconds for remote MCP servers, including saved servers, when a turn starts. If one is slow or down, the turn runs without connection tools instead of hanging. ## Asking before a connection's tools run diff --git a/content/docs/web/settings.mdx b/content/docs/web/settings.mdx index 20c07a9..3f8ace5 100644 --- a/content/docs/web/settings.mdx +++ b/content/docs/web/settings.mdx @@ -76,7 +76,7 @@ actually support them. - **Billing** contains **Billing Settings** and **Usage**. **Models** and **Connections** have their own sidebar destinations. -Open **Connections → MCP Servers** to manage server definitions for CLI sync. +Open **Connections → MCP Servers** to manage saved servers for web chat and the CLI. For model setup, see [Available Models](/web/models). For the connection-specific operating guide, see @@ -187,7 +187,7 @@ work?** Open **Connections** from the app sidebar to add or manage external services. This page now lives at `//connections`, outside Settings. -Use **Integrations** for services and **MCP Servers** for CLI server definitions. +Use **Integrations** for services and **MCP Servers** for saved servers in web chat and the CLI. The MCP Servers tab has a direct link at `//connections?tab=mcp`. Old Settings links still redirect to it. From ad203447a321c2a2891e2c6416b25585856e9e23 Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:54:29 -0400 Subject: [PATCH 4/9] docs: describe saved MCP startup deadlines --- content/docs/configure-and-extend/connections-and-mcp.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index 07e370d..ac486bb 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -167,6 +167,8 @@ These saved servers belong to the user and apply across repos. Integration scope Control waits up to eight seconds for remote MCP servers, including saved servers, when a turn starts. If one is slow or down, the turn runs without connection tools instead of hanging. +Saved-server discovery in workspace chat also uses an eight-second startup budget. +A server that misses that deadline is left out. The deadline does not cancel later tool calls on servers that loaded successfully. ## Asking before a connection's tools run From e9096d7c2348dd33fb85f856075e1757d3487585 Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:57:30 -0400 Subject: [PATCH 5/9] docs: distinguish Integration and saved MCP runtime coverage --- .../connections-and-mcp.mdx | 28 +++++++++++-------- .../guides/connection-scope-and-overrides.mdx | 3 ++ 2 files changed, 20 insertions(+), 11 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index ac486bb..ecae7b2 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -30,6 +30,8 @@ The old `//settings/mcp` page and Settings links with `?tab=mcp` or ## Use a saved server in web chat +Here, web chat means workspace chat and Control in the app. + Choose **Add server** and leave **Streamable HTTP** selected. Enter the server URL and any required headers. Save the server with **Enabled** on. Its tools become available on the next web chat or Control turn without a separate Integration. The server must support Streamable HTTP and have a public URL. Saved secret headers stay on the server. @@ -38,7 +40,7 @@ The server must support Streamable HTTP and have a public URL. Saved secret head Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. Disable or delete a saved server to exclude its tools from subsequent turns. -The team's `connections.create` capability still controls access to these tools. +Servers remain personal. When a turn runs in team scope, the caller also needs the team's `connections.create` capability. Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. Tools with an explicit `prompt` approval mode require Control, which can ask before a call. Workspace chat, the Slack agent, and native-harness runs withhold these tools because they cannot ask. @@ -152,17 +154,17 @@ or REST APIs that do not have a preset yet. ## Where connection tools load -| Surface | Connection tools | -| --- | --- | -| Control's coordinator | Every enabled connection in scope for the selected repo. | -| Workspace chat, Slack agent, native-harness runs | The same set. | -| Claude Code sandbox runs, Mogplex CLI | MCP connections, synced as MCP config. | -| Codex sandbox runs | None yet. | +| Surface | Integrations | Saved MCP Servers | +| --- | --- | --- | +| Control's coordinator | Enabled connections in scope for the selected repo. | Enabled public HTTP servers, with approval cards when requested. | +| Workspace chat, Slack agent, native-harness runs | The same connection set. | Enabled public HTTP servers, except tools that require a prompt. | +| Claude Code sandbox runs | MCP connections, supplied as MCP config. | Not loaded from this catalog. | +| Mogplex CLI | MCP connections, synced as MCP config. | Enabled HTTP and stdio servers through catalog sync. | +| Codex sandbox runs | None yet. | None yet. | The Control row is the coordinator, the agent you talk to. A worker it delegates to is a sandbox run, so it follows the row for its harness. -Enabled public HTTP servers from **MCP Servers** also load in Control, workspace chat, the Slack agent, and native-harness runs. These saved servers belong to the user and apply across repos. Integration scope exclusions do not apply to this separate catalog. Control waits up to eight seconds for remote MCP servers, including saved servers, when a turn starts. If @@ -172,7 +174,9 @@ A server that misses that deadline is left out. The deadline does not cancel lat ## Asking before a connection's tools run -By default a connection's tools run without asking, on every surface. You can +This section describes **Integrations**. For saved MCP Servers, use the [Extra JSON permissions described above](#use-a-saved-server-in-web-chat). + +By default, tools from Integrations run without asking. You can change that per connection: open the connection's menu in **Connections** (or the `auto` control on a row in the Connections pane) and choose **Ask before running tools**. The row then shows `asks first`. @@ -255,8 +259,10 @@ Use `/mcp` in the CLI to inspect MCP state during a session. | Symptom | Check | | --- | --- | -| Tool missing in a hosted run | Confirm the connection is enabled and included in the repo's resolved set. | -| Tool works globally but not in one repo | Check for a project exclusion or a project-specific connection cap. | +| Integration tool missing in a hosted run | Confirm the connection is enabled and included in the repo's resolved set. | +| Saved MCP tool missing in web chat | Confirm Enabled is on, the URL is public, and the server supports Streamable HTTP. Check saved tool restrictions and the startup deadline. | +| Saved MCP tool needs approval | Use Control for tools with an explicit `prompt` approval mode. Other hosted chat surfaces withhold them. | +| Integration tool works globally but not in one repo | Check for a project exclusion or a project-specific connection cap. | | CLI does not show cloud MCP servers | Confirm CLI token login, then inspect `/mcp` and the remote cache file. | | OAuth preset stopped working | Reconnect it from Connections and retest before changing prompts. | | MCP response leaks secrets in logs | Rotate the exposed credential and stop logging MCP config output. | diff --git a/content/docs/web/guides/connection-scope-and-overrides.mdx b/content/docs/web/guides/connection-scope-and-overrides.mdx index 06ad054..833f9a5 100644 --- a/content/docs/web/guides/connection-scope-and-overrides.mdx +++ b/content/docs/web/guides/connection-scope-and-overrides.mdx @@ -5,6 +5,9 @@ description: Understand when a connection should be global, project-scoped, or e Connections in Mogplex are not just account-wide settings. +This guide covers **Integrations**. The separate **MCP Servers** catalog applies across repos and does not use project exclusions. +See [saved servers in web chat](/configure-and-extend/connections-and-mcp#use-a-saved-server-in-web-chat) for that catalog's permissions and availability. + They resolve at two levels: - **Global** connections are available everywhere by default. From 16a90d4cb5469afb881536948b9507c740187d43 Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:58:25 -0400 Subject: [PATCH 6/9] docs: clarify MCP credential handling and catalog capacity --- content/docs/configure-and-extend/connections-and-mcp.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index ecae7b2..9322c44 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -34,7 +34,8 @@ Here, web chat means workspace chat and Control in the app. Choose **Add server** and leave **Streamable HTTP** selected. Enter the server URL and any required headers. Save the server with **Enabled** on. Its tools become available on the next web chat or Control turn without a separate Integration. -The server must support Streamable HTTP and have a public URL. Saved secret headers stay on the server. +The server must support Streamable HTTP and have a public URL. +Saved secret headers stay hidden in the browser. Mogplex sends them to the configured MCP server when it connects. **Local (CLI only)** uses stdio to start a process on your computer. Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. @@ -209,7 +210,7 @@ for the full operating model. ## MCP limits Mogplex caps enabled MCP server connections from **Integrations** at five per resolved scope. -This existing cap does not apply to the **MCP Servers** catalog. +The **MCP Servers** catalog has no server-count cap. The cap protects runs from receiving an oversized or noisy tool surface. If a repo reaches the cap, decide whether to: From bfc428d9d5412aa82d256320fbaf4469d7ac282c Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 14:08:16 -0400 Subject: [PATCH 7/9] docs: explain saved MCP tool policy and team access --- .../connections-and-mcp.mdx | 22 +++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index 9322c44..213bdd5 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -41,7 +41,7 @@ Saved secret headers stay hidden in the browser. Mogplex sends them to the confi Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. Disable or delete a saved server to exclude its tools from subsequent turns. -Servers remain personal. When a turn runs in team scope, the caller also needs the team's `connections.create` capability. +Servers remain personal. In team scope, owners, admins, and developers can use them. Viewers cannot use connection tools. Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. Tools with an explicit `prompt` approval mode require Control, which can ask before a call. Workspace chat, the Slack agent, and native-harness runs withhold these tools because they cannot ask. @@ -51,6 +51,24 @@ The **Integrations** approval menu applies only to Integration entries. Saved se Without an explicit approval mode, saved tools run automatically, like Integrations in web chat. CLI approval defaults remain unchanged. Other CLI-specific extra options do not configure web chat. +For example, this **Extra JSON** allows `search` and `publish`, blocks `delete`, and asks before `publish` in Control. +Replace these example names with the tool names your server exposes. + +```json +{ + "enabled_tools": ["search", "publish", "delete"], + "disabled_tools": ["delete"], + "default_tools_approval_mode": "auto", + "tools": { + "publish": { "approval_mode": "prompt" } + } +} +``` + +The allowlist limits which tools can load. The blocklist and per-tool `enabled: false` exclude tools even if the allowlist includes them. +A per-tool approval mode overrides the default. `auto` and `approve` both allow automatic calls. +Per-tool `deny` excludes a tool. `prompt` requires a Control approval card and withholds the tool on other web chat surfaces. + ## Direction matters There are three MCP-related surfaces with different directionality: @@ -170,7 +188,7 @@ These saved servers belong to the user and apply across repos. Integration scope Control waits up to eight seconds for remote MCP servers, including saved servers, when a turn starts. If one is slow or down, the turn runs without connection tools instead of hanging. -Saved-server discovery in workspace chat also uses an eight-second startup budget. +Saved-server discovery uses a six-second startup budget, leaving time to return healthy tools before Control's deadline. A server that misses that deadline is left out. The deadline does not cancel later tool calls on servers that loaded successfully. ## Asking before a connection's tools run From 6241423e4460b42e7d74df9866b7a04532461e6f Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 14:14:41 -0400 Subject: [PATCH 8/9] docs: clarify personal MCP scope and approval defaults --- content/docs/configure-and-extend/connections-and-mcp.mdx | 6 ++++-- content/docs/web/guides/connection-scope-and-overrides.mdx | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index 213bdd5..19d178b 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -41,7 +41,7 @@ Saved secret headers stay hidden in the browser. Mogplex sends them to the confi Local HTTP addresses also remain CLI-only. Web chat cannot reach your computer's local servers. Disable or delete a saved server to exclude its tools from subsequent turns. -Servers remain personal. In team scope, owners, admins, and developers can use them. Viewers cannot use connection tools. +Servers stay private to the account that created them. In team scope, owners, admins, and developers can use their own saved servers. Viewers cannot use connection tools. Saved `enabled_tools`, `disabled_tools`, and per-tool restrictions in **Extra JSON** also apply to chat. Tools with an explicit `prompt` approval mode require Control, which can ask before a call. Workspace chat, the Slack agent, and native-harness runs withhold these tools because they cannot ask. @@ -65,9 +65,11 @@ Replace these example names with the tool names your server exposes. } ``` +`delete` appears in both lists to show that the blocklist wins. The allowlist limits which tools can load. The blocklist and per-tool `enabled: false` exclude tools even if the allowlist includes them. A per-tool approval mode overrides the default. `auto` and `approve` both allow automatic calls. -Per-tool `deny` excludes a tool. `prompt` requires a Control approval card and withholds the tool on other web chat surfaces. +A server-level default of `prompt` makes every tool without a per-tool override Control-only. +Per-tool `deny` excludes a tool. `prompt` requires a Control approval card. Workspace chat, the Slack agent, and native-harness runs withhold these tools. ## Direction matters diff --git a/content/docs/web/guides/connection-scope-and-overrides.mdx b/content/docs/web/guides/connection-scope-and-overrides.mdx index 833f9a5..58a83f6 100644 --- a/content/docs/web/guides/connection-scope-and-overrides.mdx +++ b/content/docs/web/guides/connection-scope-and-overrides.mdx @@ -8,7 +8,7 @@ Connections in Mogplex are not just account-wide settings. This guide covers **Integrations**. The separate **MCP Servers** catalog applies across repos and does not use project exclusions. See [saved servers in web chat](/configure-and-extend/connections-and-mcp#use-a-saved-server-in-web-chat) for that catalog's permissions and availability. -They resolve at two levels: +Integrations resolve at two levels: - **Global** connections are available everywhere by default. - **Project** connections only exist for one repo. From db431483f75b0fb2802231f421d2bb75a9a0ee9c Mon Sep 17 00:00:00 2001 From: Charles Howard <96023061+charlesrhoward@users.noreply.github.com> Date: Tue, 22 Sep 2026 14:20:10 -0400 Subject: [PATCH 9/9] docs: align connections index and Integration scope --- content/docs/configure-and-extend/connections-and-mcp.mdx | 2 +- content/docs/configure-and-extend/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/configure-and-extend/connections-and-mcp.mdx b/content/docs/configure-and-extend/connections-and-mcp.mdx index 19d178b..4b4ef36 100644 --- a/content/docs/configure-and-extend/connections-and-mcp.mdx +++ b/content/docs/configure-and-extend/connections-and-mcp.mdx @@ -212,7 +212,7 @@ Choose **Run tools without asking** to switch back. ## Scope resolution -Connections can be global or project-scoped. +Integrations can be global or project-scoped. Saved MCP Servers apply across repos and do not use these scope settings. | Scope | Behavior | | --- | --- | diff --git a/content/docs/configure-and-extend/index.mdx b/content/docs/configure-and-extend/index.mdx index 88a39fd..ce46a4c 100644 --- a/content/docs/configure-and-extend/index.mdx +++ b/content/docs/configure-and-extend/index.mdx @@ -35,7 +35,7 @@ team, or local workflow needs.