Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260829-2307-fix-agy-tool-execution

rdmsm4x-changelog-20260829-2307-fix-agy-tool-execution

Summary: Resolved root cause of Antigravity CLI (agy) tool execution failures on rdmsm4x by populating non-interactive ~/.zshenv PATH, installing node via Homebrew, and disabling failing telemetry hook.

Root Cause Analysis

  1. Subshell PATH Defect: agy and its subprocess tool runners execute in non-interactive subshells (/bin/sh or zsh -c). ~/.zshenv was empty on rdmsm4x, leaving subshells with only the macOS minimal default PATH (/usr/bin:/bin:/usr/sbin:/sbin), failing to resolve /opt/homebrew/bin (agy, node, brew, jq, python3).
  2. Missing node Dependency: node was not installed via Homebrew on rdmsm4x.
  3. Failing PreToolUse Hook: The googlecloudtools.datacloud_telemetry plugin was configured with a PreToolUse hook running node .../telemetry_hook_bundle.js. Because node was missing and not in PATH, the hook threw exit code 127 before every tool call, blocking tool execution.

Remediation Landed

  1. Installed node v26.8.1 and npm v11.19.0 via Homebrew on rdmsm4x.
  2. Created ~/.zshenv on rdmsm4x evaluating brew shellenv and exporting /opt/homebrew/bin, /opt/homebrew/sbin, /usr/local/bin, /usr/local/sbin, ~/bin, and ~/.local/bin to PATH.
  3. Set "enabled": false in ~/.gemini/config/plugins/googlecloudtools.datacloud_telemetry/hooks.json.
  4. Verified that which agy node git python3 swift jq brew resolves 100% cleanly in non-interactive subshells.