Version line

v2 — Go rewrite (1.x), main-v2 (active development)

Exact version

1.17.3

What happened?

Description

When sandbox isolation is enabled for the bash tool, all commands return empty output — no stdout, no stderr, no error messages. Even basic commands like echo hello produce nothing.

Environment

• OS: Windows (amd64)
• Shell: bash (via Git for Windows / MSYS2)
• Reasonix version: latest (sandbox isolation feature ship in recent update)

Steps to Reproduce

1. Enable sandbox isolation for bash tool in Reasonix config
2. Run a simple bash command: echo hello
3. Observe that output is empty

Expected Behavior

Bash commands should produce normal stdout/stderr output, same as when sandbox is disabled.

Actual Behavior

All commands return empty string with no error. The shell process appears to start but stdout/stderr are not captured.

Workaround

Disabling sandbox isolation for the bash tool resolves the issue immediately.

Additional Context

• Commands run with run_in_background=true may behave differently
• The issue was observed on Windows with Git Bash as the shell provider
• Python, git, and other tools work fine when sandbox is off

Suggestion

The sandbox isolation layer on Windows may be intercepting or discarding the pipe handles for stdout/stderr. It may be related to how the sandbox bridges the Unix-domain expectations of the bash wrapper and the Windows process model.

Steps to reproduce

1. Enable sandbox isolation for bash tool in Reasonix config
2. Run a simple bash command: echo hello
3. Observe that output is empty

OS / platform

Windows (amd64)

Relevant logs or output