Gemini CLI fix normalizes DEBUG environment variable truthiness
Eswar809 · ghdev · 2026-08-24
This PR fixes the interpretation of the DEBUG environment variable across sandbox utilities in google-gemini/gemini-cli.
Problem:
Previous logic relied on JavaScript string truthiness. Non-empty strings like "false" or "0" evaluated to true, causing unintended behaviors:
- Docker/Podman sandboxes unnecessarily published the debug port (9229).
- macOS Seatbelt sandboxes injected --inspect-brk, pausing CLI execution unexpectedly.
- Debug console patching and image-pull logging were enabled despite user intent.
Fix:
Introduced a centralized isDebugModeEnabled() helper that strictly checks for explicitly enabled values ("true", "1", or active CLI flags), aligning sandbox logic with existing entrypoint behaviors.
More from coding & agent
- Are the fastest GPU kernels now written by AI? Kernels are hyper-verifiable, argues one dev — fleetwood___ · 2026-10-16
- Anthropic lead engineer's 4-question prompt makes agents more ambitious, now a free skill — daniel_mac8 · 2026-10-16
- ChainForge dev shows 'feature map' for orchestrating subagents on large PRs — IanArawjo · 2026-10-16
- aiDotEngineer benchmarks agent orchestration pipelines, staging humans as Foreman and workers — vikvang1 · 2026-10-16
- Developer mass-produces 200 videos in hours using Claude Code + Hyperframes — mcraddock · 2026-10-16
- Penny University hosts software factory discussion; dev shares $40/mo vendor-agnostic AI stack — JnBrymn · 2026-10-16