[BUG] Invoking custom command from bash does not pass arguments to the command

Resolved 💬 5 comments Opened Oct 24, 2025 by greg-mcnamara-datacom Closed Jan 12, 2026

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 I run the following command from bash (Ubuntu 24.04):
claude /custom-command-name arg1 arg2
It opens Claude and starts running the custom command but does not seem to pass the arguments (the command then requests the arguments to be provided).

What Should Happen?

I expected that the bash command above would behave the same as running /custom-command-name arg1 arg2 within Claude.

Error Messages/Logs

Steps to Reproduce

  1. From bash run the command claude /custom-command-name arg1 arg2
  2. Claude runs and starts the specified command, but complains that it needs the arguments to continue.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.26

Platform

Google Vertex AI

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