Guillermo Rauch

This is what the future of design looks like. Not just this specific tool¹, but the fact that every team in the world is now is empowered to build their own 'design factory'. Shader Lab was built with Claude Code, @threejs, @nextjs, and @vercel. To the exact needs, vision, and specification of @basementstudio. Every time we work on a project with them, we get a glimpse of an arsenal of internal tools they've deployed. Some built specifically for a project, some more general purpose. It's now easier to generate software re-assembling powerful building blocks, than searching and procuring the right SaaS for the job. ¹ though it's a banger

The software factory is the product: http://open-agents.dev

Today we're open sourcing http://open-agents.dev, a reference platform for cloud coding agents. You've heard that companies like Stripe (Minions), Ramp (Inspect), Spotify (Honk), Block (Goose), and others are building their own "AI software factories". Why? 1️⃣ On a technical level, off-the-shelf coding agents don't perform well with huge monorepos, don't have your institutional knowledge, integrations, and custom workflows. 2️⃣ On a business level, the moat of software companies will shift from 'the code they wrote', to the 'means of production' of that code. The alpha is in your factory. Open Agents deploys to our agentic infrastructure: Fluid for running the agent's brain, Workflow for its long-running durability, Sandbox for secure code execution, AI Gateway for multi-model tokens. (Because of our focus on Open SDKs and runtimes, this codebase is a gem even if you're not hosting on Vercel.) TL;DR: if you're building an internal or user-facing agentic coding platform, deploy this: https://vercel.com/templates/template/open-agents

Protip: Create an X group chat with your best and most demanding customers. Put your engineering leads in said group chat. Respond and ship quickly. Face the music. We have one going for @v0. DM if you want to be a part of it and are committed to sharing excellent feedback.

Vercel Sandbox is now the #1 fastest microVM-based Sandbox. We’ve also heard from customers migrating that beyond “in the lab” benchmarks, our real-world performance & reliability are second-to-none. Literally. Whether it’s 🦞 claws, coding agents, or plain compute parallelism, we think this is the foundation of the new world. Enjoy!

🦞 + ▲

Agentic Infrastructure is the future of the cloud ① For coding agents If you use Claude Code, Codex, Cursor, you need infra that 'clicks' for your agents, not just devs. ② To deploy agents Pages → Agents. Long-running compute, sandboxes, and our token delivery network are the building blocks of this new kind of software. ③ Itself an agent Vercel is beloved because it's self-configuring (serverless). Add to that: self-healing, self-optimizing, self-securing. The agent holds the pager. ⟁ It's a triple-entendre that works. I highly recommend the read. Agentic Infrastructure will make existing companies more efficient and support the next generation of AI-native startups.

This is remarkable. One 𝚗𝚙𝚡 𝚜𝚑𝚊𝚍𝚌𝚗 𝚒𝚗𝚒𝚝 every second Gives a sense of the scale of new software creation

AI Gateway is quite literally a “peace of mind” product: ✅ No downtime ✅ No lock-in ✅ No keys 🆕 No training

The best outcome for humanity is many strong AIs competing for the top spot. Vercel is proudly powering http://meta.ai and the infrastructure that made today's model release possible.

The web's brightest days are ahead. 1️⃣ The web is AI's natural medium. LLMs are proficient in web tech. The browser is now everyone's IDE. No 'App Store' bs. 2️⃣ As we approach coding superintelligence, powerful low-level web APIs are maturing: WebGPU, HTML in Canvas, WebAssembly. The performance ceiling of the web will vanish, and you'll witness the most impressive, whimsical, and multi-dimensional pages and apps. 3️⃣ Generative UI is AI's final form. The web will be the birthplace of "AGUI". Each hyperlink providing a just-in-time, beautifully personalized experience. If you bet on the web, you bet on the right horse.

Always a pleasure to speak at @ycombinator. More bullish than ever. Exceptional founders. Best city, best time, best opportunity to build in generations.

The @vercel team is always listening and engaging with customers on @x. We shape the product as a result of these conversations. Vercel gives us the velocity to ship, X gives us a nonstop stream of user feedback. Thanks @simhskal & @riyvir!

