Promote connecting AI clients (Claude, ChatGPT) in Rill Cloud chat#9661
Merged
Conversation
Surface prominent, branded entry points for connecting external AI clients (Claude, ChatGPT, Gemini) to a Rill project over MCP: - Empty-state hero card in every Cloud chat surface (global, dashboard, developer) - Restore the "Connect your own client" button in the project chat sidebar - Compact connect button in the dashboard/developer chat header - Brand the MCPConnectDialog for the chosen provider Wired via a shared connect-client Svelte context; only web-admin enables it, so Rill Developer and embedded dashboards render no CTA.
nishantmonu51
force-pushed
the
connect_to_claude
branch
from
July 7, 2026 19:09
b66eca7 to
e332783
Compare
AdityaHegde
requested changes
Jul 9, 2026
| Query your Rill metrics from your favorite AI client. | ||
| </div> | ||
| <div class="connect-hero-subtitle">Or directly ask questions in Rill.</div> | ||
| <ConnectClientButtons /> |
Collaborator
There was a problem hiding this comment.
The only other instance of this is test harness. Even those tests are not really testing anything singnificant. Lets move the markup here and remove those tests.
| const label = "Connect Claude, ChatGPT & more"; | ||
| </script> | ||
|
|
||
| <IconButton ariaLabel={label} bgGray onclick={() => connectClient.open()}> |
Collaborator
There was a problem hiding this comment.
Since there is no way to change the provider in MCPConnectDialog this button feels like a restricted action. How about adding some way to switch privoder in MCPConnectDialog?
Or conversely since there is no difference for providers, just label and icon how about just generalising messages in MCPConnectDialog?
| </div> | ||
| {#if connectClient.enabled} | ||
| <div class="collapsed-footer"> | ||
| <span title="Connect your own client"> |
Collaborator
There was a problem hiding this comment.
This is very similar to ConnectClientHeaderButton.svelte. How about adding variants to ConnectClientHeaderButton and using it?
| // Never surface connect CTAs inside an embedded dashboard, regardless of | ||
| // whether a shell wired the context. | ||
| if (EmbedStore.isEmbedded()) return DISABLED_CONTEXT; | ||
| if (!hasContext(CONNECT_CLIENT_CONTEXT_KEY)) return DISABLED_CONTEXT; |
Collaborator
There was a problem hiding this comment.
This should throw an error IMO. Not having CONNECT_CLIENT_CONTEXT_KEY means there was a dev error, if this silently hides then it might get missed.
| <div class="chatbot-header"> | ||
| <span class="chatbot-title">{currentConversationDto?.title || ""}</span> | ||
| <div class="chatbot-header-actions"> | ||
| {#if connectClient.enabled} |
Collaborator
There was a problem hiding this comment.
Maybe good to move this check inside ConnectClientHeaderButton?
- Inline the branded provider buttons into ConnectClientHero; remove the single-use ConnectClientButtons component and its tests. - Generalize MCPConnectDialog: drop the per-provider prop/branding. - Consolidate the connect buttons into one ConnectClientButton with full/square/icon variants that self-gates; use it in the sidebar and header. - getConnectClientContext() now throws when no provider ancestor is present; consumers gate on the adminServer flag, so Cloud dev errors are loud while Rill Developer and embedded dashboards (adminServer=false) never call it.
nishantmonu51
added
Type:Feature
# Conflicts: # web-admin/src/routes/[organization]/[project]/+layout.svelte # web-admin/src/routes/[organization]/[project]/-/ai/+layout.svelte
Keep the connect-your-AI-client popover in the full-page chat header only, wire its context from the AI page layout, and restore the previous connect-your-MCP sidebar footer button and project layout from main.
Re-add ConnectClientProvider as a self-contained wrapper that owns the MCPConnectDialog, wrap the explore and canvas chat mounts with it, and make the context lookup non-throwing so chat surfaces without a provider (embeds, edit mode, Rill Developer) simply render no connect CTA.
Collaborator
Author
|
@AdityaHegde : Review comments have been addressed on this one. Please check again. |
Collaborator
Author
|
@codex: review |
AdityaHegde
approved these changes
Jul 17, 2026
nishantmonu51
added a commit
that referenced
this pull request
Jul 17, 2026
…9661) * feat(chat): promote connecting AI clients in Rill Cloud chat Surface prominent, branded entry points for connecting external AI clients (Claude, ChatGPT, Gemini) to a Rill project over MCP: - Empty-state hero card in every Cloud chat surface (global, dashboard, developer) - Restore the "Connect your own client" button in the project chat sidebar - Compact connect button in the dashboard/developer chat header - Brand the MCPConnectDialog for the chosen provider Wired via a shared connect-client Svelte context; only web-admin enables it, so Rill Developer and embedded dashboards render no CTA. * Address review feedback - Inline the branded provider buttons into ConnectClientHero; remove the single-use ConnectClientButtons component and its tests. - Generalize MCPConnectDialog: drop the per-provider prop/branding. - Consolidate the connect buttons into one ConnectClientButton with full/square/icon variants that self-gates; use it in the sidebar and header. - getConnectClientContext() now throws when no provider ancestor is present; consumers gate on the adminServer flag, so Cloud dev errors are loud while Rill Developer and embedded dashboards (adminServer=false) never call it. * Replace obtrusive connect hero/button with a compact ConnectClientPopover * Fix stale `ProjectHeader.svelte` import path after merge from main * Reduce connect-client changes to minimal diff vs main Keep the connect-your-AI-client popover in the full-page chat header only, wire its context from the AI page layout, and restore the previous connect-your-MCP sidebar footer button and project layout from main. * Show connect-client popover in dashboard and canvas AI chat Re-add ConnectClientProvider as a self-contained wrapper that owns the MCPConnectDialog, wrap the explore and canvas chat mounts with it, and make the context lookup non-throwing so chat surfaces without a provider (embeds, edit mode, Rill Developer) simply render no connect CTA. (cherry picked from commit cbb72c0)
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
2 participants
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.
Surfaces prominent, branded entry points for connecting external AI clients to a Rill project over MCP, replacing the single generic button that was buried at the bottom of the chat sidebar.
MCPConnectDialogfor the chosen provider via an optionalproviderprop.connect-clientSvelte context. Onlyweb-adminenables it, so Rill Developer and embedded dashboards render no CTA (embed is also guarded explicitly viaEmbedStore.isEmbedded()).Checklist:
Developed in collaboration with Claude Code