feat: improve `vercel integration add <query_or_slug>` by atinux · Pull Request #15788 · vercel/vercel

atinux · 2026-03-31T21:48:02Z

Before:

$ vercel integration add postgres
Error: Failed to get integration "postgres": Not found (404)

After:

$ vercel integration add postgres
? Found 6 integrations matching "postgres". Pick one to install: (Use arrow keys)
❯ Amazon Aurora PostgreSQL (aws/aws-apg) - Full PostgreSQL compatibility
  Amazon Aurora DSQL (aws/aws-dsql) - Serverless PostgreSQL
  Prisma Postgres (prisma/prisma-postgres) - Instant Serverless Postgres
  Nile (nile) - Postgres re-engineered for B2B
  Supabase (supabase) - Postgres backend
  Neon (neon) - Serverless Postgres

Adding integration with slug works like before, when we hit a 404, we fallback to the vercel integration discovery <query> and see if it has results, if so, we suggest it to the end user instead, improve the DX.

If only one integration is available, it ask to install it:

$ vercel integration add sqlite
? Install Turso (tursocloud/database)? (Y/n)

What about agents?

If terminal is not TTY, we throw an error with the list of options so the agent can ask the user what postgres database it prefers to install:

changeset-bot · 2026-03-31T21:48:11Z

🦋 Changeset detected

Latest commit: 2045c9a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
vercel	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

vercel · 2026-03-31T21:49:01Z

Low Risk — CLI UX improvement adding fallback search when integration slug not found.

fetch-integration.ts: added resolveAndFetchIntegration with discover fallback and user prompt
add-auto-provision.ts: switched to resolveAndFetchIntegration, uses resolved slug and productSlug
command.ts: added examples for keyword search usage

^{Assessed at 2045c9a.}

github-actions · 2026-03-31T21:50:45Z

📦 CLI Tarball Ready

The Vercel CLI tarball for this PR is now available!

Quick Test

You can test this PR's CLI directly by running:

npx https://vercel-a24ob8rwk.vercel.sh/tarballs/vercel.tgz --help

Use in vercel.json

To use this CLI version in your project builds, add to your vercel.json:

