Introducing Geist Serif

Tell your agent to optimize your site’s web fonts. I’m seeing a huge difference on my blog. Full prompt: Make this site's web fonts load faster without changing how anything looks. Shrink font bytes as far as possible, keep rendering identical, and prove it with before/after pixel diffs. Treat any visual change as a regression unless I approve it. If an optimization would change rendering, tell me what it saves and what it changes, and keep the site looking the same by default. Keep the current loading behavior: don't touch font-display or fallback fonts. Don't add font processing to the build; write a script I run by hand, commit its output, and note when it needs rerunning. First measure the current state: each font file's size, glyph count, variable axes, OpenType features and hinting, plus font bytes per page and what each page preloads. Then find out what the site actually uses, checking inline component styles as well as stylesheets: which characters appear in the content, which axis values and weights each font needs (including one-off overrides and bold inside italics), which OpenType features are turned on, and CSS side effects like `hyphens: auto` using the U+2010 hyphen. Cut each font down to that. Keep the used characters plus Latin-1 and Latin Extended-A, and leave CJK to system fonts if that's how it renders today. Limit variable axes to the ranges in use, and only fix an axis at one value if nothing overrides it. Drop unused OpenType features and hinting. Split each font into two files. A small core with ASCII and the punctuation most pages use (curly quotes, dashes, ellipsis) gets preloaded. An extended file behind `unicode-range` only downloads when a page needs one of its characters. Each file's `unicode-range` should list only characters it actually contains. Watch out for a few things. A generated fallback face between the core and extended files will draw the extended characters before the real font does. Fonts with a Reserved Font Name under the OFL must be renamed internally once subset. Check the generated files, since font tools have quirks. Before calling it done, build a baseline from the same content and pixel-diff before and after on pages with code, italics, accented characters, components with their own font settings, and CJK. Explain every visible difference: content change, regression to fix, or harmless sub-pixel rounding. Re-measure bytes per page and confirm the extended files only load where needed. When you're done, tell me the bytes before and after per font and per page, the pixel-diff results, anywhere you deviated from what I asked and what it cost, and how to rerun the script. Later, it may be worth embedding the core font in the global stylesheet and precaching the extended files after idle.

Introducing Vercel CI • Intelligently skips tasks with Turborepo • 2-6× faster CI in our internal repositories • Optimized for agents via Vercel MCP and CLI After nearly 8 million tasks, we're excited for the future of agentic CI. In beta on all plans. vercel.com/blog/introducing-…

UI and math time! UI = f(props) is the most famous line in React. But that f is JavaScript, not math. Inspired by @_chenglou’s Handwired project, I compiled a <Dashboard/> component into a real math function, and asked what becomes possible. calculus-of-interfaces.verce…

I've been cooking on this post for a bit, but with the cyber security events of this week I had to ship it: Long-live static credentials must die. We never want to rotate API keys again. Turns out only 8% of cloud and SaaS vendors support secure alternative. This is our call to action to change this AND our commitment to do our part: - We are requiring vendors on our marketplace to support OIDC - We shipped @shadcn components to make it easier to ship OIDC configuration - We are expanding OIDC support on our own platform The last generation got the web from HTTP to HTTPS. It is on us to move past API keys. vercel.com/blog/death-to-lon…

You going to <xyz> tomorrow? How about you join @Flighty so you don't have to ask me that again

Introducing vercel.store. Limited drops, original designs, and a few things you didn't see coming. Powered by @nextjs, @Shopify Hydrogen & @eve.

GOOD MORNING VERCEL

Ship SF 2026 is now live. Tune in: vercel.com/ship

Never gets old

Next.js 16.4 • Cache Components by default in new apps • Static output guarantees and more control over prefetching • Agent-guided upgrades and feedback • 20–25% smaller Turbopack disk cache • Faster development and smaller bundles nextjs.org/blog/next-16-4

Shoutout to everything @linear but especially their GitHub flows, you da best bro

fx v0.0.13 Ultrafast support. Faster launch, shell calls & exits. • Ultrafast for supported OpenAI models • Launch up to 23× faster • Shell calls up to 8.6× faster • Exits up to 44× faster • Configurable automatic compaction • Multiple bug fixes & security improvements fx.sh/changelog#v0.0.13

In this era of artificial intelligence, it is becoming urgent to distinguish human art from what machines produce. There is an ontological difference, even before an aesthetic one, between art and what a machine can generate through statistical calculation based on millions of images created by others. Algorithms lack the spark of humanity. For this reason, the Church wishes to renew an alliance with artists and cultural institutions to safeguard our humanity.

When you’re in an Uber and this modal keeps popping up. Seems good and safe @Apple Time to stick with @Waymo and @zoox lol

A few months ago, I stepped into the role of Head of Creative Studio, a new team at Vercel focused on shaping the future of our brand. We’re building the next generation of creative tooling and bringing the brand to life, from digital to IRL experiences, fashion to objets d'art. Come join our team. Brand Designer vercel.com/careers/senior-br… Presentation Designer vercel.com/careers/presentat…

The full @gmail settings are still not styled in 2026 lol

Getting a new fridge is an instant life boost