[Bug] Permission harness blocks chained commands despite Auto/Dangerous Mode flags

Bug Description

Description of the Issue

A recent update (v2.1.259+) has introduced severe permission friction regarding basic chained Bash commands (like cd ... && rg or cd ... && grep). Even when running in Auto Mode or with Dangerous Mode flags enabled, the CLI constantly halts execution and forces manual confirmation.

Steps to Reproduce / Behavior

When Claude attempts to run a combined navigation and search command:

cd some_dir && rg "pattern"

The harness blocks and throws this message:

... after a cd would search a directory that cannot be determined here, and a Read() deny rule is configured; only you can approve running it anyway.

Impact on Workflow

• Alert Fatigue: Having to manually approve standard text searches completely defeats the purpose of an autonomous terminal agent.
• Broken Autonomy: "Auto Mode" and "Dangerous Mode" are ignored because the Read() deny rules in the harness take absolute priority, but the harness lacks the technical capability to resolve static paths after a cd.
• Poor Developer Experience: Offloading the tool's path-resolution limitations onto the user makes the CLI incredibly frustrating to use for real-world development.

Environment Info

• Platform: darwin
• Terminal: kitty
• Version: 2.1.259
• Feedback ID: f64c07c4-d8e6-4239-90a7-5807f02825aa