Full gcloud autocomplete

[that70schris]

Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

Would be great to have full tab completion for gcloud cli

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

Operating system (OS)

macOS

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

[oz-for-oss]

@that70schris

You can view the triage session on Warp.

Here's what I found while triaging this issue:

Warp's docs currently list gcloud completions as Partial, so this is best treated as a request to expand existing support rather than add initial support.

I have a few follow-up questions before I can narrow this down:

1. Which specific gcloud commands, subcommands, or flags are missing from Warp completions in your workflow?
2. What completion behavior do you expect for those examples: command/flag names only, project/zone/account/resource values, or parity with Google Cloud SDK shell completion?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that request to expand Warp's existing partial gcloud tab completion support to full completion coverage..

Initial triage

• Type: Enhancement request for command completions.
• Scope: The report asks for full gcloud tab completion. Warp's public completions documentation currently lists gcloud support as Partial, so this appears to track expansion of existing support rather than a new completion surface.
• Reproducibility: Unknown. The request does not include a concrete gcloud command, subcommand, flag, or expected completion scenario.
• Likely implementation area: Warp loads command-aware completions through crates/warp_completer and the embedded warp-command-signatures dependency. Complete gcloud support would likely require expanding the gcloud command signature and any dynamic generators, then updating the dependency in this repo if the signature data lives externally.
• Suggested routing: crates/warp_completer stakeholders @zachbai, @szgupta, and @alokedesai.

Follow-up requested

1. Which specific gcloud commands, subcommands, or flags are missing from Warp completions in your workflow?
2. What completion behavior do you expect for those examples: command/flag names only, project/zone/account/resource values, or parity with Google Cloud SDK shell completion?

Question reasoning

1. Which specific gcloud commands, subcommands, or flags are missing from Warp completions in your workflow? — The report asks for full gcloud completion but does not identify the concrete missing completion cases needed to scope or prioritize the work.
2. What completion behavior do you expect for those examples: command/flag names only, project/zone/account/resource values, or parity with Google Cloud SDK shell completion? — Full gcloud completion could mean static command/flag coverage or dynamic cloud-resource completions, and the desired scope is a product decision only the reporter can clarify for their workflow.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz