Skip to content

changelog: use the shared command block for the MCP address - #5682

Open
dimitrieh wants to merge 1 commit into
mainfrom
changelog/ff-command-nuxt
Open

changelog: use the shared command block for the MCP address#5682
dimitrieh wants to merge 1 commit into
mainfrom
changelog/ff-command-nuxt

Conversation

@dimitrieh

Copy link
Copy Markdown
Contributor

Description

Stacked on #5681. Base is that branch, not main.

The changelog entry gets the same copyable command block /ai shows, via the FfCommand component that PR introduces, instead of restating the MCP address as inline code. This is the thing that was not possible while /ai was 11ty and the changelog was Nuxt Content: two renderers, no shared component.

Also carries the changelog entry and feature-catalog entry from #5672, so this shows the merged result rather than a fragment.

Related Issue(s)

FlowFuse/flowfuse#8192

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

Stacked on the /ai Nuxt rebuild, which introduces FfCommand in
components/content/. The entry gets the same copyable block the page shows
rather than restating the address as inline code.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Base automatically changed from ai/nuxt-rebuild to main August 27, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant