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 摘要。