[{"data":1,"prerenderedAt":298},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F04\u002Fflowfuse-release-2-29":3},{"id":4,"title":5,"body":6,"description":12,"extension":287,"meta":288,"navigation":293,"path":294,"seo":295,"stem":296,"__hash__":297},"blog\u002Fblog\u002F2026\u002F04\u002Fflowfuse-release-2-29.md","FlowFuse 2.29: FlowFuse Expert Comes to Self-Hosted Enterprise",{"type":7,"value":8,"toc":268},"minimark",[9,13,18,24,29,32,35,43,47,50,53,62,66,73,83,87,97,101,104,108,111,114,117,128,132,135,141,144,147,150,161,165,196,200,220,224,233,242,246,260],[10,11,12],"p",{},"FlowFuse 2.29 gives teams more control over how flows move through their stack, makes it easier to understand what changed between versions, and brings FlowFuse Expert to self-hosted enterprise customers.",[14,15,17],"h2",{"id":16},"flowfuse-expert-available-to-more-teams-and-more-capable-expert","FlowFuse Expert, Available to More Teams and More Capable {#expert}",[10,19,20],{},[21,22,23],"em",{},"FlowFuse Expert is our integrated AI assistant — one consistent surface across the FlowFuse website, platform, and immersive Node-RED editor for troubleshooting, building, and getting targeted help.",[25,26,28],"h3",{"id":27},"self-hosted-enterprise-expert-self-hosted","Self-Hosted Enterprise {#expert-self-hosted}",[10,30,31],{},"FlowFuse Expert was previously only available to cloud customers. Self-hosted enterprise teams had no equivalent surface for in-context troubleshooting and guidance.",[10,33,34],{},"Expert is now available for self-hosted enterprise FlowFuse instances. Your team gets the same contextual guidance and targeted help as cloud customers, with your operational data staying on your own infrastructure.",[10,36,37,42],{},[38,39,41],"a",{"href":40},"\u002Fcontact-us\u002F?subject=FlowFuse%20Expert%20for%20Self-Hosted","Contact us"," to enable Expert on your self-hosted environment.",[25,44,46],{"id":45},"take-action-directly-from-expert-responses-expert-actions","Take Action Directly from Expert Responses {#expert-actions}",[10,48,49],{},"Expert responses previously surfaced information and suggestions. Acting on them — importing a flow, selecting relevant nodes, opening a new tab — required switching out of the conversation and doing it manually.",[10,51,52],{},"Expert responses can now include clickable action links. Click one and Expert performs the action directly in your editor: opening a new flow tab, selecting the nodes it just mentioned, or importing a flow from the conversation.",[10,54,55],{},[56,57],"img",{"alt":58,"dataZoomable":59,"src":60,"style":61},"Expert action links demo","","\u002Fblog\u002F2026\u002F04\u002Fimages\u002Fexpert-action-links.gif","border: 2px solid #E5E7EB;",[63,64,65],"figcaption",{},"Expert responses can now act on your behalf — click a link and Expert opens a tab, selects nodes, or imports a flow directly in your editor.",[10,67,68,72],{},[69,70,71],"strong",{},"Coming next:"," spinning up Node-RED instances directly from Expert, letting you go from idea to running flow without leaving the chat.",[74,75,78,79],"div",{"className":76},[77],"ff-related-changelogs","Changelog: ",[38,80,82],{"href":81},"https:\u002F\u002Fflowfuse.com\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links\u002F","FlowFuse expert action links",[25,84,86],{"id":85},"in-practice","In practice",[88,89,90,94],"ul",{},[91,92,93],"li",{},"You act on Expert suggestions in one click instead of manually applying them",[91,95,96],{},"You stay in the conversation while Expert works in your editor",[14,98,100],{"id":99},"more-visibility-and-control-across-your-deployment-workflow-deployment-workflow","More Visibility and Control Across Your Deployment Workflow {#deployment-workflow}",[10,102,103],{},"Managing flows across environments means tracking what changed, when, and by whom. When tooling gaps introduce friction here — or leave your version control workflow fragmented — they slow teams down at exactly the wrong moment.",[25,105,107],{"id":106},"azure-devops-git-integration-azure-devops","Azure DevOps Git Integration {#azure-devops}",[10,109,110],{},"FlowFuse's GitOps support previously required GitHub. Teams standardised on Azure DevOps had no native way to include Node-RED flows in their existing version control workflow.",[10,112,113],{},"FlowFuse 2.29 adds Azure DevOps as a supported Git provider. You can now push and pull snapshots directly from Azure DevOps repositories using Personal Access Tokens, configured under Team Settings → Integrations.",[25,115,86],{"id":116},"in-practice-1",[88,118,119,122,125],{},[91,120,121],{},"You connect Azure DevOps repos alongside or instead of GitHub",[91,123,124],{},"Your Node-RED flows participate in the same version control workflow as the rest of your stack",[91,126,127],{},"You authenticate with Azure Personal Access Tokens, with no secondary tooling required",[25,129,131],{"id":130},"see-exactly-what-changed-in-a-snapshot-snapshot-diff","See Exactly What Changed in a Snapshot {#snapshot-diff}",[10,133,134],{},"FlowFuse's snapshot comparison view showed flows side by side, but the visual alone doesn't always tell the whole story. You could see that a node was different, but not which specific property changed. When a function node's code changed, you couldn't identify which lines were different without manually diffing two code blocks outside of FlowFuse.",[10,136,137],{},[56,138],{"alt":139,"dataZoomable":59,"src":140,"style":61},"Snapshot diff demo","\u002Fblog\u002F2026\u002F04\u002Fimages\u002Fsnapshot-comparision-view-2.29.png",[63,142,143],{},"The compare dialog now shows exactly which properties changed and highlights line-level differences in function code, templates, and JSON — no manual diffing required.",[10,145,146],{},"The compare dialog now includes a property-level diff sidebar: structural property changes old to new at a glance, and git-style line diffs for function code, template HTML, and JSON. A navigation bar steps through every changed, added, or deleted node with arrow key shortcuts. The canvas highlights and scrolls to the current node as you navigate.",[25,148,86],{"id":149},"in-practice-2",[88,151,152,155,158],{},[91,153,154],{},"You review what changed between dev and production without leaving FlowFuse",[91,156,157],{},"You validate a teammate's update at the property level, not just the node level",[91,159,160],{},"You debug why a flow changed after a deploy with the same tooling you use to promote it",[14,162,164],{"id":163},"what-else-is-new","What else is new?",[88,166,167,173,179,190],{},[91,168,169,172],{},[69,170,171],{},"Expert opens by default",": FlowFuse Expert now opens automatically when you visit the editor for the first time. If you close it, that preference is remembered across browser sessions.",[91,174,175,178],{},[69,176,177],{},"Embedded editor tab titles",": Hosted and Remote Instance editor tabs now show the actual Node-RED flow name rather than a generic title.",[91,180,181,184,185,189],{},[69,182,183],{},"Instance URL env var",": Hosted Node-RED instances now expose an ",[186,187,188],"code",{},"FF_INSTANCE_URL"," environment variable containing the instance's URL (default or custom hostname). Useful for flows that need to know their own address, like webhook callbacks or OAuth redirects.",[91,191,192,195],{},[69,193,194],{},"Blueprint markdown rendering",": Blueprint descriptions now support markdown rendering, so formatting like headers and lists display as intended.",[25,197,199],{"id":198},"fixes","Fixes",[88,201,202,208,214],{},[91,203,204,207],{},[69,205,206],{},"MCP server discoverability",": Older MCP servers that were registered on your instances were not showing up in Expert Insights mode. All registered MCP servers are now discoverable again.",[91,209,210,213],{},[69,211,212],{},"Snapshot detail in the immersive editor",": Reviewing a snapshot from inside the immersive editor now opens it in a modal, so you can inspect snapshots without leaving the editor.",[91,215,216,219],{},[69,217,218],{},"Developer Mode tab restored in the immersive editor",": The Developer Mode tab is back in the immersive editor drawer, letting you toggle Auto Snapshots and create snapshots without opening a second window.",[25,221,223],{"id":222},"node-red","Node-RED",[10,225,226,232],{},[38,227,231],{"href":228,"rel":229},"https:\u002F\u002Fgithub.com\u002Fnode-red\u002Fnode-red\u002Freleases\u002Ftag\u002F4.1.8",[230],"nofollow","Node-RED 4.1.8"," is now available as a stack option in FlowFuse. Highlights include function node tab badges (see at a glance which tabs contain code), theme plugin overrides for settings and menu options, configurable palette categories via theme plugins, and show-first\u002Flast-tab keyboard actions.",[10,234,235,236,241],{},"Looking ahead, ",[38,237,240],{"href":238,"rel":239},"https:\u002F\u002Fnodered.org\u002Fblog\u002F2025\u002F12\u002F03\u002Fnode-red-roadmap-to-5",[230],"Node-RED 5.0"," is in beta. It's a modernization and UI re-architecture that readies Node-RED for better AI-guided development and brings more clarity to manual editing. FlowFuse will ship 5.0 once it reaches stable release.",[243,244],"hr",{"style":245},"margin: 3rem 0; border: 0; border-top: 1px solid #D1D5DB;",[10,247,248,249,253,254,259],{},"For detailed breakdowns of each feature with additional visuals, visit our ",[38,250,252],{"href":251},"\u002Fchangelog\u002F","changelog",". For the complete list of everything included in FlowFuse 2.29, check out the ",[38,255,258],{"href":256,"rel":257},"https:\u002F\u002Fgithub.com\u002FFlowFuse\u002Fflowfuse\u002Freleases",[230],"release notes",".",[10,261,262,263,267],{},"If something in this release improves your workflow, or if there is still friction we can remove, please ",[38,264,266],{"href":265},"mailto:contact@flowfuse.com?subject=Feedback%20on%202.29","share feedback or report issues regarding this release"," to us.",{"title":59,"searchDepth":269,"depth":269,"links":270},2,[271,277,283],{"id":16,"depth":269,"text":17,"children":272},[273,275,276],{"id":27,"depth":274,"text":28},3,{"id":45,"depth":274,"text":46},{"id":85,"depth":274,"text":86},{"id":99,"depth":269,"text":100,"children":278},[279,280,281,282],{"id":106,"depth":274,"text":107},{"id":116,"depth":274,"text":86},{"id":130,"depth":274,"text":131},{"id":149,"depth":274,"text":86},{"id":163,"depth":269,"text":164,"children":284},[285,286],{"id":198,"depth":274,"text":199},{"id":222,"depth":274,"text":223},"md",{"navTitle":5,"excerpt":289},{"type":7,"value":290},[291],[10,292,12],{},true,"\u002Fblog\u002F2026\u002F04\u002Fflowfuse-release-2-29",{"title":5,"description":12},"blog\u002F2026\u002F04\u002Fflowfuse-release-2-29","iNVADONAICG6FfHPKoMkJ15uf9nmX57c-NkSYVq8RHk",1780070554581]