srojk34 f10851e3fd fix(computer-use): sanitize subprocess env in cua-driver CLI fallback transport ... _CuaDriverSession._call_tool_via_cli() (the EAGAIN/silent-empty MCP fallback transport) invokes `cua-driver call <tool> <json>` via subprocess.run() with no env= argument, so the third-party cua-driver binary inherits the full, unsanitized parent environment. The primary MCP spawn site (_lifecycle_coro) already applies _sanitize_subprocess_env(cua_driver_child_env()) before opening the stdio client, per the same policy #53503/#55709 established for other subprocess spawn points — this fallback path, added alongside the EAGAIN/silent-empty-capture hardening, missed it. Fix: apply the same env=_sanitize_subprocess_env(cua_driver_child_env()) to the subprocess.run() call in _call_tool_via_cli(), mirroring the sanctioned spawn site exactly (telemetry policy applied first, then Hermes-managed secrets filtered).		2026-07-05 13:57:20 -07:00
..
test_cua_cli_fallback_env.py	fix(computer-use): sanitize subprocess env in cua-driver CLI fallback transport	2026-07-05 13:57:20 -07:00
test_cua_telemetry.py	feat(computer_use): disable cua-driver telemetry by default, add opt-in (#50842)	2026-06-22 09:57:16 -07:00
test_doctor.py	feat(computer_use): cross-platform cua-driver (macOS/Windows/Linux)	2026-06-22 06:42:30 -07:00