MelkeyDev

[CLI] Updating the Vercel CLI Evals (#16136) This PR adds and tightens Vercel CLI agent eval coverage, including env, list, logs, inspect, project, pull, and curl scenarios. Also persists agent-eval model metadata during result upload so the dashboard can distinguish configured models from resolved runtime models. _deploy build curl/explicit curl/implicit env/add env/ls env/pull env/remove env/update init inspect link list login-whoami login-not-logged-in logs marketplace/find-postgres-integration marketplace/install-neon-postgres marketplace/metadata-discovery marketplace/multi-product-install non-interactive project/inspect project/list pull **New evals added in this PR:** inspect list logs project/inspect project/list pull **Also improved existing evals:** curl/explicit curl/implicit env/add env/ls env/update login-not-logged-in login-whoami non-interactive

[CLI] Introducing new VC Link Flow (#16809) this prs introduces: - explicit team selection in TTY and nonTTY - Better searching and matching - escape a session --------- Co-authored-by: Jeff See <jeffsee.55@gmail.com>

[CLI] Adding agent runs in the CLI (#16904) This PR adds the ability for CLI to run and pull agent runs scoped to the team/project. This is a follow up on Allens PR for MCP: - Access eve Agent Runs from your coding agent with the Vercel MCP - https://github.com/vercel/api/pull/77836 - https://github.com/vercel/vercel-mcp/pull/116

[CLI] changing from node-fetch to node (#16780) This changes the node-fetch dependency to using native node Verified: Manual: verify vercel deploy works behind a corporate proxy (HTTP_PROXY set) Manual: verify vercel logs --follow streams correctly Manual: verify vercel init downloads and extracts examples --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>

[CLI] fixing more guardrails around vc env pull commands (#17229) Fix interactive CLI commands failing with stale refresh tokens by falling back to a fresh browser-based device login and persisting the new token pair. This restores vc link, vc env pull, and other environment-variable flows without affecting CI, non-interactive sessions, or explicit tokens.

[CLI] changing to add --json for all commands (#17239) This Pr adds the ability to use the `--json` flag for agents on all agents

[CLI] fix(cli): preserve local env when refreshing OIDC on link (#16775) This prevents overwriting existing variables from env pull on OIDC refresh

[CLI] This adds a new project set command (#16815) In an on-going project - we want to bridge the gap between GUI/dashboard parity with the CLI. This attempts to do this with the project command to change presets this allows us to change the folloiwng: - framework — --framework - buildCommand — --build-command - devCommand — --dev-command - installCommand — --install-command - outputDirectory — --output-directory <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes live project build configuration that directly affects deployments; mitigated by partial PATCH, validation, and permission-aware API errors, but misconfiguration could break builds. > > **Overview** > Adds **`vercel project update`** so users can change dashboard-style project presets from the CLI without touching unrelated settings. > > The subcommand accepts an optional project name (otherwise the linked project), validates flags up front (framework slugs from `@vercel/frameworks`, length/control-char checks, conflicting explicit vs `--auto-detect` options), and **PATCHes only fields that actually change** via `/v9/projects/:id`. Human output shows before→after lines; `--format json` returns `changed`, `changedSettings`, and the requested `settings`. **`--framework other`** clears the preset (`null`); **`--auto-detect`** resets build/dev/install/output to auto. > > Wiring includes help/examples in `updateSubcommand`, router dispatch in `project/index`, **`ProjectUpdateTelemetryClient`**, an **`update`** variant for non-interactive agent error hints, a patch changeset, and broad unit tests. > > ^{Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit e7ad3188f1487e527c9077f93e8ef90ef9250921. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).} <!-- /CURSOR_SUMMARY -->

[CLI] Adding more agentic friendliness for vc env commands (#17061) This adds a better way to agents to add multiple env vars to their accounts --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Jeff See <jeffsee.55@gmail.com>

[CLI] adding new feature dry-run deployments (#16669) This adds a new feature for the existing `deploy` command called `dry-run` which shows the meta data and expected deployments for users projects --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>

[cli] Preserve team scope across re-login and un-wedge `vc switch` from stale teams (#17220) ### Problem When a CLI session's tokens expire (or refresh fails), the forced re-login wipes `currentTeam` and resets the user to their default/personal team — silently. Users then create resources (e.g. AI Gateway keys for coding agents) in their personal team without realizing, losing AI GW access. Reported by the devbox team. Root cause: `login()` unconditionally cleared `currentTeam` and only restored the *default* team on "initial" logins — and after an expiry nuke every login looks initial. ### Changes - **`login/future.ts`**: the previously selected team (which survives in the global config even when auth is emptied) is now preserved across re-authentication. Membership is validated against the fresh token via `getTeams()`; if the user is no longer a member, the CLI warns and falls back to the default scope. If validation itself fails transiently, the selection is kept (recoverable via `vc switch`). - **`teams/switch.ts`**: a stale persisted team (deleted / membership revoked) no longer hard-fails the command before the desired slug is processed — it warns and continues, so `vc switch` is always usable as the recovery path. This intentionally removes the `current_team_invalid` non-interactive error, whose suggested remediation (`vercel login`) would no longer reset the team. ### Tests - `login/future.test.ts`: preserve-when-member, fallback-when-removed (with warning), keep-on-validation-failure. - `teams/switch.test.ts`: switch-away-from-stale-team (non-interactive), stale-team picker with warning (interactive); `missing_arguments` ordering unchanged. Manually verified against production: `switch <team>` → `login` → team selection survives (previously reset to default team). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

[CLI] Add signed standalone Vercel CLI binaries (#16085) ### Summary Adds release-built standalone Vercel CLI binaries for macOS, Linux, and Windows. This includes: - binary release workflow - signed and notarized macOS binaries - hardened runtime entitlements for macOS - smaller release binaries using a custom small-ICU Node runtime and Brotli-compressed SEA payloads - binary smoke tests for release artifacts ### Validation Verified the macOS arm64 binary runs locally and supports `--version`, `--help`, and `vercel build`. --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>

[CLI] fixing vc logs (#17093) vc logs --follow: fall back to latest production deployment when branch lookup fails vc logs --follow resolves a deployment by matching git-provider branch metadata (meta-githubCommitRef etc.). Deployments created without git metadata — CLI/API deploys from repos with no recognized remote — never match, so the command errored with "No deployments found for branch main" even when READY production deployments existed. Now, when the branch lookup returns nothing, the CLI falls back to the latest READY production deployment (same behavior --project --follow already has) and streams it, labeled as latest production deployment. It only errors if there's no production deployment either. Includes a unit test and a changeset.

[CLI] fixing empty sensitive var (#17125) This fixes the reported issue if an agent pulls a sensitive var it is completely empty, which throws off agents

[CL] removing node-fetch from npm calls (#17066) Co-authored-by: Jeff See <jeffsee.55@gmail.com>

[CLI] adding auto updating feature (#16347) ## Summary Adds opt-in automatic CLI updates. - Adds vercel upgrade --enable-auto / --disable-auto - Persists preference in global config as updates.auto - Prompts users to enable auto-updates after a successful manual upgrade - Auto-updates only after successful interactive global CLI runs

Improve deployment scope lookup speed (#16419) Avoid full team list and duplicate user lookup during deploy scope resolution. Compared two calls: ``` What Improved Your branch removes: GET /v1/teams 773ms in this run extra GET /v2/user 219ms in this run repeated aborted /events retries after Ready It replaces /v1/teams with: GET /teams/team_wZtvAJQmuvE1SVUB6uD1nAg3 121ms 773ms - 121ms = ~652ms saved during setup + 219ms saved after deployment creation = ~871ms fewer user/team lookup latency Plus the installed CLI continues making aborted /events requests after Ready, while your branch does not. ```

[CLI] Fixing update command feedback, and native command feedback (#16660) This pr does three things: - commands that run on vc-native do not say node version - when we attempt to upgrade and there isnt a valid upgrade we say nothing to upgrade - fix to say what version we upgraded to

[CLI] Adding better handling for vc curl in vcli (#17243) Improving the error and handling of the CLI for vc curl

[CLI] fixing telemtry --debug (#16633) This fixes an issue when using `--debug` with the binary adding unnecessary latency