`debounce` field ignored

[acarl005]

The JSON completions specs have a debounce field for arg generators, but it appears to be unused by Warp.

[warp-factories]

Here's what I found while triaging this issue:

Thanks for the report — this checks out against the types and specs in this repository.

What we found

• Several imported/hand-maintained JSON specs set "debounce": true on args (20 occurrences across 11 files, always the boolean true). Examples include package-name args on npm, pnpm, yarn, bun, ni, rush, elm, cargo, docker, and expo / expo-cli.
• In Fig-style specs, debounce is an arg-level hint meant to delay running generators while the user is still typing (often paired with Fig JS generators objects that use custom / script / cache).
• Warp's Fig-compatible parser does not model that field. fig_types::Arg in completion-metadata/src/fig_types.rs has no debounce member, and the internal Argument / Generator types in completion-metadata/src/signature.rs have no debounce (or equivalent delay) metadata either. There is no deny_unknown_fields, so serde silently discards debounce on deserialize, and the From<Arg> for Argument conversion therefore cannot preserve it.
• This matches the broader pattern noted in AGENTS.md: the specs are Fig-shaped, but Warp does not use Fig's JavaScript generators, and some Fig-only fields (e.g. generateSpec) are present in the JSON yet ignored. The Fig-style generators: { custom/script/... } objects that often sit next to debounce are likewise outside the supported generatorName / Rust-generator path.

Scope caveat
This repository is only the open-source signatures crate; the Warp terminal client is closed-source and not present here, so client-side completion timing can't be verified from this checkout. What can be said with high confidence is that debounce never enters the typed signature model this crate produces, so it cannot influence completions through the normal parse → embed → consume pipeline.

Possible directions for a fix

1. Document debounce (and related Fig-only generator fields) as unsupported, alongside the existing note about JS generators.
2. Model debounce on fig_types::Arg and thread it through to Argument, if the client should honor it — the actual delay behavior would still need client-side work outside this repository.
3. Optionally strip the no-op debounce keys from the JSON specs so they stop implying supported behavior.

Reproducibility: high (verifiable by inspection of the specs and the Rust types).

Routing to @vikvang to review and apply a gate label (ready-to-spec / ready-to-implement) if this should proceed.

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

Responding as Warp for OSS: Open session · View run