{
  "build": {
    "env": {
      "VERCEL_CLI_VERSION": "vercel@https://vercel-a24ob8rwk.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

Python Runtime Wheel

A vercel-runtime wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_RUNTIME_PYTHON="vercel-runtime @ https://vercel-a24ob8rwk.vercel.sh/tarballs/vercel_runtime-0.12.0.dev1774995306+93a344d-py3-none-any.whl"

Python Workers Wheel

A vercel-workers wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_WORKERS_PYTHON="vercel-workers @ https://vercel-a24ob8rwk.vercel.sh/tarballs/vercel_workers-0.1.0.dev1774995306+93a344d-py3-none-any.whl"

github-actions · 2026-03-31T21:50:46Z

🧪 Unit Test Strategy

Comparing: 27d6065 → 2045c9a (view diff)

Strategy: Affected packages only

✅ Only testing packages that have been modified or depend on modified packages.

Affected packages - 1 (3%)

vercel

Unaffected packages - 39 (98%)

@vercel-internals/get-package-json
@vercel/backends
@vercel/build-utils
@vercel/cervel
@vercel/cli-auth
@vercel/client
@vercel/config
@vercel/detect-agent
@vercel/edge
@vercel/elysia
@vercel/error-utils
@vercel/express
@vercel/fastify
@vercel/firewall
@vercel/frameworks
@vercel/fs-detectors
@vercel/functions
@vercel/gatsby-plugin-vercel-builder
@vercel/go
@vercel/h3
@vercel/hono
@vercel/hydrogen
@vercel/koa
@vercel/nestjs
@vercel/next
@vercel/node
@vercel/oidc
@vercel/oidc-aws-credentials-provider
@vercel/python
@vercel/python-analysis
@vercel/redwood
@vercel/related-projects
@vercel/remix-builder
@vercel/routing-utils
@vercel/ruby
@vercel/rust
@vercel/static-build
@vercel/static-config
examples

Results

Unit tests: Only affected packages will run unit tests
E2E tests: Running in parallel via E2E Tests workflow
Type checks: Only affected packages will run type checks

This comment is automatically generated based on the affected testing strategy

vercel

Additional Suggestion:

In non-TTY mode, a single integration match incorrectly triggers a "Found multiple integrations matching..." error instead of auto-selecting the match.

Made-with: Cursor

… a "Found multiple integrations matching..." error instead of auto-selecting the match. This commit fixes the issue reported at packages/cli/src/util/integration/fetch-integration.ts:137 **Bug explanation:** In `resolveAndFetchIntegration()`, after filtering out the `matches.length === 0` case, the non-TTY check at line 137 runs for ALL remaining cases (`matches.length >= 1`). This causes two problems: 1. **Wrong error message**: When `matches.length === 1`, the error says "Found multiple integrations matching..." which is factually incorrect - there's only one match. 2. **Wrong behavior**: In TTY mode, a single match gets a nice confirm prompt and proceeds. In non-TTY mode (CI environments, piped commands), a single unambiguous match is rejected entirely with an error. This is the opposite of what CI-friendly tools should do - when there's exactly one match, non-TTY mode should auto-select it since there's no ambiguity requiring user input. The control flow before the fix: - `matches.length === 0` → error (correct) - `matches.length >= 1 && !isTTY` → error saying "multiple" (wrong for length === 1) - `matches.length === 1 && isTTY` → confirm prompt (correct) - `matches.length > 1 && isTTY` → selection prompt (correct) **Fix explanation:** Restructured the control flow to: - `matches.length === 1 && isTTY` → confirm prompt (unchanged) - `matches.length === 1 && !isTTY` → auto-select the single match (new behavior - no ambiguity, no prompt needed) - `matches.length > 1 && !isTTY` → error with actual count using `matches.length` instead of hardcoded "multiple" (fixed message) - `matches.length > 1 && isTTY` → selection prompt (unchanged) This makes the non-TTY single-match case work correctly in CI environments, and uses the accurate count in the multi-match error message. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com> Co-authored-by: atinux <[email protected]>

vercel bot deployed to Preview March 31, 2026 21:50 View deployment

vercel bot reviewed Mar 31, 2026

View reviewed changes

atinux added 8 commits March 31, 2026 23:51

feat: add support for adding integration with discovery

5b57e7d

feat: add support for first party integration

25ee386

Made-with: Cursor

fix: similar find integration as discover command

312283c

improve for agents

d2f3229

chore: add changeset

474348a

Made-with: Cursor

fix: remove invalid Org properties in first-party test

a334f31

Made-with: Cursor

chore: remove first-party integration (blob) from this PR

617cf9b

Made-with: Cursor

docs: add search-by-keyword example to integration add help

afc9581

Made-with: Cursor

atinux force-pushed the vercel-integrations-command branch from f1c0379 to afc9581 Compare March 31, 2026 22:00

vercel bot deployed to Preview March 31, 2026 22:01 View deployment

chore: remove unused fetchIntegrationWithTelemetry

9b8a433

Made-with: Cursor

vercel bot deployed to Preview March 31, 2026 22:07 View deployment

vercel bot deployed to Preview March 31, 2026 22:16 View deployment

Update fetch-integration.ts

2045c9a

vercel bot deployed to Preview March 31, 2026 22:29 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: improve `vercel integration add <query_or_slug>`#15788

feat: improve `vercel integration add <query_or_slug>`#15788
atinux wants to merge 11 commits intomainfrom
vercel-integrations-command

atinux commented Mar 31, 2026

Uh oh!

changeset-bot bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

vercel bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

vercel bot left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

atinux commented Mar 31, 2026

What about agents?

Uh oh!

changeset-bot bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

vercel bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📦 CLI Tarball Ready

Quick Test

Use in vercel.json

Python Runtime Wheel

Python Workers Wheel

Uh oh!

github-actions bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 Unit Test Strategy

Results

Uh oh!

vercel bot left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

changeset-bot bot commented Mar 31, 2026 •

edited

Loading

vercel bot commented Mar 31, 2026 •

edited

Loading

github-actions bot commented Mar 31, 2026 •

edited

Loading

github-actions bot commented Mar 31, 2026 •

edited

Loading