-
Notifications
You must be signed in to change notification settings - Fork 18
Changelog for FF Expert enhancements (all in one) #5279
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.
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
Open
Steve-Mcl
wants to merge
14
commits into
main
Choose a base branch
from
5277-changelog-for-expert-enhancements-all-in-one
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
85a12ef
changelog outline
Steve-Mcl b70fa5a
Additions for insights
Steve-Mcl f134899
add platform automations section to the expert enhacement changlog
cstns 0b39c35
docs(changelog): add plan mode, questions, and human-in-the-loop sect…
58e033b
Merge branch '5277-changelog-for-expert-enhancements-all-in-one' of g…
353015a
docs(changelog): add plan, questions, and approval card images
f9b1c76
docs(changelog): describe tool permissions settings for human in the …
d2c5837
docs(changelog): explain make permanent for per-chat permissions
01ddae4
Optimised images with calibre/image-actions
github-actions[bot] 35a8c04
Update messaging around insights and additional formatting.
Steve-Mcl 242f8e8
Merge branch 'main' into 5277-changelog-for-expert-enhancements-all-i…
Steve-Mcl 2e2f718
Spelling
Steve-Mcl 93de16d
apply suggestions: dedent headings, remove screenshots sub-heading
Steve-Mcl dee7986
Merge branch 'main' into 5277-changelog-for-expert-enhancements-all-i…
Steve-Mcl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,107 @@ | ||
| --- | ||
| title: FlowFuse Expert Enhancements | ||
| description: FlowFuse Expert now supports Insights on your devices, Platform automations, Plan Mode, Human in the Loop and more... | ||
| date: 2026-07-02 15:30:00 | ||
| authors: ["stephen-mclaughlin", "serban-costin", "andrea-palmieri"] | ||
| tags: | ||
| - changelog | ||
| issues: | ||
|
|
||
| --- | ||
|
|
||
| ## Insights | ||
|
|
||
| With the release of device-agent 4.0.0 and FlowFuse 2.32.0, FlowFuse Expert Insights Agent can now work with Remote Instances and Self Hosted Instances. | ||
|
|
||
| {% caution %} | ||
| **Important:** | ||
|
|
||
| In order to achieve Insights on Remote Instances and Self Hosted Instances, we had to modify how data is routed through the platform. Your old Hosted Instances on FlowFuse Cloud will require an update to the latest Launcher Version (2.23.0 or greater) to continue working. | ||
|
|
||
| {% endcaution %} | ||
|
|
||
| {data-zoomable} | ||
| *Resource from Hosted and Remote Instances can now be selected* | ||
|
|
||
| {data-zoomable} | ||
| *Insights querying a Remote Instance* | ||
|
|
||
| {data-zoomable} | ||
| *Insights in an action - querying a Remote Instance* | ||
|
|
||
|
|
||
| ## Platform Automations | ||
|
|
||
| The Expert can now take action on your FlowFuse platform directly. Instead of telling you which buttons to click, it can create instances, register devices, take snapshots, and manage applications on your behalf. You can ask the Expert to: | ||
|
|
||
| - Create hosted instances with the right type, stack, and template, optionally starting from a flow blueprint | ||
| - Register remote instances (devices) and assign them to applications | ||
| - Take and list snapshots of both hosted and remote instances | ||
| - Create applications, list what's running inside them, and check their audit logs | ||
| - Look up live status and logs for any hosted instance, or query a remote instance's state over MQTT | ||
|
|
||
| Behind the scenes, FlowFuse exposes over 30 automation tools covering instances, devices, applications, snapshots, teams, and configuration. When you ask the Expert to do something, it picks the right tools, calls them with your permissions, and reports back. | ||
|
|
||
|
|
||
| ## Support Agent | ||
|
|
||
| We have added three ways to stay in control of what the Expert does while it works alongside you in the editor. | ||
|
|
||
| ### Plan Mode | ||
|
|
||
| The Expert can now propose a plan before it changes anything, so you can review the approach before it touches your flows. | ||
|
|
||
| Turn on **Plan Mode** with the toggle in the chat composer. Instead of acting straight away, the Expert lays out what it intends to do as a plan you can read through. From there you can: | ||
|
|
||
| - **Approve**: the Expert proceeds with the plan. | ||
| - **Edit**: open the plan in the composer, adjust the wording yourself, and send it back. | ||
| - **Request changes**: describe what you would like to be different, and the Expert proposes an updated plan. | ||
| - **Reject**: discard the plan and start again. | ||
|
|
||
| This is ideal for larger or unfamiliar changes, where you want to agree on the approach before any work happens. | ||
|
|
||
| {data-zoomable} | ||
| *The Expert proposes a plan and waits for your approval before making any changes* | ||
|
|
||
| ### Clarifying Questions | ||
|
|
||
| The Expert now asks clarifying questions when a request could go more than one way, rather than guessing and building the wrong thing. | ||
|
|
||
| When it needs more detail, the Expert presents up to four questions in a single turn, each as a set of options you pick from, either single choice or multiple choice. You answer them all together, and it uses your answers to get the result right the first time. For example: | ||
|
|
||
| - Which flow should this run in? | ||
| - Should the incoming payload be stored, forwarded, or both? | ||
| - Which of these nodes should trigger the alert? | ||
|
|
||
| You can revisit and change your answers before continuing, and you decide the pace: use the follow-up questions setting in the composer menu to have the Expert ask everything **all at once** or **one at a time**. | ||
|
|
||
| {data-zoomable} | ||
| *The Expert asks clarifying questions and collects your answers before acting* | ||
|
|
||
| ### Human in the Loop | ||
|
|
||
| You are now in charge of exactly which actions the Expert is allowed to take on your flows, so no change happens that you did not permit. | ||
|
|
||
| When the Expert wants to run an action that needs your sign-off, it pauses and shows an approval card in the chat. The card names the action, whether it reads, writes, or deletes, and the exact details of what it will do, with four choices: | ||
|
|
||
| - **Allow** or **Deny**: approve or refuse this one action. | ||
| - **Always allow** or **Always deny**: apply your choice to every matching action. | ||
|
|
||
| The Expert waits for your decision however long you need, and you can cancel a pending action at any time with the stop button. | ||
|
|
||
| {data-zoomable} | ||
| *The Expert pauses and asks for approval before running an action that needs your sign-off* | ||
|
|
||
| An **Always allow** or **Always deny** you set from a card applies to the current chat only, and resets when you refresh or start over. If you want to keep it, click **Make permanent** to save that choice for future chats. | ||
|
|
||
| {data-zoomable} | ||
| *Make a per-chat permission permanent so it carries over to future chats* | ||
|
|
||
| You can also set your permissions ahead of time. Open **Tool permissions** in the Expert settings and choose a default for **Read**, **Write**, and **Delete** actions: **always allow**, **ask**, or **always deny**. Out of the box the Expert can read freely but asks before it writes or deletes anything. Flow building and platform actions each have their own defaults, and you can expand **Individual tools** to override the default for a specific action, which then stays put until you reset it. These settings are saved for you and persist across chats within the team you are working in; switching to another team starts from the defaults again. | ||
|
|
||
| {data-zoomable} | ||
| *Set default permissions per action type, and override individual tools where you need to* | ||
|
|
||
| --- | ||
|
|
||
| _All of these new features are available to FlowFuse Cloud users and Self-Hosted users from v2.32._ | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.