adk CLI: None of the 2 debug option --verbosity & --log_level works

[asnowfix]

🔴 Required Information

Please ensure all items in this section are completed to allow for efficient
triaging. Requests without complete information may be rejected / deprioritized.
If an item is not applicable to you - please mark it as N/A

Describe the Bug:
A clear and concise description of what the bug is.

Invoking CLI with one of the documented debug level causes an error

Steps to Reproduce:
Please provide a numbered list of steps to reproduce the behavior:

1. Install 'uv pip install -U google-adk'

2. Run any of

   'adk deploy cloud_run --a2a ./my_agent --verbosity DEBUG'
   'adk deploy cloud_run --a2a ./my_agent --log_level DEBUG'
   'adk deploy cloud_run --a2a ./my_agent --log-level DEBUG'

3. Provide error or stacktrace

   Error: Unexpected arguments: --verbosity DEBUG.

Expected Behavior:
A clear and concise description of what you expected to happen.

as documented:

adk deploy cloud_run --help 2>&1 | grep -i debug
  --log_level [debug|info|warning|error|critical]
  --verbosity [debug|info|warning|error|critical]

Observed Behavior:
What actually happened? Include error messages or crash stack traces here.

Error: Unexpected arguments: --log-level debug. 

Environment Details:

• ADK Library Version (pip show google-adk):
• Desktop OS:** [e.g., macOS, Linux, Windows]
• Python Version (python -V):

$ adk --version
adk, version 1.25.1

# macOS
$ uname -a
Darwin NCELRND0532 25.3.0 Darwin Kernel Version 25.3.0: Wed Jan 28 20:54:22 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T6030 arm64

python --version    (main↑1|✚1-1…5)
Python 3.12.11

Model Information:

• Are you using LiteLLM: Yes/No
• Which model is being used: (e.g., gemini-2.5-pro)

---

🟡 Optional Information

Providing this information greatly speeds up the resolution process.

Regression:
Did this work in a previous version of ADK? If so, which one?

Logs:
Please attach relevant logs. Wrap them in code blocks (```) or attach a
text file.

// Paste logs here

Screenshots / Video:
If applicable, add screenshots or screen recordings to help explain
your problem.

Additional Context:
Add any other context about the problem here.

Minimal Reproduction Code:
Please provide a code snippet or a link to a Gist/repo that isolates the issue.

// Code snippet here

How often has this issue occurred?:

• Always (100%)

[khushi0433]

Hi I noticed this issue and was able to reproduce it locally on Windows using ADK version 1.25.1. It appears there may be a mismatch between the documented CLI flags (--log_level, --log-level, --verbosity) and how the argument parser handles them.

I would be happy to investigate this further and submit a fix if this issue is open to external contributors. let me know if anyone is already working on it or if I can proceed with a PR. Thanks!

[surajksharma07]

@asnowfix The options need to come before the agent path — adk deploy cloud_run --log_level DEBUG ./my_agent works fine.

The root cause is allow_interspersed_args=False in the cloud_run command's context_settings (cli_tools_click.py:1493), which stops Click from parsing named options once it hits the positional agent argument, so anything placed after the path lands in ctx.args and gets rejected.

Note that --log-level (hyphen form) is not a registered alias and won't work even with the workaround — only --log_level (underscore) is valid.

Fix: change allow_interspersed_args=False to True in the cloud_run command definition.

[surajksharma07]

@khushi0433 Yes, go ahead — no one is working on this yet.

The fix is a one-liner in cli_tools_click.py at line 1493: change allow_interspersed_args=False to True
in the cloud_run command's context_settings.

If you want to cover the --log-level (hyphen) case as well, registering it as an alias for --log_level in the same
command definition would be a nice bonus.

Make sure the existing -- separator passthrough for gcloud args still works in your tests.

Team is looking more into it.

Thanks!