/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

google-gemini/gemini-cli

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-29T22:30:02.899Z

3mo ago

google-gemini/gemini-cli

Gemini CLI is a large, actively maintained open-source terminal AI agent for working with Gemini from the command line. It has high adoption, with 99,460 stars and 12,719 forks, and it is currently very active, with commits pushed on 2026-03-29. The repo is Apache 2.0 licensed and ships frequent preview, stable, and nightly releases.

Loading tags...

Stars99,460

Forks12,719

Default branchmain

Last pushed2026-03-29T22:17:11Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork if you want a customized Gemini CLI with extension and IDE-companion emphasis. Prefer upstream if you want the latest fixes, release cadence, and lower long-term maintenance risk.

Choose this fork if you want a substantially different, UI-driven Claude experience and are comfortable with losing upstream parity. Choose upstream Gemini CLI if you want the broader terminal-agent feature set, active maintenance, and lower integration risk.

Choose this fork if Chinese localization is the main requirement. Choose upstream if you want the newest Gemini CLI features, fixes, and release cadence.

Choose this fork if your main goal is running Gemini CLI inside Termux or on Android and you value environment-specific fixes over staying current with upstream. If you need the newest upstream features and release stream, upstream is the safer default.

Choose this fork if you want a more experimental, automation-oriented terminal agent and are comfortable with major upstream divergence. Avoid it if you need Gemini CLI’s upstream compatibility, predictable release behavior, or a conservative maintenance posture.

Prefer this fork only if you want its custom workflow tooling and are willing to maintain a highly divergent codebase. If you want current Gemini CLI features, bug fixes, and lower maintenance risk, upstream is the safer choice.

Fork comparison

gen-cli/gen-cli

38/100

stale

significant_divergence

Prefer this fork if you want a customized Gemini CLI with extension and IDE-companion emphasis. Prefer upstream if you want the latest fixes, release cadence, and lower long-term maintenance risk.

Likely purpose

A fork of Gemini CLI that appears to repurpose the project around custom agent workflows, extension support, and IDE-companion integration rather than tracking upstream closely.

Best for

Teams building a branded or productized CLI agent on top of Gemini CLI.; Users who want extension and IDE integration more than upstream feature parity.; Maintainers willing to own a heavily customized codebase.; Organizations that can absorb maintenance cost in exchange for tailored workflows.

Additional features

Extension-related workflows, including user extensions handling and workspace extension filtering.
IDE companion integration, including Firebase Studio-specific behavior.
CLI-side context filtering and port discovery logic.
Telemetry hardening with a rate limiter and high-water mark tracker.
More explicit logging around extension installation and shell output handling.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

It is about 200 commits behind upstream, so recent upstream CLI features and fixes are likely missing.
Upstream's newest Gemini 3-oriented UX changes and recent terminal interaction improvements are not reflected here.
Recent sandbox and Windows-specific fixes from upstream are likely absent.
Upstream's preview, stable, and nightly release cadence appears to be from a much newer line than this fork's snapshot.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Good fit for teams that want a more customized Gemini CLI foundation.
Appears oriented toward extension-driven and IDE-connected workflows.
Likely easier to adapt if you need telemetry or context-handling changes.
Large divergence means the fork can be optimized for its own product direction instead of upstream parity.

Risks

Very large divergence from upstream makes rebasing and future merges expensive.
The fork is stale relative to upstream, so security, sandbox, and UX fixes may lag.
Large deletions suggest some upstream behavior may have been removed or substantially rewritten.
Adopters should expect compatibility drift with upstream docs, releases, and extension assumptions.

google-gemini/gemini-cli · Discofork