docs: use the shared agent picker on the third-party agents page - #8313
Merged
Conversation
andypalmi
approved these changes
Aug 28, 2026
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
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
Outcome: the setup steps become something the reader uses, not just reads.
Pick your agent, copy the address, follow three steps. The same picker
/aiand the changelog entry use, so all three stay in step with each other.The FlowFuse Expert tab is hidden, since this page is about connecting your own agent. The sign-up button in step 03 is off, since the reader already has an account.
The component lives in the website repo and is added by FlowFuse/website#5699. That has to be deployed first. Until then this block shows as plain text, including in GitHub's own markdown view.
One thing worth deciding. The picker sits above the per-agent sections, which cover the same four agents again. Those sections hold detail the tabs do not: the Copilot tenant administrator path, the ChatGPT developer mode gate, the Claude Code command, the Ollama note. Happy to fold that detail into the picker and drop the sections, which would leave one description per agent instead of two.
Related Issue(s)
#8192