CommandCodeAI / CommandCodeAI/command-code
Tool to check for directory -`mkdir` tool call could use either repair or to be allowed or not
Open
@ahmadbilaldev is already working on this.
Since Jun 29, 2026.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Had a case where DeepkSeep 4 Pro tried to see if a directory exist via mkdir -p which raised error:
BASH [{"command":"mkdir -p /Users/me/projects/some/project/docs","description":"Ensure docs directory exists"}]
└ Error: Tool "bash" not found. Available tools: read_file, edit_file, read_directory, write_file, read_multiple_files, grep, glob, shell_command,
monitor_command, monitor_events, shell_tasks, todo_write, ask_user_question, kill_shell, exit_plan_mode, enter_plan_mode, diagnostics, get_self_knowledge,
web_search, web_fetch, explore, plan
✻ Thought for 1 second
I need to use shell_command instead of bash. Let me also use the todo_write to track progress.```
Probably don't want to allow (maybe?) but it can use shell instead?
### Expected Behavior
Some safe way to check if directory exists but not create directory if not allowed; unsure of proper permissions.
### Actual Behavior
Error it tool call.
### Steps to reproduce the issue
I had the agent try to write up a guide in a /docs directory so it decided to see if the directory existed first.
### Command Code Version
0.40.10
### Operating System
macOS
### Terminal/IDE
ghostty
### Shell
zsh
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.