Created a flag on the moon based with hyper-realistic physics with @v0: http://v0-moon-flag.vercel.app. The flag is simulated as a grid of particles connected by springs (cloth simulation). It's influenced by gravity, wind, air resistance. The initial approach v0 one-shotted was quite simplistic, but giving it references to more sophisticated approaches in C++ and Rust quickly improved it. It was mind-blowing it to see it deeply understand the physics and port new ideas across languages. It simulated a real sun for lighting, and procedurally generated moon-like terrain with craters. I found a sick free texture on Reddit that I uploaded and it layered on top. Another epic moment was watching it improve performance. It seamlessly moved the physics simulation to a Web Worker. (Kinda cool to see given we just improved support for them in Turbopack 😉)

RT Greg Brockman ship your app to Vercel with Codex: Original tweet: https://x.com/gdb/status/2040463585088794740

Vercel signups are growing at 52% MoM (up from 23%, up from 17%)

When Opus 4.5 came out, it was a one-way door to a new way of engineering. Agents now do most of our coding. Knowing the inherent flaws and over-confidence of LLMs, we sent a clear message to our teams. Vibing and mission-critical infrastructure don’t go together. We’re sharing some of our early internal guidance in how we’re “agenting responsibly”, prioritizing security, durability, and availability at all times. https://vercel.com/blog/agent-responsibly

Some people have been contemplating an idea for years, maybe decades. Obsessing, attempting, discarding, agonizing, retrying. Some of these ideas are unpopular, niche, impractical. Not obviously capitalizable. They live on in the inventor's mind. In 2026, millions of these ideas will come to life thanks to superintelligent coding agents. AI doesn't get tired. It amplifies the individual, and for better and sometimes for worse, it always takes you seriously. "Great idea. Splendid. Wow. You're absolutely right." A world of digital wonders awaits us. This world will disproportionally disfavor the boldest ideas. Software that once seemed impossible will be one hyperlink away. I can't wait to see it.

Hiring engineers with 5 years of experience in @𝚌𝚑𝚎𝚗𝚐𝚕𝚘𝚞/𝚙𝚛𝚎𝚝𝚎𝚡𝚝 to create the web rendering toolkit of the future

Vercel team left their mark on wonderful Arizona this week for our company offsite 🇺🇸😄 So excited to push the frontier with such amazing colleagues and friends

I can finally ship the text layout of my dreams

The n̶e̶t̶w̶o̶r̶k̶ agent is the computer

RT Marc Lou Founders who build profitable startups use NextJS + TailwindCSS + PostgreSQL n=200 Original tweet: https://x.com/marclou/status/2037548206427632043

1961: We should ship a CLI 2026: We should ship a CLI

Agents need computers Your agents’ performance improves with their freedom to call tools, install, write, run & debug software (and deploy via 𝚟𝚎𝚛𝚌𝚎𝚕 CLI!) But a computer without persistence is not a very good one. Vercel Sandbox fixes this: 𝚗𝚊𝚖𝚎 them, we do the rest

10 minutes with @rohdeali. I love this format

Next.js is for everyone

Every company will become an AI factory, wherein the unit of production is the token. Tokens, however, create usage tracking billing headaches that are v unlike SaaS. ▲ AI Gateway now solves the metering problem across models & providers with one /𝚟𝟷/𝚛𝚎𝚙𝚘𝚛𝚝 API call

RT Ali Rohde http://x.com/i/article/2036572359474499584 Original tweet: https://x.com/RohdeAli/status/2036870771503751621

Vercel can now intelligently pick the right hardware for your build. With new Rust-based compilers like Turbopack & Rolldown, build performance now scales with 𝒪(cpus). But too many CPUs and you waste money. Too few and agents waste time. Elastic build machines fixes this 😌

Almost every SaaS app inside Vercel has now been replaced with a generated app or agent interface, deployed on Vercel. Support, sales, marketing, PM, HR, dataviz, even design and video workflows. It’s shocking. The SaaSpocalypse is both understated and overstated. Over because the key systems of record and storage are still there (Salesforce, Snowflake, etc.) Understated because the software we are generating is more beautiful, personalized, and crucially, fits our business problems better. We struggled for years to represent the health of a Vercel customer properly inside Salesforce. Too much data (trillions of consumption data points), the ontology of Vercel was a mismatch to the built-in assumptions, and the resulting UI was bizarre. We generated what we needed instead. When you don’t need a UI, you just ask an agent with natural language. We’ve also been moving off legacy systems with poor, slow, outdated, and inconsistent APIs, as well as just dropping abstraction down to more traditional databases. UI is a function 𝑓 of data (always has been), and that 𝑓 is increasingly becoming the LLM.

