From 03629311941722a579a2a172697211b8fabdff57 Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Thu, 27 Aug 2026 18:26:11 +0200 Subject: [PATCH] changelog: use the shared agent picker instead of listing the agents --- src/changelog/2026/08/connect-your-own-ai-agent.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/changelog/2026/08/connect-your-own-ai-agent.md b/src/changelog/2026/08/connect-your-own-ai-agent.md index cd6ba26ab8..40ca12308c 100644 --- a/src/changelog/2026/08/connect-your-own-ai-agent.md +++ b/src/changelog/2026/08/connect-your-own-ai-agent.md @@ -14,7 +14,12 @@ You can now connect your own AI agent to FlowFuse. Your company-approved AI can Add the FlowFuse address to connect, then decide which teams the agent reaches and whether it can make changes. -The address is `https://app.flowfuse.com/mcp`. [Pick your agent on the AI page](/ai/) for the exact steps in [Microsoft Copilot](https://copilotstudio.microsoft.com/), [ChatGPT](https://chatgpt.com/), [Claude](https://claude.ai/settings/connectors) or [Gemini](https://gemini.google.com/). Any MCP client that supports the HTTP transport works too, including command-line and editor agents and local models. Sign-in uses OAuth where the client supports it, with a token fallback where it does not. +Pick your agent, and follow the three steps: + +::agent-setup-tabs{:exclude-expert="true" surface="changelog"} +:: + +Any MCP client that supports the HTTP transport works, including command-line and editor agents and local models. Sign-in uses OAuth where the client supports it, with a token fallback where it does not. Your own agent gets the full, growing set of FlowFuse platform automation and flow-building tools to run. That matters most where company policy only permits an approved AI agent, so FlowFuse Expert wasn't an option.