Bash tool returns no output on macOS

[Alvis1337]

Shell commands (even simple 'echo') return no output and sessions expire before output can be read. macOS terminal. Copilot CLI v1.0.22, Claude Opus 4.6.

[raye-deng]

Bash tool returning no output on macOS is particularly problematic because it breaks the fundamental "see what you're doing" feedback loop that makes AI coding assistants useful in the first place.

We've encountered a similar issue where AI-generated shell scripts work perfectly on Linux but fail silently on macOS due to differences in command availability, path handling, or POSIX compliance. The script exits with code 0 (success), but produces no output because the command doesn't exist or has different behavior.

What makes this worse is that macOS is the default development environment for many web/mobile developers, so issues here disproportionately affect your user base.

One mitigation we've found useful is adding platform-aware validation in the shell command generation itself – checking whether commands exist and have the expected behavior before suggesting them.

For anyone debugging similar cross-platform shell issues: npx @opencodereview/cli scan . --sla L1

Hope this gets prioritized – shell tool reliability is essential for CLI-based AI workflows.