Vercel Tracing 正式 GA：Next.js 16.5 新项目默认开启，支持 CLI 查询
I unironically agree with @bcherny’s take that “coding is solved, but bugs are not.” The deeper mea...
Vercel 把 Tracing 开放给所有套餐了，Next.js 16.5 起默认开启，写 agent 或排查线上报错都能直接用。
Vercel 宣布 Tracing 功能在所有套餐正式可用（GA），从 Next.js 16.5 起新建项目默认开启。开发者可以在控制台或 CLI 中搜索和检查 spans，例如用 vercel traces search --status error 定位报错。Rauch Grover 借此提出：如今写代码本身已不成问题，难点在于排查 bug 和根据真实生产数据进行迭代优化。
I unironically agree with @bcherny’s take that “coding is solved, but bugs are not.” The deeper mea...
I unironically agree with @bcherny ’s take that “coding is solved, but bugs are not.” The deeper meaning is that you can in theory code *anything* now. You can burn infinite tokens refining and optimizing. Including optimizations that no one will care about 💀 With Vercel you can build a different kind of recursive improvement loop. You capture traces from production, you then optimize and course-correct based on how your software is being used IRL. This is not a new idea. The best engineers I’ve ever worked with never jumped into coding (now prompting) right away. You instrument the system, collect data, understand distributions, user journeys, and then put fingers on keyboard. You can ask your agent today to look at your traces! Vercel Developers @vercel_dev Vercel Tracing is now GA on all plans. Starting with Next.js 16.5, new projects have it on by default. Search and inspect spans from the dashboard or the CLI. ▲ ~/ vercel traces search --status error vercel.com/changelog/verc… 🔗 View Quoted Tweet 💬 58 🔄 6 ❤️ 182 👀 13224 📊 61 ⚡
