Skip to content

Add the Gemini tab to the agent connector widget - #5799

Merged
ZJvandeWeg merged 3 commits into
mainfrom
ai/gemini-connector-tab
Sep 15, 2026
Merged

ZJvandeWeg merged 3 commits into
mainfrom
ai/gemini-connector-tab

Conversation

@dimitrieh

Copy link
Copy Markdown
Contributor

Description

Adds the Gemini tab to the agent connector widget. gemini.svg and 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 described src/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

  • 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)

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.
@netlify

netlify Bot commented Sep 14, 2026

Copy link
Copy Markdown

Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit fc056cd
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6aa918d33fc1e80008041f3a
😎 Deploy Preview https://deploy-preview-5799--flowfuse-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 43 (🟢 up 12 from production)
Accessibility: 95 (no change from production)
Best Practices: 92 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

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.
@dimitrieh

Copy link
Copy Markdown
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:

expert copilot chatgpt claude claude-code codex gemini local

Gemini is a chat assistant, so it is now anchored on the Claude entry:

expert copilot chatgpt claude gemini claude-code codex local

Main is merged in, so this is tested against what it will actually land on.

@ZJvandeWeg
ZJvandeWeg merged commit fcd35b8 into main Sep 15, 2026
7 checks passed
@ZJvandeWeg
ZJvandeWeg deleted the ai/gemini-connector-tab branch September 15, 2026 13:18
@dimitrieh

Copy link
Copy Markdown
Contributor Author

context" #5808 (comment)

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.

2 participants