google-gemini/gemini-cli

Error updating google workspace extension

Open

#18884 opened on Feb 12, 2026

View on GitHub
 (6 comments) (0 reactions) (1 assignee)TypeScript (103,992 stars) (13,657 forks)batch import
area/extensionseffort/mediumhelp wantedkind/bugpriority/p1priority/p2status/bot-triagedtype/bug

Description

What happened?

Error while trying to update workspace extension

Image

What did you expect to happen?

Successful update

Client information

  • CLI Version: 0.28.2
  • Git Commit: da5e47ae3
  • Session ID: 7273c1cb-9ae1-429b-80d5-33e311d14b3d
  • Operating System: win32 v24.12.0
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 200.3 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here

Login information

No response

Anything else we need to know?

No response

Contributor guide

Tech stack
typescript
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue is a bug report about an error updating a Google workspace extension. The screenshot shows an error message but no reproduction steps. First, review the attached image to understand the error. Then, examine the extension update logic in the codebase, likely in the CLI's extension management module (e.g., src/extensions/). Check for any recent changes that might have broken the update flow. Look for network requests or state validation that could fail. The assignee may have insights; check comments for any additional context. Reproduce the update process locally to isolate the issue.