ShipStackLabShipStackLabStart a stack
TOOL / Coding agent

Gemini CLI

Gemini CLI is a terminal coding agent with account-specific access: consumer sign-in has transitioned to Antigravity, while Code Assist Standard/Enterprise and API key paths are distinct. This sourced profile is not a hands-on recommendation.

PROFILE PARTIALNOT YET TESTEDChecked 2026-10-07
Official website Add to stack

What Gemini CLI does

Gemini CLI is an open-source terminal coding agent with repository file operations, shell commands, web tools, and MCP integrations. It can support scoped implementation work, but its account access must be checked before adopting a workflow.

Stable Gemini CLI v0.63.0, reviewed October 7, documents bounded tool output in long-running loops, separate handling for absent versus malformed MCP enablement configuration, and fixes for headless authentication loops. Its linked policy change aligns redirection checks and converts non-interactive ASK_USER decisions to DENY across safety evaluation paths; MCP resource and web-search results are wrapped as untrusted context.

Its non-interactive plan workflow no longer waits for conversational agreement before drafting and starting execution; interactive sessions retain that consultation. This prompt behavior is separate from tool authorization: not waiting for a user conversation does not turn an ASK_USER permission into an allow decision. The stable release does not reverse the consumer-account transition below.

Stable Gemini CLI v0.61.0, reviewed September 28, documents fixes for indirect prompt injection through build-file changes and untrusted flags, plus stronger filesystem boundaries and runtime-state isolation in the sandbox. This is a stable-release claim, not evidence that arbitrary repository instructions or build commands are safe.

Stable Gemini CLI v0.59.0 includes fixes for server-side request forgery (SSRF) in MCP OAuth metadata discovery and authentication. It also enforces fail-closed workspace trust and filters mcpServers in restricted mode. These are the stable release's documented fixes, not a claim that every MCP server or workflow is safe.

Stable Gemini CLI v0.60.0 adds RFC 9207 issuer checks to MCP OAuth and hardens web-fetch destinations, extension loading, workspace paths, and system-configuration ownership checks. It also isolates macOS sandbox temporary storage and container settings, and adds consent for extension environment changes. These release-scoped changes do not alter the consumer-account transition described below.

Account change effective June 18, 2026: Google's dated deprecation notice says Gemini CLI stopped serving the individual free, Google AI Pro, and Google AI Ultra tiers through consumer Google sign-in. Gemini Code Assist Standard and Enterprise subscriptions are not affected by this change.

The official maintainer announcement separately states that API key authentication is unaffected. That does not establish a free allowance or entitlement for a specific key, model, or project; verify its current access and billing separately.

Google directs affected consumer users to Antigravity CLI. The repository README still describes older personal-account free access; this profile follows the dated deprecation notice for that access decision, not those older onboarding claims.

Workflow role

  • build

Inputs and outputs

Inputs

  • Local repository and coding brief
  • Approved file, shell, and MCP context

Outputs

  • Reviewable file edits
  • Command output and task results

Compatible tools

UNKNOWN

Ownership and deployment

Code ownershipUNKNOWNUNKNOWN · Official code-ownership evidence has not been recorded. · Checked 2026-08-19
Data ownershipUNKNOWNUNKNOWN · Official data-ownership evidence has not been recorded. · Checked 2026-08-19
Deployment modelA terminal agent for repository work, not managed hosting for the resulting applicationVERIFIED · Official source evidence recorded · Checked 2026-09-06
Pricing statusUNKNOWNUNKNOWN · Current model/key/project prices and allowances have not been verified; do not reuse the README's older consumer free-tier claims. · Checked 2026-09-06

Suitable and unsuitable tasks

Suitable

  • Scoped terminal-based repository work after confirming the actual account and authentication path

Not established

  • Assuming an individual free, Google AI Pro, or Google AI Ultra subscription still grants Gemini CLI consumer sign-in access

Known limitations and unknowns

  • Consumer free, Google AI Pro, and Google AI Ultra sign-in access stopped on June 18, 2026; Code Assist Standard/Enterprise subscriptions are unaffected by that deprecation.VERIFIED · Checked 2026-09-06
  • ShipStackLab has not tested authentication, migration, or task outcomes on these account paths.UNKNOWN · Checked 2026-09-06

Adoption checks

  • Identify whether the intended run uses an affected consumer subscription, a Code Assist Standard/Enterprise license, or an API key. Do not treat the consumer transition as a shutdown of every Gemini CLI authentication path.
  • For v0.63.0 unattended runs, record the version/channel, interactive setting, permission mode, command arguments, sandbox and authentication/billing route. Establish explicit scope and external-write authorization before scheduling; do not bypass a DENY to finish the run. Any behavioral evaluation requires a separately authorized disposable repository. ShipStackLab has not independently tested this release's policy, authentication or headless execution behavior.
  • For v0.61.0, record the installed version and channel; review build-file changes and command flags before execution. Keep untrusted repositories and runtime state separate from production credentials. Any authorized evaluation should use disposable data and verify denied paths remain unchanged, without disabling sandbox controls. ShipStackLab has not reproduced the issues or independently tested these fixes; earlier exposure remains UNKNOWN.
  • MCP security check: record the installed version and release channel, and verify that the stable v0.59.0 fixes are included before relying on these protections. Review workspace trust and configured MCP servers; do not bypass restricted mode just to make a server run. Preview and nightly changes are not evidence for this stable version. ShipStackLab has not reproduced the security issues or independently audited these fixes.
  • For v0.60.0, review extension environment changes before consenting, and keep workspace, symlink, sandbox, and configuration boundaries in the test record. Do not bypass a rejected OAuth or path check to restore functionality. The stable release is distinct from preview/nightly builds; ShipStackLab has not independently tested its security fixes.
  • Before migration, back up configuration and review the official migration guide. First-launch onboarding offers an interactive selection of assets to import; custom themes and experimental overlays may not have feature parity.
  • Check project skills and MCP configuration after migration: the guide moves workspace skills from .gemini/skills/ to .agents/skills/ and puts MCP servers in separate mcp_config.json profiles. Manual remote-server migrations require the documented serverUrl schema key. Review imported servers, credentials, and permissions before running them.
  • Record the CLI version, model, authentication method, project, and permission settings for a repeatable test. Verify the resulting diff and checks in an isolated repository; an installed client or successful import is not proof that account access, billing, or the workflow works.

Source register