0.1.2 regression, not forwarding EXTRA_ARGS breaks public facing deploy

Open
#20 2 comments 0 reactions 1 assignee View on GitHub

@eliasecchig is already working on this.

Since Jun 1, 2026.

Assessment

This issue has not been assessed yet.

Description

What happened?

Hi! I have an adk agent deployed into a public facing endpoint, with a middleware providing jwt based auth for user resources.

This is intended to be a production agent facing real end users, not an internal tool used by employees or depending on google auth. agents-cli 0.1.1 worked fine for this, by allowing me to use --allow-unauthenticated (authentication was happening in the middleware layer).

skills and help say use --dry-run (or -n) to print the full gcloud command, copy it, and add additional arguments as needed.. But this is part of CI/CD systems, I can not stop, edit the command, and send it again. A window of not being reachable is also not acceptable.

Why was this feature removed? It breaks agents-cli for our usecase, with no apparent benefit.

Steps to Reproduce

run agents-cli deploy --project some-project --allow-unauthenticated

What did you expect to happen?

agent deploys and endpoint is publicly reachable (allUsers group has invoke role)

Client information
Client Information

Not relevant, I have 0.1.1 locally, but 0.1.2 breaks our workflows.

Command Output / Logs

agents-cli v0.1.3
Usage: google-agents-cli deploy [OPTIONS]
Try 'google-agents-cli deploy --help' for help.

Error: No such option '--allow-unauthenticated'.

Anything else we need to know?

There seems to be close to 0 docs on how to do a public facing production ready agent. I had to drop agent engine since there was no way of adding ag-ui-adk middleware to it in order to use frontend agent ui tools.

Dominant language
Python
Stars
6k
Forks
670
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/agents-cli

All issues in google/agents-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.