RCA-2026-04-03-001: Fix Applied

Resolution

Immediate Action (Workaround)

Used absolute path to invoke the binary:

/usr/bin/bluetoothctl devices
/usr/bin/bluetoothctl connect 24:24:B7:B5:1C:CC

Verification

# Confirmed connection
/usr/bin/bluetoothctl info 24:24:B7:B5:1C:CC | awk '/Name|Connected/'

The Fix Pattern

When constructing PATH in shell init files, ensure system paths are always present:

# DEFENSIVE: Always include system paths explicitly
export PATH="$HOME/.local/bin:$HOME/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# OR: Only prepend if PATH already has content
if [[ -n "$PATH" ]]; then
    export PATH="$HOME/.local/bin:$PATH"
else
    export PATH="$HOME/.local/bin:/usr/local/bin:/usr/bin:/bin"
fi

Defensive Patterns for Claude Code

When Bash Tool Fails with Exit 127

# 1. Check if binary exists
ls /usr/bin/<command> /usr/local/bin/<command> 2>/dev/null

# 2. Use absolute path
/usr/bin/<command> <args>

# 3. Or fix PATH inline
PATH="/usr/bin:/usr/sbin:$PATH" <command> <args>

Common Absolute Paths (Arch Linux)

Command Path

bluetoothctl

/usr/bin/bluetoothctl

systemctl

/usr/bin/systemctl

pacman

/usr/bin/pacman

ip

/usr/bin/ip

ss

/usr/bin/ss

docker

/usr/bin/docker

journalctl

/usr/bin/journalctl