changelog: connect your own AI agent (3.0) - #5672
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Per review, the entry ended on a docs link, which is not a call to action. It now carries the one-click routes that exist: the VS Code redirect and the Cursor deeplink, both verified (the VS Code one 302s to vscode:mcp/install with the right payload), the claude mcp add command, and the paste-the-address route for Claude, ChatGPT and Copilot Studio, which have no deeplink. Also: agent rather than assistant, matching the docs, and a line on the audit log now that third-party calls are attributed via MCP.
…tooling The previous commit put editor and command-line deeplinks at the top, which inverts the story. The audience is the agent a company has already approved, and /ai leads on the enterprise assistants and local models with coding agents as a trailing note. The CTA now matches that order and hands off to /ai, which already carries the copyable address and the three steps per agent.
Text only. The schematic stays on /ai, where it sits alongside the picker it explains.
|
|
||
| Flow building happens on the canvas in front of you. Open the instance, turn on the MCP toggle in the page header, and you watch the agent work. | ||
|
|
||
| This is available to all FlowFuse Cloud users and to Enterprise self-hosted installations from v3.0, across FlowFuse Hub, Edge and Fleet. See [connecting your own agent](/docs/user/expert/third-party-agents/) for setup, including what to check on an instance before asking for a flow. |
There was a problem hiding this comment.
Flagging this link: what ships first is not settled yet, and gets decided later today.
/ai and the docs page are landing on different tracks. /ai is #5670 (11ty) or #5681 (Nuxt), still an open renderer question, and we aligned in the Slack thread that it may land the week after release. The docs page is FlowFuse/flowfuse#8241, which is green.
Default for now: point at /ai. It carries the address to copy and the three steps per agent, which is what a reader at this point actually needs. The docs link stays for the detail.
If /ai slips past release day, this line needs the order flipped, so leave the thread open until that call is made.
There was a problem hiding this comment.
I'll leave this up to you and marketing then, correct?
There was a problem hiding this comment.
docs is fine for changelog entries. we can mention the ai page additionally
There was a problem hiding this comment.
Correct, ours to call. Keeping the order as it stands: /ai first for the per-agent steps, the docs page after it for the detail. Both links are in.
If /ai slips past release day I will flip them before this merges, so leaving this thread open until that lands.
Co-authored-by: Andrea Palmieri <76187074+andypalmi@users.noreply.github.com>
a0cd2c5 to
f826c4f
Compare
5 participants
Description
Changelog entry for the 3.0 third-party agent feature, plus the feature-catalog entry that carries its plan badges.
The entry now ends on one-click install links for VS Code, Cursor and Claude Code rather than a docs link, per review.
Split out of #5670 so the changelog reviews on its own. The diagram is duplicated into the changelog's own
images/directory, so neither PR depends on the other.If /ai moves to Nuxt
#5682 is this entry with the shared
FfCommandblock instead of the address as inline code. It is stacked on #5681, so it only applies if that lands.Related Issue(s)
FlowFuse/flowfuse#8192
#5611
Depends on
/docs/user/expert/third-party-agents/lands with FlowFuse/flowfuse#8241. The link check fails until that merges; Netlify's build does not run it, so the preview builds.Checklist