Skip to content
DevAgentRadarDevAgentRadar
Sign in
Proposals/Upgrade Gemini CLI nightly for macOS Seatbelt Do
proposalteamP3Worth a lookGCGemini CLI

Upgrade Gemini CLI nightly for macOS Seatbelt Docker socket isolation

Adopt Gemini CLI v0.56.0-nightly.20260822.g5411f113c so macOS Seatbelt sandboxing isolates Docker and container runtime sockets and binaries, tightening CLI sandbox boundaries when containers are present.

Why this loop

This prerelease ships a targeted sandbox fix: Docker and container runtime sockets and binaries are isolated under macOS Seatbelt. Teams running Gemini CLI on macOS alongside Docker or other container runtimes should move to this build so the sandbox no longer leaves those sockets/binaries exposed to the agent process. The change is security-surface only (surface:sandbox); workflow impact is upgrade-and-verify, not new product features.

Proposed actions

  1. Update Gemini CLI to the exact prerelease tag v0.56.0-nightly.20260822.g5411f113c (from https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260822.g5411f113c) on every macOS machine that runs the CLI with Docker or another container runtime installed.
  2. After install, run `gemini --version` (or your usual binary name) and confirm the reported version string matches v0.56.0-nightly.20260822.g5411f113c before continuing sandbox-enabled sessions.
  3. On macOS hosts that use the CLI sandbox with Docker present, restart any long-lived Gemini CLI sessions so they load the Seatbelt profile that isolates Docker and container runtime sockets and binaries.
  4. In your team runbook, note that macOS Seatbelt sandbox isolation of Docker/container runtime sockets and binaries landed in PR https://github.com/google-gemini/gemini-cli/pull/28935 and require this nightly (or newer) for container-adjacent Gemini CLI work.
  5. If you pin Gemini CLI in CI or devcontainer images on macOS runners, bump the pin to v0.56.0-nightly.20260822.g5411f113c and rebuild so sandbox policy matches local developer machines.

Agent prompt

Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI cost

Google Antigravity / agent task

# DevAgentRadar → Google Antigravity

Goal: turn this release signal into a safe pilot plan for my stack.

## Context
Assistant: Gemini CLI
Proposal: Upgrade Gemini CLI nightly for macOS Seatbelt Docker socket isolation
Summary: Adopt Gemini CLI v0.56.0-nightly.20260822.g5411f113c so macOS Seatbelt sandboxing isolates Docker and container runtime sockets and binaries, tightening CLI sandbox boundaries when containers are present.
Primary source: https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260822.g5411f113c

## Why it matters
This prerelease ships a targeted sandbox fix: Docker and container runtime sockets and binaries are isolated under macOS Seatbelt. Teams running Gemini CLI on macOS alongside Docker or other container runtimes should move to this build so the sandbox no longer leaves those sockets/binaries exposed to the agent process. The change is security-surface only (surface:sandbox); workflow impact is upgrade-and-verify, not new product features.

## Suggested actions
1. Update Gemini CLI to the exact prerelease tag v0.56.0-nightly.20260822.g5411f113c (from https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260822.g5411f113c) on every macOS machine that runs the CLI with Docker or another container runtime installed.
2. After install, run `gemini --version` (or your usual binary name) and confirm the reported version string matches v0.56.0-nightly.20260822.g5411f113c before continuing sandbox-enabled sessions.
3. On macOS hosts that use the CLI sandbox with Docker present, restart any long-lived Gemini CLI sessions so they load the Seatbelt profile that isolates Docker and container runtime sockets and binaries.
4. In your team runbook, note that macOS Seatbelt sandbox isolation of Docker/container runtime sockets and binaries landed in PR https://github.com/google-gemini/gemini-cli/pull/28935 and require this nightly (or newer) for container-adjacent Gemini CLI work.
5. If you pin Gemini CLI in CI or devcontainer images on macOS runners, bump the pin to v0.56.0-nightly.20260822.g5411f113c and rebuild so sandbox policy matches local developer machines.

## Config surfaces this release may change
- sandbox settings — check your repo before applying


Please:
1. Map the change to concrete pilot steps
2. Flag security / permission implications
3. Keep the pilot reversible
modelsecuritycliprereleaseRelease source ↗

Your loop

This browser · no sign-in · not shared as “you”

Your decision stays on this device. A public tally appears after a few votes.

Originating release signal

GCGemini CLIv0.56.0-nightly.20260822.g5411f113cAug 22, 2026

v0.56.0-nightly.20260822.g5411f113c Release v0.56.0-nightly.20260822.g5411f113c

fix(sandbox): isolate Docker and container runtime sockets and binaries in macOS Seatbelt

Verified excerpt — the source's own words
## What's Changed
* fix(sandbox): isolate Docker and container runtime sockets and binaries in macOS Seatbelt by @josebalius in https://github.com/google-gemini/gemini-cli/pull/28935

## New Contributors
* @josebalius made their first contribution in https://github.com/google-gemini/gemini-cli/pull/28935

**Full Changelog**: https://github.com/google-gemini/gemini-cli/compare/v0.56.0-nightly.20260821.g30573d2e4...v0.56.0-nightly.20260822.g5411f113c
Primary source ↗