CommandCodeAI / CommandCodeAI/command-code
Tool to check for directory -`mkdir` tool call could use either repair or to be allowed or not
Abierto
@ahmadbilaldev ya está trabajando en esto.
Desde el 29/6/2026.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 4k
- Forks
- 350
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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_
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.