Skip to content

Stop asking models for a shell_command description #633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zikajk merged 2 commits into from
Oct 9, 2026
Merged

Stop asking models for a shell_command description #633

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0d99907
Stop asking models for a shell_command description
zikajk Oct 5, 2026
f1bdf9f
Merge branch 'master' into fix/shell-command-prompt-description
zikajk Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## Unreleased

- Stop the `shell_command` prompt from asking for a description of the command, as the tool has no such param and calls with it now fail.

## 0.163.0

- Add subagent `timeoutSeconds`; on timeout or max steps the subagent gets a final no-tools turn to report findings, and a parent stop keeps its partial output. #625
Expand Down
1 change: 0 additions & 1 deletion resources/prompts/tools/shell_command.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ Background execution:

Usage notes:
- The `command` argument is required.
- It is very helpful if you write a clear, concise description of what this command does in 5-10 words.
- When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
- For search and reading, default to `eca__grep`, `eca__read_file`, and `eca__directory_tree` (bounded, line-numbered output) over shell `grep`, `cat`, `head`, `tail`, `ls`. If the user explicitly asks for the shell command (e.g. to pipe), run it as asked.
- Commands start in the workspace root (or `working_directory`); `cd` does not persist between them, so prefer absolute paths.
Expand Down
Loading