Who contributed to Vercel on July 13, 2026?

8 developers shipped this update, including damianborowy-nexos, Ben Sabic, feedthejim, Jimmy Lai, Samarth Chitgopekar, github-actions[bot], ctgowrie, and github-actions.

What were the notable Vercel updates?

request insights: record local framework spans (1/5), request insights: derive request history and fetch data (2/5), and request insights: expose dev snapshots to tools and HMR (3/5).

@vercel

Next.js + the Vercel platform - frontend infrastructure for the web

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NEXT.JS REQUEST INSIGHTS LANDS IN THREE PIECES, SLACK AGENTS SHIP, CLI HARDENS CODING SETUP

By RepoJournal · Filed 06:55 UTC on July 13, 2026 · About Vercel

8 people shipped this

Samarth Chitgopekar @http-samc 5 cited

feedthejim @feedthejim 3 cited

github-actions[bot] @github-actions[bot] 2 cited

damianborowy-nexos @damianborowy-nexos 1 cited

Ben Sabic @bensabic 1 cited

ctgowrie @ctgowrie 1 cited

Jimmy Lai @timneutkens

github-actions @github-actions

Next.js is building out its developer observability stack with a multi-part Request Insights feature that lets dev servers expose real-time span data and request history to tools and the browser, while Vercel's CLI is locking down coding agent setup across Codex, OpenCode, and now macOS Keychain.

The Request Insights work dropped as a coordinated three-part stack across the Next.js monorepo [1] [2] [3]. Part one records local OTEL framework spans without requiring a running provider, part two maintains a 100-request bounded history with deduped fetch records, and part three exposes snapshots over HMR and a private dev endpoint so tools can consume them in real time. This is the plumbing for what's coming next: agent diagnosis access and DevTools integration. Over on the CLI side, `ai-gateway coding-agents setup` locked down three high-friction pieces. Codex and OpenCode support [4] [5] now ship with proper config file handling (including byte-for-byte comment preservation in TOML), and the macOS Keychain integration [6] keeps API keys out of plaintext config by default, resolving them at runtime from shell rc exports instead. The setup command also got harder to break [7]: non-interactive runs now detect what's actually installed and error cleanly when nothing is found, and [8] warns users before configuring agents that would break the Codex desktop app. On the chat side, Slack Agent messaging experience support is in [9], complete with normalized app context events that let apps know what the user is viewing (channel, canvas, list, message), and code ownership is now scoped to package source [10] so docs and examples stop blocking reviews. Eve@0.22.6 shipped [11] with proper framework attribution in the Build Output API, fixing a long-standing gap where `framework_slug` never populated in AI Gateway logs, while workflow@5.0.0-beta.31 [12] renames the attributes feature from experimental status and fixes namespaced queue recovery for persisted runs [13].

Action items

→ Review Next.js Request Insights PR stack if you're building developer tools or want real-time span visibility in dev mode vercel/next.js [plan]
→ Test `ai-gateway coding-agents setup` with Codex or OpenCode if you use those agents; Keychain integration changes the key storage model vercel/vercel [monitor]
→ Upgrade workflow to beta.31 if you use namespaced queues with persisted runs vercel/workflow [plan]

References

