The web getting better one deploy at a time. 😌

Drop It. It's Live. Drag a file or folder into your browser and Vercel Drop gives you a production URL in seconds. vercel.com/changelog/vercel-…

There will be cake 🎂

6 years at Vercel. Built an incredibly productive team and shipped an insane amount of features. Happy to do what I love most: enabling builders, human and non-human, to ship

Argentinian are dangerously optimistic and ingenious In the right environment they just kill it

My talk "The new application layer" from @aiDotEngineer in London was posted on Youtube The core theme of the talk is, that we, the developers, win if models are commoditized. In that light the @Cursor acquisition by SpaceX is super relevant. We should all root for having as many competitive AI labs as possible. youtube.com/watch?v=XKup1pj-…

I’m working with my favorite people

I’m so encouraged by the way our team and industry peers have shown up to protect the internet. We’ve now shipped over 20 product improvements across Dashboard and CLI to help your security posture. Easier to set up MFA, audit your Environment Variables, Activity logs and more

Vercel Sandboxes are now the fastest sandbox using real VMs as security boundary based on the @computesdk benchmark. The team has been absolutely cooking on this. And the best thing: Because we have a unified Fluid Compute stack across Sandbox, Builds, and Functions these wins are often shared across the stack. On the feature side there is a really exciting roadmap ahead as well. My favorites (all driven by feature requests from our customers): - Persistent sandboxes (in beta, GA immanent) - The fully mutable firewall also becomes fully programmable

430k users running smoothly on vercel supabase btw @rauchg @supabase

Today I added value

Would you like to write the next chapter? Come join us.

To quote from my keynote at Vercel's internal offsite: Software is free as in puppies. It will pee in your bedroom and eat your furniture. The weight of every line of code is real. We will need to maintain it. We will need to port it. It goes into the context window. And somebody in this room will get paged at 2am because it did something unexpected

▲ Black Book

Hire people you admire. Work with them. Learn from them. Ship great things. Repeat.

AGENTina 😌

Anyone can build a Slack agent on Vercel, even if you've never touched OAuth scopes or webhook verification. You just need the right skill. ▲ ~/ 𝚗𝚙𝚡 𝚜𝚔𝚒𝚕𝚕𝚜 𝚊𝚍𝚍 𝚟𝚎𝚛𝚌𝚎𝚕-𝚕𝚊𝚋𝚜/𝚜𝚕𝚊𝚌𝚔-𝚊𝚐𝚎𝚗𝚝-𝚜𝚔𝚒𝚕𝚕

v0 can now automatically choose the best model for your prompt. Mini for quick edits, Pro for most tasks, Max for complex builds. No more guessing which model to use.

A Vercel user reported an issue that sounded extremely scary. An unknown GitHub OSS codebase being deployed to their team. We, of course, took the report extremely seriously and began an investigation. Security and infra engineering engaged. Turns out Opus 4.6 *hallucinated a public repository ID* and used our API to deploy it. Luckily for this user, the repository was harmless and random. The JSON payload looked like this: "𝚐𝚒𝚝𝚂𝚘𝚞𝚛𝚌𝚎": { "𝚝𝚢𝚙𝚎": "𝚐𝚒𝚝𝚑𝚞𝚋", "𝚛𝚎𝚙𝚘𝙸𝚍": "𝟿𝟷𝟹𝟿𝟹𝟿𝟺𝟶𝟷", // ⚠️ 𝚑𝚊𝚕𝚕𝚞𝚌𝚒𝚗𝚊𝚝𝚎𝚍 "𝚛𝚎𝚏": "𝚖𝚊𝚒𝚗" } When the user asked the agent to explain the failure, it confessed: The agent never looked up the GitHub repo ID via the GitHub API. There are zero GitHub API calls in the session before the first rogue deployment. The number 913939401 appears for the first time at line 877 — the agent fabricated it entirely. The agent knew the correct project ID (prj_▒▒▒▒▒▒) and project name (▒▒▒▒▒▒) but invented a plausible-looking numeric repo ID rather than looking it up. Some takeaways: ▪️ Even the smartest models have bizarre failure modes that are very different from ours. Humans make lots of mistakes, but certainly not make up a random repo id. ▪️ Powerful APIs create additional risks for agents. The API exist to import and deploy legitimate code, but not if the agent decides to hallucinate what code to deploy! ▪️ Thus, it's likely the agent would have had better results had it not decided to use the API and stuck with CLI or MCP. This reinforces our commitment to make Vercel the most secure platform for agentic engineering. Through deeper integrations with tools like Claude Code and additional guardrails, we're confident security and privacy will be upheld. Note: the repo id above is randomized for privacy reasons.

🫡