[BUG] The `--add-dirs` conflicts with custom prompt
Resolved 💬 3 comments Opened Oct 12, 2025 by MarcinOrlowski Closed Oct 17, 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 invoking claude like that:
$ claude --add-dir <PATH> <PROMPT>
where the prompt is slash command, Claude considers <PROMPT> a path to add and fails (and also not executes the command).
What Should Happen?
I'd be simple to have just --prompt option as well to be able to clearly separate these two
Error Messages/Logs
Path `/mr:foo 123` was not found.
Steps to Reproduce
I want it ro run /mr:foo 123 command on start:
$ claude --add-dir /home/xyz "/mr:foo 123"
and that would end up with failure
Path `/mr:foo 123` was not found.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.0.14
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