Skip to content

changelog: use the shared agent picker instead of listing the agents #5700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dimitrieh merged 3 commits into from
Aug 28, 2026
Merged

changelog: use the shared agent picker instead of listing the agents #5700

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0362931
changelog: use the shared agent picker instead of listing the agents
dimitrieh Aug 27, 2026
b747230
Merge branch 'ai/agent-setup-tabs' into changelog/agent-setup-tabs
dimitrieh Aug 28, 2026
15fcbb9
Merge branch 'ai/agent-setup-tabs' into changelog/agent-setup-tabs
dimitrieh Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/changelog/2026/08/connect-your-own-ai-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/) or [Claude](https://claude.ai/). 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.

Expand Down