Add the Gemini tab to the agent connector widget - #5799
Merged
Merged
Conversation
The gemini.svg mark and its README row were already committed, but the client entry was never added, so Gemini was the one mainstream assistant the widget did not offer. Gemini reaches a custom MCP server through Settings & help, Connected Apps, Add a custom app. FlowFuse supports Dynamic Client Registration, so no client ID or secret is needed. Google currently limits this to Gemini Spark on personal accounts in the US, which the step says, the same way the ChatGPT tab says developer mode needs a paid plan. One entry covers every surface that embeds the component: /ai, the changelog entry, the blog post and the third-party-agents docs page. Also points the logo README at AgentSetupTabs.vue. It still described src/ai.njk, which no longer exists on main.
4 tasks
✅ Deploy Preview for flowfuse-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
5 tasks
Merging main in puts Gemini in the wrong group. This branch was written when the local tab followed Claude directly, so inserting before local was right; main now has Claude Code and Codex in that gap, and the same insertion point lands Gemini after them: expert copilot chatgpt claude claude-code codex gemini local Gemini is a chat assistant, so it belongs beside Copilot, ChatGPT and Claude, not after the two coding agents. Anchored on the Claude entry instead of on local, which also stops this branch and the coding-agent branch inserting at the same point: expert copilot chatgpt claude gemini claude-code codex local Merges main in at the same time, so the PR is tested against what it will actually land on.
Contributor
Author
|
Updated for the current main. Merging this as it stood put Gemini in the wrong group. The branch was written when the Local tab followed Claude directly, so inserting before Local was correct then; main now has Claude Code and Codex in that gap, and the same insertion point landed Gemini after them:
Gemini is a chat assistant, so it is now anchored on the Claude entry:
Main is merged in, so this is tested against what it will actually land on. |
Contributor
Author
|
context" #5808 (comment) |
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
Adds the Gemini tab to the agent connector widget.
gemini.svgand its README row were already committed; the client entry was never added, so Gemini was the one mainstream assistant the widget did not offer.Gemini reaches a custom MCP server through Settings & help → Connected Apps → Add a custom app. FlowFuse supports Dynamic Client Registration, so no client ID or secret is needed. Google currently limits this to Gemini Spark on personal accounts in the US, which the step says, the same way the ChatGPT tab already says developer mode needs a paid plan.
One entry covers every surface that embeds
AgentSetupTabs:/ai, the changelog entry, the blog post, and the third-party-agents docs page.Also repoints the logo README at
AgentSetupTabs.vue; it still describedsrc/ai.njk, which no longer exists on main.The matching change for the in-platform modal is a separate PR on FlowFuse/flowfuse, which carries its own copy of this widget.
Related Issue(s)
https://github.com/FlowFuse/engineering/issues/272
Checklist