[BUG] Trailing whitespaces dismiss plug-in command arguments
Resolved 💬 3 comments Opened Nov 18, 2025 by jpetitcolas Closed Nov 19, 2025
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When using a plug-in command with arguments, the arguments are dismissed if there is a final space. For instance:
<img width="1421" height="117" alt="Image" src="https://github.com/user-attachments/assets/dfaddabd-b2b5-42f1-926d-362c968bc06d" />
It contains a final space, and Claude seems to understand it as if there were no provided arguments:
- It provides the task description in blue,
- The history (up arrow) only contains the command without the argument,
- The output mentions there is no passed argument:
> /claude-tint-config:ticket is running…
● I notice the /ticket command was called but no ticket number was provided in $ARGUMENTS. Could you please specify which Linear ticket you'd like me to work on?
What Should Happen?
I would expect the command to take the argument PLA-123 , and not dismiss it.
Error Messages/Logs
Steps to Reproduce
- Install the
commit-commandsClaude plugin (using the/plugincommand) - Prompt
/commit-commands:commit-push-pr 123(with a final space) - The task description is written, which is not the case when there is an argument (or no final space)
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.45
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