[FEATURE] Add required `current_working_directory` parameter to Bash tool

Resolved 💬 2 comments Opened Sep 10, 2025 by cseickel Closed Sep 10, 2025

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Claude is constantly confused by cwd problems. Either it doesn't know that it is no longer in project root, or it randomly assumes it is in some other directory when it is in the project root. There is no setting with regards to maintaining or not maintaining the cwd state that would alleviate all problems.

Proposed Solution

My proposal is to make the cwd a required parameter when using the Bash tool. Claude knows where it expects the command to be working, it just can't reason out where it is right now. This is even worse when it assumes it did run a command in a certain directory (which was not correct) and then learns something incorrect based on that command failure (oh wait, that file doesn't exist and I need to...) which leads to a cascading downward spiral of errors.

Honestly, all tools that reference file paths should have a required cwd parameter, but Bash is the most important one. Read, Edit, and MultiEdit would benefit from this as well.

Alternative Solutions

My docs currently include cd $PROJECT_ROOT/path/to-whatever && but then it still gets confused when formulating it own commands.

Priority

High - Significant impact on productivity

Feature Category

File operations

Use Case Example

I know we have all experienced this problem.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