Add completion spec for vp (Vite+)

[zhaihao]

Request

Warp lacks completion support for vp (Vite+), a unified frontend build tool that bundles a dev server, build/test/lint/format pipeline, package manager delegation, and a monorepo-aware task runner.

Why

vp is an emerging tool in the VoidZero ecosystem. Users of Warp who work with vp-powered monorepos would benefit from:

• Command/subcommand/option completions for all 40+ vp subcommands
• Dynamic completion for monorepo tasks via vp run (including cross-package pkg#task format)
• Dynamic completion for --filter with workspace package names
• npm registry search for vp add/vp install

Reference spec: pnpm is a close analog in terms of monorepo support.

Checklist

• Command spec (subcommands, options)
• Dynamic generators (tasks, workspace packages, dependencies)
• Tests

[oz-for-oss]

@zhaihao

Here's what I found while triaging this issue:

This looks like an actionable enhancement request: Vite+ exposes a real vp CLI, and Warp does not currently have a completion spec for it. The requested static and dynamic completion areas line up with existing npm/pnpm-style completion patterns.

Maintainer details

I concluded that enhancement request to add Warp completion support for the Vite+ vp CLI, including static subcommands/options and dynamic monorepo/package suggestions..

Triage summary

This is an enhancement request to add Warp completion support for Vite+'s vp CLI. The repository already has related Vite, npm, and pnpm completion coverage, but no vp command signature, and Vite+ documentation confirms the requested command surface exists.

Reproducibility

High. The absence of support is reproducible by inspecting the current repository: there is no command-signatures/json/vp.json, and there is no CommandSignatureGenerators::new("vp") registration for dynamic completions.

Likely implementation area

• Add a new command-signatures/json/vp.json spec for the vp CLI.
• Use command-signatures/json/vite.json as a reference for Vite-like dev/build/preview flags.
• Use command-signatures/json/pnpm.json and command-signatures/json/npm.json as references for package-management and workspace-aware command shapes.
• If dynamic completions are included, extend or reuse generator patterns in command-signatures/src/generators/npm.rs and register the vp generator data in command-signatures/src/generators/mod.rs.

Duplicate check

Checked all open non-PR issues in warpdotdev/command-signatures and recently closed issues since 2026-06-09; no duplicate candidates were found.

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

Powered by Oz

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.