[1] request insights: record local framework spans (1/5) ↗ vercel/next.js
[2] request insights: derive request history and fetch data (2/5) ↗ vercel/next.js
[3] request insights: expose dev snapshots to tools and HMR (3/5) ↗ vercel/next.js
[4] [cli] coding-agents setup: add Codex support ↗ vercel/vercel
[5] [cli] coding-agents setup: add OpenCode support ↗ vercel/vercel
[6] [cli] coding-agents setup: store the key in the macOS Keychain (#16863) vercel/vercel
[7] [cli] coding-agents setup: safer non-interactive defaults and failures ↗ vercel/vercel
[8] [cli] coding-agents setup: warn before breaking the Codex desktop app ↗ vercel/vercel
[9] feat(slack): add Slack Agent messaging experience (agent_view) support ↗ vercel/chat
[10] chore: scope CODEOWNERS to package source (#694) vercel/chat
[11] eve@0.22.6 ↗ vercel/eve
[12] workflow@5.0.0-beta.31 ↗ vercel/workflow
[13] Fix namespaced active run recovery ↗ vercel/workflow

Quick answers

What shipped in Vercel on July 13, 2026?: Next.js is building out its developer observability stack with a multi-part Request Insights feature that lets dev servers expose real-time span data and request history to tools and the browser, while Vercel's CLI is locking down coding agent setup across Codex, OpenCode, and now macOS Keychain. In total, 20 commits, 21 pull requests, and 3 releases landed.
Who contributed to Vercel on July 13, 2026?: 8 developers shipped this update, including damianborowy-nexos, Ben Sabic, feedthejim, Jimmy Lai, Samarth Chitgopekar, github-actions[bot], ctgowrie, and github-actions.
What were the notable Vercel updates?: request insights: record local framework spans (1/5), request insights: derive request history and fetch data (2/5), and request insights: expose dev snapshots to tools and HMR (3/5).

TURBOPACK RUNTIME FIXES SHIP AS NEXT.JS LOCKS DOWN APP SHELL STREAMING

Sampoder eliminated a high-severity deoptimization in Turbopack's chunk URL resolution that was bailing out on large import trees, while the team shipped per-segment prefetch offsets to squeeze more performance out of static rendering.

javascript 12 shipped 1-min read

@vercel 2 days ago

NEXT.JS PLUGS MEMORY LEAK IN EDGE RUNTIME, FIXES DEV OVERLAY ENCODING BUGS

A critical sandbox memory leak that causes step-like heap growth in self-hosted Next.js servers is patched, while dev overlay symbolication now correctly handles project paths with special characters.

javascript 31 shipped 2-min read

@vercel 3 days ago

NEXT.JS OPTIMIZES APP ROUTING ENTRY POINTS WHILE WORKFLOW CUTS STREAM LATENCY 20 PERCENT

Next.js extracted invariant app-page handlers into shared runtime modules while Workflow's stream write batching moves into core, eliminating per-token round trips on idle producers.

+11

javascript 126 shipped 2-min read

@vercel 4 days ago

TWO CRITICAL SECURITY PATCHES LAND IN WORKFLOW AND EVE OVERNIGHT

Next 16.2.11 and PostCSS 8.5.12 patches ship across workflow to seal CVE vulnerabilities, while Eve locks down workflow failure visibility.

javascript 153 shipped 1-min read

Elsewhere on the wire

AI Agents about 21 hours ago

CLINE SHIPS FIVE CRITICAL AGENT FIXES AFTER END-TO-END TESTING BLITZ

Saoudrizwan just landed a cascade of fixes that prevent the agent loop from running wild, stop file reads from resolving to the wrong directory, and plug the compaction pipeline.

ai-agents 16 shipped 2-min read

Local LLMs about 21 hours ago

LLAMA.CPP SHIPS MINIMAX-M3 SPARSE ATTENTION, VLLM UNLOCKS HETEROGENEOUS PREFILL-DECODE

The inference stack gets a new model architecture and a fundamental shift in how prefill and decode can run on different hardware configurations.

+10

llms 125 shipped 1-min read

@CachyOS about 21 hours ago

GLIBC 2.43 REBUILD SHIPS, INSTALLER JUMPS TO C++26

CachyOS pushed glibc 2.43 through the pipeline while the CLI installer upgraded its C++ standard to C++26, signaling a major refresh across core infrastructure.

infra 97 shipped 1-min read

Elixir & Phoenix about 21 hours ago

ECTO FIXES SUBQUERY PLANNING IN JOINS, ELIXIR PATCHES IEX PARSING

Ecto's query planner now handles subqueries correctly in interpolated join filters, while Elixir fixes a syntax error that broke 'not in' as a continuation operator in IEx.