koopa-env

Why a tool resolves inside the koopa prefix instead of Homebrew or the system, how to check that, and how koopa activation behaves in non-interactive and agentic sessions. Use when a command resolves to an unexpected binary, when PATH order looks wrong, or when working inside an SSH/CI/agent harness session that needs koopa's tools on PATH, when asking which shell an agent runs, or what KOOPA_BUCKET is.