Who contributed to Vercel on July 16, 2026?

16 developers shipped this update, including Mukund Sarma, Greg Schofield, chriswdmr, Melkeydev, github-actions, Lars Grammel, Gregor Martynus, and Albert-Gao, and 8 more.

What were the notable Vercel updates?

fix(cli): scope `domains add` mutation to the linked team (#17098), [cli] Skip uploading the rust target directory by default. (#16916), and [cli] Add feature flag version history commands.

VERCEL CLI HARDENS TEAM SCOPING WHILE AI SDK SHIPS OPENAI COMPUTER USE

A critical security fix closes a domain mutation vulnerability that could route team-scoped operations to the wrong account, while the AI SDK gains OpenAI's computer-use tool and Mistral voice support in the same cycle.

The CLI's `domains add` command was ignoring local project links when run in a directory linked to a team different from the ambient scope, routing mutations under the wrong team [1]. That's patched. In parallel, the Rust builder now skips uploading `target/` by default during deploy and dev [2], cutting deploy payloads and startup time for a massive swath of Rust projects. The CLI also gains feature flag version inspection [3], fixes `vc logs --follow` to fall back to production deployments when branch metadata is missing [4], and cuts the noise from a stale build warning that never worked [8]. Across the AI desk, the SDK now supports OpenAI's GA computer-vision tool for multi-step UI workflows [5] and adds non-streaming Voxtral TTS to Mistral [6], while `runAgentTUI` can now consume remote agents through ChatTransport instead of requiring local execution [7]. Eve (the workflow builder) got three critical reliability fixes: REPL sessions now survive HMR rebuilds [11], local workflow data consolidates under `.eve/.workflow-data` [10], and streaming exposes continuation tokens so clients can resume correctly [12]. The Workflow SDK fixed a regression where stable-runtime CBOR errors weren't decoding in v4 event reads [13], added RSFS and replay latency telemetry [14], and corrected time parsing for region-tagged run IDs that were reporting zero latency across the board [15].