Create Google Gemini cli extension by grahamplata · Pull Request #8177 · rilldata/rill

grahamplata · 2025-10-27T18:16:20Z

Create Google Gemini cli extension

Checklist:

Covered by tests
Ran it and it works as intended
Reviewed the diff before requesting a review
Checked for unhandled edge cases
Linked the issues it closes
Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
Intend to cherry-pick into the release branch
I'm proud of this work!

ericpgreen2

As mentioned in Slack, can you please remove all the Google integrations so we can first land the Rill-native functionality?

ericpgreen2 · 2025-11-05T14:25:45Z

Some of this language seems to be addressed to the end user (e.g. "By connecting to your Rill projects, the Gemini agent can..."), not the Gemini agent. I'd expect that the document would be exclusively addressed to the Gemini agent.

…kflow

begelundmuller · 2025-11-07T15:12:49Z

+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: '.nvmrc'
+
+      - name: Build Gemini Extension
+        if: env.PUBLISH_RELEASE == 'true'
+        run: |
+          cd integrations/gemini
+          npm ci
+          npm run build
+          npm run package
+        env:
+          HUSKY: 0


Can you pull the Gemini extension release into a separate workflow? So that issues with the Gemini extension can't hold up normal releases/patches

Fair enough, I am going to make it a manually triggered release

begelundmuller · 2025-11-07T15:16:55Z

+      - name: Add Gemini Extension to Release
+        if: env.PUBLISH_RELEASE == 'true'
+        uses: softprops/action-gh-release@v1
+        with:
+          files: integrations/gemini/release/**
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}


Does this create a release on Github? How will that look on the releases page? We don't want it to overshadow our normal Rill release

begelundmuller · 2025-11-07T15:17:31Z

+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: '.nvmrc'
+
+      - name: Install dependencies
+        run: cd integrations/gemini && npm ci
+        env:
+          HUSKY: 0
+
+      - name: Build extension
+        run: cd integrations/gemini && npm run build


The workflow is called Build and Release Rill Integrations, but looks like it just builds and exits?

begelundmuller · 2025-11-07T15:20:11Z

+# Rill Configuration
+RILL_ORG="demo"
+RILL_PROJECT="demo-project"
+RILL_ACCESS_TOKEN="rill_usr_1234567890abcdef"


Where precisely will users provide these values? I'm seeing placeholders both here and in integrations/gemini/gemini-extension.json. Ideally there's just one place, and ideally it's a single snippet they can copy/paste from their AI tab.

begelundmuller · 2025-11-07T15:20:45Z

+Update the extension with your Rill credentials by providing the following information when prompted:
+
+- `Organization`: Your Rill organization name
+- `Project`: Your Rill project name
+- `Access Token`: Your Rill access token


Where do they provide these values?

begelundmuller · 2025-11-07T15:22:00Z

+Install the extension via GitHub:
+
+```bash
+gemini extensions install https://github.com/rilldata/rill


Since we have a monorepo, how does Gemini know where in the repo to pick it up from? Does it need some additional hint?

The two supported options are that It needs to be at the root or referenced in the releases. This can also be lifted into its own repo.

begelundmuller · 2025-11-07T15:22:45Z

+This extension is distributed through [GitHub Releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases). This provides a faster and more reliable initial installation experience for users, as releases are shipped as single archives instead of requiring a git clone.
+
+Each release includes an archive file containing the full contents of the repository at the tagged commit. When checking for updates, Gemini CLI looks for the "latest" release on GitHub (you must mark it as such when creating the release), unless the user installed a specific release by passing `--ref=<some-release-tag>`.


Isn't the latest release occupied by our normal rill binary? I.e. not Gemini. Do we need a dedicated repo here?

initial setup

780c2ec

grahamplata force-pushed the gplata/gemini-extension branch from 21e3af9 to 780c2ec Compare October 27, 2025 18:18

grahamplata added 2 commits October 27, 2025 14:23

address prettier issues

79d0366

move docs

39ed6e2

grahamplata requested review from begelundmuller and ericpgreen2 October 27, 2025 18:28

ericpgreen2 suggested changes Oct 30, 2025

View reviewed changes

begelundmuller reviewed Oct 30, 2025

View reviewed changes

Comment thread extensions/gemini/commands/rill/analyze.toml Outdated

Comment thread extensions/gemini/src/tools/tools.ts Outdated

begelundmuller reviewed Oct 30, 2025

View reviewed changes

Comment thread package.json Outdated

Comment thread extensions/README.md Outdated

grahamplata force-pushed the gplata/gemini-extension branch from bd3c3a0 to 39ed6e2 Compare October 30, 2025 20:08

Merge branch 'main' into gplata/gemini-extension

9719397

grahamplata force-pushed the gplata/gemini-extension branch 2 times, most recently from 74b4731 to 62464b2 Compare November 4, 2025 14:30

initial review pass

be569bd

grahamplata force-pushed the gplata/gemini-extension branch from 62464b2 to be569bd Compare November 4, 2025 14:36

grahamplata added 2 commits November 4, 2025 10:04

allow rill-gemini-extension user agents

6bec3bc

update documentation for Analyst Agent features

0ee2ee1

grahamplata requested a review from ericpgreen2 November 4, 2025 15:41

ericpgreen2 requested a review from begelundmuller November 4, 2025 19:06

simplify persistent context and rely on agents

319985e

grahamplata force-pushed the gplata/gemini-extension branch from 2eec0b4 to 319985e Compare November 4, 2025 21:03

grahamplata added 3 commits November 4, 2025 16:04

Merge branch 'main' into gplata/gemini-extension

f77346c

go lint merge main

6a023c2

target cloud

9822704

ericpgreen2 suggested changes Nov 5, 2025

View reviewed changes

update release instructions in Gemini README

de2e5ef

grahamplata force-pushed the gplata/gemini-extension branch from 7abb8e2 to de2e5ef Compare November 5, 2025 22:06

grahamplata added 3 commits November 5, 2025 17:13

add line chart and context

4c4098a

move release

7f4a49f

add Node.js setup and build steps for Gemini Extension in release wor…

52a788d

…kflow

grahamplata requested a review from ericpgreen2 November 5, 2025 22:29

begelundmuller requested changes Nov 7, 2025

View reviewed changes

review

ca354fa

grahamplata force-pushed the gplata/gemini-extension branch from f7d0b13 to ca354fa Compare November 7, 2025 18:00

grahamplata closed this Nov 10, 2025

		This extension is distributed through [GitHub Releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases). This provides a faster and more reliable initial installation experience for users, as releases are shipped as single archives instead of requiring a git clone.

		Each release includes an archive file containing the full contents of the repository at the tagged commit. When checking for updates, Gemini CLI looks for the "latest" release on GitHub (you must mark it as such when creating the release), unless the user installed a specific release by passing `--ref=<some-release-tag>`.

Uh oh!

Conversation

grahamplata commented Oct 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ericpgreen2 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ericpgreen2 Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

grahamplata commented Oct 27, 2025 •

edited

Loading

ericpgreen2 Nov 5, 2025 •

edited

Loading