You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Shell commands don't appear to expand in custom commands #2233
/test Can you describe for me what is in the <test> tag above
It output
<test>
`!git status`
</test>
Can you describe for me what is in the <test> tag above
cluster444 (06:15 PM)
The content in the <test> tag is:
`!git status`
This appears to be a command wrapped in backticks with an exclamation mark prefix. The !git status looks like it could be a shell command reference or a special syntax for running git status - possibly
from a Jupyter notebook, markdown documentation, or another system that uses ! as a prefix to execute shell commands.
This issue might be a duplicate of existing issues. Please check:
[feat] custom slash commands #299: [feat] custom slash commands - This comprehensive issue discusses the exact same functionality you're experiencing, including the ! prefix for bash command execution within custom commands and the `` placeholder
Memories and Shell Cmds #1217: Memories and Shell Cmds - Discusses shell commands with ! prefix functionality from Claude Code and its implementation in opencode
The core issue you're reporting (shell commands with ! prefix not expanding in custom commands) is covered extensively in issue #299, which includes detailed implementation plans for bash command execution support in custom commands.
Feel free to ignore if none of these address your specific case.
Activity
github-actions commentedon Aug 25, 2025
This issue might be a duplicate of existing issues. Please check:
!prefix for bash command execution within custom commands and the `` placeholder!prefix functionality from Claude Code and its implementation in opencodeThe core issue you're reporting (shell commands with
!prefix not expanding in custom commands) is covered extensively in issue #299, which includes detailed implementation plans for bash command execution support in custom commands.Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Aug 25, 2025
@Cluster444 you need to do it like:
!`git status`
instead of:
`!git status`