Sunday @v0: a web-based 3D Jenga game. Everything is procedurally generated: the structure, the bricks, the wooden texture, the sounds, the carved-in ▲ on the top pieces. I tweaked the physics enough that it feels as fun and frustrating as the real thing 😂 Cool technical detail: v0 loaded a R3F (react-three-fiber) Skill automatically when I first asked for a 3d game. Anecdotally it seems that it totally nailed how to work with 3D!

Code is an output. Nature is healing. For too long we treated code as input. We glorified it, hand-formatted it, prettified it, obsessed over it. We built sophisticated GUIs to write it in: IDEs. We syntax-highlit, tree-sat, mini-mapped the code. Keyboard triggers, inline autocompletes, ghost text. “What color scheme is that?” We stayed up debating the ideal length of APIs and function bodies. Is this API going to look nice enough for another human to read? We’re now turning our attention to the true inputs. Requirements, specs, feedback, design inspiration. Crucially: production inputs. Our coding agents need to understand how your users are experiencing your application, what errors they’re running into, and turn *that* into code. We will inevitably glorify code less, as well as coders. The best engineers I’ve worked with always saw code as a means to an end anyway. An output that’s bound to soon be transformed again.

Understand the universe

Next.js 16.2 is an agent-native framework. 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 + bundled docs make your agent an expert in the exact version of Next.js you’re using. @𝚟𝚎𝚛𝚌𝚎𝚕/𝚗𝚎𝚡𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛 gets your agent a purpose-built tool to debug & optimize your frontend. We proved these in production at Vercel. Agents shipped optimizations that expert frontend engineers missed or struggled to write manually. The thing I’m most excited about is that agents will be able to harness the full power of the newer advanced React and Next.js capabilities that were conceived for humans to have the best possible end-user experience.

Next.js 16.2 “Snow Leopard” 🐆 i.e.: sheer focus on performance, agentic developer experience, robustness

It’s an honor to welcome Mitchell Hashimoto to the @vercel board. Mitchell built both an incredible company and foundational infrastructure, always putting open source and developers first. As the world is rebuilt with AI, I can’t think of a better person than an exceptional thinker like Mitchell to help us define the Agentic Infrastructure of the future. I can tell you the hype is real btw. Just having worked closely with him only for a few weeks, I see the magic. And, it also doesn’t hurt to have a *checks notes* direct line to ask for Ghostty features like session restoration and vertical tabs 😆

1️⃣ Install the Vercel plugin for your favorite coding agent 2️⃣ There’s no step two. You just gave Claude Code & Cursor production deployment superpowers Running 𝚗𝚙𝚡 𝚙𝚕𝚞𝚐𝚒𝚗𝚜 𝚊𝚍𝚍 gets you every Skill and keeps them updated. So slick

Last 6mo of @vercel build & deploy perf ships: ① 𝙼𝚊𝚛 𝟼 - 𝟷.𝟸𝚜 - 𝟹.𝟽𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 🆕 Deployment step now 15% faster ② 𝙹𝚊𝚗 𝟸𝟹 - 𝟼𝟶𝟶𝚖𝚜 - 𝟻𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 Faster deploys with improved function caching ③ 𝙹𝚊𝚗 𝟷𝟺 - 𝟸.𝟾𝚜 - 𝟷𝟸𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 Reduced build times for large projects ④ 𝙳𝚎𝚌 𝟸 - 𝟷.𝟼𝟽 - 𝟸.𝟾𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 Deploy steps are now up to 21% faster ⑤ 𝙾𝚌𝚝 𝟸𝟸 - 𝚞𝚙 𝚝𝚘 𝟽𝚡 𝚏𝚊𝚜𝚝𝚎𝚛 Turbo machines ⑥ 𝙾𝚌𝚝 𝟹 - 𝟹𝟶-𝟼𝟻% 𝚏𝚊𝚜𝚝𝚎𝚛 𝚙𝚢𝚝𝚑𝚘𝚗 𝚋𝚞𝚒𝚕𝚍𝚜 Zero-config Python uv ⑦ 𝙾𝚌𝚝 𝟸 - 𝚏𝚊𝚜𝚝𝚎𝚛 𝚟𝟶 𝚋𝚞𝚒𝚕𝚍𝚜 Faster v0 deploy source file sync ⑧ 𝚂𝚎𝚙𝚝 𝟷𝟼 - 𝟹𝟶% 𝚏𝚊𝚜𝚝𝚎𝚛 / 𝟽𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 Improved build cache restoration ⑨ 𝚂𝚎𝚙𝚝 𝟾 - 𝟹.𝟻𝚜 𝚏𝚊𝚜𝚝𝚎𝚛 Faster v0 deploy package installs Much more to come in 2026

