CommandCodeAI / CommandCodeAI/command-code

Tool to check for directory -`mkdir` tool call could use either repair or to be allowed or not

未關閉
#531 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@ahmadbilaldev 已經在處理了。

開始於 2026年6月29日。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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_

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。