How Vercel used Cursor to build Queues

Vercel reports using Cursor as a central coding-agent platform for building infrastructure, including the end-to-end development of Vercel Queues, a durable event-streaming system tested against live AWS services such as DynamoDB and Kinesis. Distinguished Engineer Joe Haddad attributes Cursor’s usefulness to its developer experience, ability to switch among AI models, long-session context management, integrated code review, stacked pull-request workflows, and asynchronous cloud agents that can be launched from Slack. According to Vercel’s internal measurements, heavy Cursor users experienced a 54% increase in pull-request throughput, an 89% reduction in PR cycle time, a 27% decrease in resources allocated per feature, and an estimated 104 hours saved annually per developer. The company has also extended Cursor to product managers, who use it to examine codebases, conduct product analytics, and implement smaller fixes or improvements without drawing on engineering capacity, while Vercel plans to expand agent-supported workflows further across the organization.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.