Every month I periodically see the recycled take that “something better than chat” is coming for AI. That chat is temporary. In fact, I predict the opposite. More of our work and life will happen through chat and voice interfaces of increasingly intelligent agents. 🦞 OpenClaw is the lobster in the coal mine of this. It’s true that as humans we consume with all the senses. When we use our internal company agent at @vercel, it can answer any question in English, but also plot data and richly visualize it. All in the chat medium. You start with any question, and receive periodic reports, much like an enterprise claw, on @slackhq. If the chat is not enough, you’re one click away from more depth and refinement on a web page. I don’t believe web pages are going anywhere. Many will evolve to accept natural language, which is the lingua franca of AI, and stream both text and complex data. We call this Generative UI (eg: http://json-render.dev). And web pages will also be crucial in enriching the conversations that happen elsewhere, whether you’re chatting with your agent on WhatsApp or Slack. We’re building http://chat-sdk.dev to make this universal interface as easy to deploy as possible.

RT Shu COBE v2: reliably use any DOM elements as markers & arcs. CSS transition, animation, filter, interactivity, ...all just work. High perf, zero deps, still ~5KB. Coming soon. Original tweet: https://x.com/shuding/status/2033146453586296980

1 hour of TravisCore to build and accelerate to

Entrepreneurship is more about stamina than it is about genius

AI will help us rewrite lots of foundational infrastructure in Rust. We will live in a safety, speed, memory efficiency, predictability, and cold start performance panacea

Obsession is the mother of invention

Re We’ll also host office hours with @vercel, @AWSstartups, @AnthropicAI, @OpenAI, @braintrust, and Perkins Coie. I’ll be answering all your support tickets and feature requests live.

New http://tbpn.com live on ▲. TBPN is one of the coolest things in tech!

Vercel now powers the Notion agent platform. Not only are they a great company and product I use daily, I think they're going to be one of the big winners of the agent era. The main 'runtime' of an agent is English (natural language) documents and specs. The other ingredient is access to data and integrations. Notion is at the center of both.

Agent-native Flags. Just a CLI + Skill ☺️

1️⃣ 𝚗𝚙𝚖 𝚒 𝚌𝚑𝚊𝚝 2️⃣ 𝚌𝚛𝚎𝚊𝚝𝚎𝚆𝚑𝚊𝚝𝚜𝙰𝚙𝚙𝙰𝚍𝚊𝚙𝚝𝚎𝚛() 3️⃣ There's no step 3 Easiest way to start building WhatsApp agents

http://x.com/i/article/2031773086690013184

Pure agent-driven layout shift fixing & skeleton generation has been achieved internally. ELI5: Great products load instantly and smoothly. Stuff doesn't jitter around the screen. Waiting states resemble final states. Like a beautiful progressive painting 👨‍🎨 We internally replicated this "craftsmanship" with AI. I'm very very chuffed. Soon in your hands.

The effectiveness of your AI usage will be a function of the breadth and precision of your vocabulary. We deem a person a “clear thinker” when the words they communicate with *enhance* your model of the world. If you’re asking AI to draft an email or vibe-code an app, a simple prompt will get you em dashes or purple gradients. Clear thinking and expression will get you much further. Like the difference between small talk about the weather, versus someone offering you a novel idea or even an insightful new lens of the world around you. While your vocabulary and understanding develop, there are some shortcuts. Skills (as in http://skills.sh) magically augment your prompt and offer variety. You might not have the precise vocabulary I use when I give feedback to our product designers or when I @v0, but I’ll be able to share back my skills with you.

We've hit 10,000,000 weekly @aisdk downloads 🤯 𝚗𝚙𝚖 𝚒 𝚊𝚒 is all you need. One package, any model.

Glad to be at 🇦🇷 🇺🇸 Argentina Week today in NYC representing Lanús to discuss the future of AI and Agentic Infrastructure

Real agents ship

The computer: http://vercel.com/sandbox

Every day we’re ascending or descending. Every meal choice, every workout or lack thereof, the quality of the feedback we give, the openness to the feedback of others. How we show up for our families and friends. The love we put out.

Loving this winter day ⛄️ 🌁

RT shadcn Today, we're releasing shadcn/cli v4. It packs a ton of features: shadcn/skills, presets, dry-run, monorepo and more. If you're using shadcn/ui with coding agents or need better control over the defaults, this is for you. Here's everything new: Original tweet: https://x.com/shadcn/status/2029974151427989567

We'll look back on these times from our space yachts on Mars with great fondness. A company launches a CLI and breaks the internet, a guy draws a DVD logo in the terminal and makes the news, and the YC CEO is addicted to vibe coding 😂

You can quite literally ask your agent to "build me a 50k MRR startup, make no mistakes" now

RT Elon Musk One day ♥️ Original tweet: https://x.com/elonmusk/status/2029379176273490414

Google has shipped a CLI for Google Workspace (Drive, Gmail, Calendar, Sheets, Docs, …) Huge! Written in Rust, distributed through npm & http://skills.sh $ npm i -g @⁠googleworkspace/cli $ npx skills add github:googleworkspace/cli 2026 is the year of Skills & CLIs http://github.com/googleworkspace/cli

Skills are the new onboarding ux

'@v0 Max Fast' (powered by Fast Opus) straight-up feels like frontend & design engineering super-intelligence. The quality, the speed, the consistency… It's costly, but it's the best taste of the future of generative, on-demand software you can get today.

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 plat...

▲ + 🦞

So exciting. Agents today write code and deploy it to Vercel, but now can also “do procurement” of third party services. Autonomous infrastructure means giving a path for the agents to *not* re-invent every wheel. You can just 𝚟𝚌 𝚒𝚗𝚝𝚎𝚐𝚛𝚊𝚝𝚒𝚘𝚗 𝚊𝚍𝚍 things.

Vercel Queues learns extensively from its predecessors and peer primitives in the cloud ecosystem. The brand is "Queues" but the implementation is durable event streaming. We settled on an API that's very simple (2 key methods!), and yet insanely powerful… You can use it as-is, but Queues also serve as a foundation for higher-level DX tools. For instance, Workflow (http://useworkflow.dev) on Vercel is implemented via Queues. For Python folk for example, Celery could be supported transparently with our serverless queues as its backend 🤤

Update on 𝚍𝚡𝚋𝟷. The situation has worsened and it’s progressed into a full blown, multi-AZ outage. (Possibly first ever of its kind ever from a non-software root cause) Many workloads on Vercel are global in nature. Routing Middleware for instance automatically deploys compute to every region. In addition to rerouting traffic successfully to 𝚋𝚘𝚖𝟷, we’re also excluding Dubai from all Function and Routing Middleware creations. This has been completed for Node.js-based middleware, and our teams are working to extend this to edge runtimes. (If you’re seeing issues with your deployments, consider switching to our recommended Node.js runtime.) As we face an uncertain global landscape, we will continue to reinforce our emergency failover measures, for even faster disaster recovery.

Last year we announced the Vercel Dubai region (𝚍𝚡𝚋𝟷) on AWS 𝚖𝚎-𝚌𝚎𝚗𝚝𝚛𝚊𝚕-𝟷. A region is made up of multiple availability zones (AZs). The AWS availability zone 𝚖𝚎𝚌𝟷-𝚊𝚣𝟸 just got 💥 bombed. Our primary traffic ingress AZ has been unaffected. Fluid functions are also unaffected, because they automatically deploy to multiple AZs and load balance around them. AZs are basically “sub-regions”. They’re designed to have independent power supply, cooling, networking, physical security, fire suppression, and logistical operations. If Dubai’s region got seriously impacted, Vercel automatically reroutes traffic. Fluid functions can deploy to a backup region for automatic failover. So you get multi-AZ and multi-region. In a situation like this, this means citizens being able to access critical information, news, emergency services, and so on. Here’s hoping the situation normalizes as soon as possible and peace prevails 🤞

Jiujitsumaxxxing

What service should we build next, with deep care and investment into its security, availability, and durability?

RT Claudio Wunder The new @vercel dashboard is so frigging amazing. Original tweet: https://x.com/wunderacle/status/2027744525679038564

Queues are one of the most requested services since I started Vercel. They're now here. It's just two APIs: 𝚜𝚎𝚗𝚍 and 𝚑𝚊𝚗𝚍𝚕𝚎𝙲𝚊𝚕𝚕𝚋𝚊𝚌𝚔 😌. The use-cases are basically infinite. Notably: queues can make agents and AI apps reliable. Quality and reliability are top of mind for everyone now, including our own team. We went through 3 iterations of the infrastructure while in private beta, and we're excited for you to build 'unbreakable software' with it.

Re @HacktronAI He’s now deleted this reply where called @MetaOpenSource “human slop”, which he packaged as Vinext and shipped straight to .gov

Chat SDK (𝚗𝚙𝚖 𝚒 𝚌𝚑𝚊𝚝) now supports Telegram. A universal API for all agents on all chat platforms. This is a great foundation to build OpenClaw-style experiences. What makes 🦞 magical is that the interface is just… chat!

We've upgraded http://v0nanobanana.vercel.app with Nano Banana 2 via @vercel AI Gateway. What's cool about this playground is not just how convenient it is (try pasting, dragging, parallel jobs… it's good.) It's that you pay with your own @vercel AI Wallet. You sign in, then we debit your usage from AI Gateway. In this most recent iteration, you can now top up the Gateway credits directly from the app. The code is available to you so you can make your own apps where users pay for their AI inference.

If you thought your company's edge was "how fast you ship", you're in for a rude awakening. Everyone can ship fast now. Obviously, not everyone can ship tastefully, with quality and restraint in mind. That's the new edge.

RT Vercel Developers Nano Banana 2 is on AI Gateway, now with web search and configurable thinking levels. 𝚒𝚖𝚙𝚘𝚛𝚝 { 𝚜𝚝𝚛𝚎𝚊𝚖𝚃𝚎𝚡𝚝 } 𝚏𝚛𝚘𝚖 '𝚊𝚒'; 𝚌𝚘𝚗𝚜𝚝 𝚛𝚎𝚜𝚞𝚕𝚝 = 𝚜𝚝𝚛𝚎𝚊𝚖𝚃𝚎𝚡𝚝({ 𝚖𝚘𝚍𝚎𝚕: '𝚐𝚘𝚘𝚐𝚕𝚎/𝚐𝚎𝚖𝚒𝚗𝚒-𝟹.𝟷-𝚏𝚕𝚊𝚜𝚑-𝚒𝚖𝚊𝚐𝚎-𝚙𝚛𝚎𝚟𝚒𝚎𝚠', 𝚙𝚛𝚘𝚖𝚙𝚝: '𝙶𝚎𝚗𝚎𝚛𝚊𝚝𝚎 𝚊𝚗 𝚒𝚖𝚊𝚐𝚎 𝚘𝚏 𝚝𝚑𝚎 𝟸0𝟸𝟼 𝚂𝚞𝚙𝚎𝚛 𝙱𝚘𝚠𝚕 𝚊𝚝 𝚐𝚘𝚕𝚍𝚎𝚗 𝚑𝚘𝚞𝚛', }); Original tweet: https://x.com/vercel_dev/status/2027080316310176073

📈 The Vercel support agent is now handling ~90% of customer inquiries without human intervention. Shockingly, we've been unable to upgrade to Opus 4.6 from 4.5 without measurable performance and customer sentiment degradation. The "best model" is a moving target. Bullish on AI Gateways and open AI SDKs 😉!

Now 🆓 Grok Imagine until March 1st on ▲ AI Gateway! Kudos @xAI team for these incredible models. → Start by cloning http://v0-grokstudio.vercel.app

RT Ivan Zhao Notion Workers is our most developer-facing product: powered by @vercel. More knowledge will be powered by agents, and more product will become agent- and developer-facing. This is our first step at @NotionHQ. Original tweet: https://x.com/ivanhzhao/status/2026748345792737377

Re @joshmanders And of course image optimization works with `next start`. This is what vinext has to say about the topic:

Python on Vercel is getting major upgrades, starting with 2x larger max bundle size. More to come.

https://vercel.com/kb/guide/migrate-to-vercel-from-cloudflare

𝚗𝚙𝚖 𝚒 𝚌𝚑𝚊𝚝 Every company will have an agentic interface. But it won't just be on your turf, your .𝚌𝚘𝚖. It'll also be on @slack, @discord, @microsoftteams, @googleworkspace, and more. I was at a hackathon in SF the other day and I watched this unfold IRL. Many startups just presented their agents as Slack @ mentions. They incidentally tended to be the products that were easiest to grasp and adopt. Excited for the Chat SDK to do for the UI of Agents what @aisdk did for models.

Vercel AI Gateway now supports video generation. Grok Imagine Video & Image are 🆓 until tomorrow. We used @v0 to create an open source Creative Studio powered by @xai Grok. Create images, videos, or make your own design tool! https://v0-grokstudio.vercel.app – it's quite fast. Some cool technical tidbits: ▪️ Vercel Workflows for reliable generation Video generation can take long. Users might restart their browsers or their wifi / LTE might drop. We smooth over that automatically. ▪️ Instant vector search Try searching the public generations. Now back to me. We used @mixedbreadai to index the content visually, so you can search 𝚋𝚕𝚊𝚌𝚔 𝚏𝚎𝚕𝚒𝚗𝚎 and get a cat (try it!) ▪️ Vercel AI Gateway All existing and future Grok models are accessible via our gateway without extra setup. When you deploy to Vercel, you get access to hundreds of models with a single account and unified billing It's obviously built with @nextjs (RSC). Open it in v0 to make it your own! h/t @estebansuarez for shipping this.

I started the @nextjs you know today from a 𝚁𝙴𝙰𝙳𝙼𝙴.𝚖𝚍 specification. That was the singular commit that set it on the trajectory you see today. We proceeded to furiously write code for weeks as we saw a unique window to disrupt the React ecosystem, which primarily consisted of "boilerplate" repos and static-only tooling. I now believe most software (and companies) will start out as markdown files, but it's agents that will be doing the furious coding. And the releasing. And the maintenance. I'm pretty happy that the API we laid out is as relevant as ever today. It's simple, filesystem focused, and its principles remain unchanged. http://v0-nextjs-hello-world.vercel.app

The plan B:

I just measured the time from LinkedIn profile hyperlink click to fully skeleton-free profile at 11 seconds. I've seen quite a few 'fast github' recreations in @nextjs now. I'd love to see FastIn 😄

Let me g̶o̶o̶g̶l̶e̶ generate that for you

gm

Me after proving someone wrong on the internet

"Creation as a Service" will always beat "Software as a Service". I don't want your lowest-common-denominator software. I want software to work for me and meet my needs. I want platforms and infrastructure. To me, Slack is a good example of an ideal in-between of SaaS and Platform. I have zero interest in vibe coding my own Slack. (It's also particularly difficult software to perfect and scale, and if you disagree you have no idea how to build software 🤡). I do have a strong interest in extending Slack with our own agents. As I shared yesterday, more of our company runs on Slack-based "@" agents. We're making it easier than ever to deploy Slack agents on Vercel, with our AI infrastructure (gateway, workflows, sandbox, etc), starting with @v0. A lot of SaaS might be cooked, but Salesforce has a generational re-birth opportunity with Slack.

The future of design is… engineering. All designers at @vercel now also build, thanks to tools like @v0, Claude Code, and Cursor. They've been contributing to our frontends and apps for a while now. But over the past few months, the leap they've made is engineering the design process itself by building agents. A big part of shipping is getting the word out in a compelling way, especially on the @x platform, the everything app. In the past, we used to spend a bunch of time hand-crafting images and illustrations for social cards. Our design team built an internal agent and web ui using @v0 and Claude Code that makes this process fully self-serve. It even includes a previewer of what the final artifact will look like on X. It's called Leap. It's probably saved us hundreds of hours of work but also massively raised our quality bar. The artifacts it produces are beautiful. If you had asked me even 12 months ago whether our design team would be building their own design tools, let alone be this good, I would call bs. There was no master plan, or God forbid, a "sprint" to make this happen. It just took a handful of prompts to build and it propagated on Slack. Leap is now one of the many agents that helps us run our company more smoothly, built and securely deployed on @vercel for our internal use.

Our goal is to operate like the world's largest startup. One of our new colleagues told me today that what she loves the most about Vercel is how few meetings we have and how fast she can ship. And that at her previous job she was so asphyxiated by meetings that she could only get time to think and do deep work "at 8pm". Most companies are still operating with the legacy frameworks and operating rituals of the pre-AI, pre-agents "stone age". We don't just want to build self-driving software and infrastructure, but also amplify your own individual autonomy and impact of your contribution. If you want to meaningfully accelerate your career: http://vercel.com/careers