blog: connecting your own AI agent to FlowFuse - #5671
Open
dimitrieh wants to merge 15 commits into
Open
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
5 tasks
The post named ChatGPT and Claude but reached Gemini only as a CLI, and left local models out, so the approved-agent set did not match the page that leads this. It now covers the same set in the same order, with coding agents as the trailing clause, and links /ai for the per-agent path. Also missing against the page's governance section: the address itself, the requirement being MCP over HTTP, that RBAC still bounds the agent to what your own account reaches, and that actions land in the audit log marked via MCP. Adds that most agents ask before they act, and that the prompt is the agent's rather than ours. Agent, not assistant, in the policy paragraph.
dimitrieh
commented
Aug 26, 2026
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Co-authored-by: sumit shinde ( Roni ) <110285294+sumitshinde-84@users.noreply.github.com>
Contributor
Author
|
Thanks @sumitshinde-84 🙏 |
dimitrieh
commented
Aug 31, 2026
…t picker Replaces the Worked example section with the shared agent-setup-tabs component, so the blog, changelog and third-party-agents docs show the same three steps instead of a hand-copied Copilot Studio walkthrough that would drift. Trims the policy and granting sections, and folds the clipboard line into the opening paragraph.
dimitrieh
commented
Aug 31, 2026
Co-authored-by: Dimitrie Hoekstra <hi@dimitr.ie>
Without the closing ::, the MDC block ran to the end of the document and absorbed every section after it, so granting, canvas, IT and where-to-start stopped rendering as sections.
The batched review suggestion left the 'Configure your AI agent' step text without its closing quote, so the frontmatter stopped parsing. Four of the five howto step anchors pointed at headings that do not exist: how-the-connection-works and what-youre-granting never matched, and worked-example-connecting-microsoft-copilot referred to a section that is gone. They now point at real headings. The step url is rendered as canonical#url, so it can only be an on-page anchor, and the AI page is referenced from the step text instead.
5 tasks
Contributor
Author
|
The AI picker rendering oversized brand marks on this post (the ChatGPT square came out 780px) is fixed separately in #5714, since it is a change to the shared component styling rather than to this post.
|
| There is a workflow I keep hearing about, and nobody is proud of it. | ||
|
|
||
| An engineer has ChatGPT open in another tab. They describe the flow they want, get JSON back, copy it, paste it into the Node-RED editor, and fix whatever came back wrong. Next time, same thing. The AI is already doing the work, just not in an efficient way requiring you for part of it. | ||
|
|
Contributor
Author
There was a problem hiding this comment.
@sumitshinde-84 not sure what you mean here
Contributor
There was a problem hiding this comment.
I have added suggestion below
| There is a workflow I keep hearing about, and nobody is proud of it. | ||
|
|
||
| An engineer has ChatGPT open in another tab. They describe the flow they want, get JSON back, copy it, paste it into the Node-RED editor, and fix whatever came back wrong. Next time, same thing. The AI is already doing the work, just not in an efficient way requiring you for part of it. | ||
|
|
Contributor
There was a problem hiding this comment.
Suggested change
| <!--more--> |
sumitshinde-84
approved these changes
Aug 31, 2026
Contributor
|
@dimitrieh we need to update the date |
Contributor
Author
|
@sumitshinde-84 for now this was intended to first be iterated on in a doc. See https://flowfuse.slack.com/archives/C0B9KUA3YES/p1788173713599859 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A how-to blog post for the 3.0 third-party agent feature, sitting between the
/aipage and the documentation in depth.It leads with the policy angle rather than the capability, because that is the strongest part of the story: teams under approved-AI-only rules were prompting an external tool for flow JSON and hand-importing it, so the AI was already doing the work through the clipboard. Then the mechanism, a worked example in Copilot Studio, what you grant, and the conversation with IT.
Deliberately included, because leaving them out would make it marketing rather than a guide:
No
image:in the frontmatter yet, matching the handful of 2026 posts that also omit it, so the build is fine. An Art Request is still needed before this publishes.Related Issue(s)
FlowFuse/flowfuse#8192
#5612 (blog post deliverable, sub-issue of https://github.com/FlowFuse/engineering/issues/272)
Depends on
Links to
/docs/user/expert/third-party-agents/, which lands with FlowFuse/flowfuse#8241. A link check against that path fails until it merges. Pairs with #5670 for the/aipage and the changelog.Checklist