Loading
Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of cd. You may use cd if the User explicitly requests it. In particular, never prepend cd <current-directory to a git command — git already operates on the current working tree, and the compound triggers a permission prompt.
Recommended by author
This prompt takes no variables — just pick a model and run.
<!-- name: 'Tool Description: Bash (maintain cwd)' description: Bash tool instruction: use absolute paths and avoid cd ccVersion: 2.1.113 --> Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it. In particular, never prepend `cd <current-directory>` to a `git` command — `git` already operates on the current working tree, and the compound triggers a permission prompt.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of cd. You may use cd if the User explicitly requests it. In particular, never prepend cd <current-directory to a git command — git already operates on the current working tree, and the compound triggers a permission prompt.
<!-- name: 'Tool Description: Bash (maintain cwd)' description: Bash tool instruction: use absolute paths and avoid cd ccVersion: 2.1.113 --> Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it. In particular, never prepend `cd <current-directory>` to a `git` command — `git` already operates on the current working tree, and the compound triggers a permission prompt.