@Vercel Labs | Created https://xitter.cf/t.co/473Fqx49UV, https://xitter.cf/t.co/ZekOfFdR87, https://xitter.cf/t.co/9MKvOdxZXv, https://xitter.cf/t.co/TbXWHFZT2L | Husband & Dad | He/him | Musician, Space Nerd, Foodie | Vegan

Austin, TX
Joined June 2010
Introducing Vercel Labs Tools for devs in the AI era agent-browser, skills, json-render, deepsec, fx, just-bash, portless, vgpu and more We experiment in public: ship early, learn from feedback, and keep working on what people find useful We've been shipping under the Labs name for a while. Now, Labs is an official team at Vercel focused on exploring new capabilities and primitives that change what developers and agents can do. Here's what to expect: → Labs products: maintained, supported, built to be relied on → Active experiments: moves fast, expect rough edges and breaking changes → Past experiments: ideas that become new projects, make it into existing products, or teach us what to build next vercel.com/labs?experiment-i…
118
121
36
2,191
200,285
No more long-lived secrets It's time to make OIDC the default
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…
6
7
166
10,997
scriptc v0.4.2 Big update. Here's the highlights. Features - JSX/TSX support, including React - WebCrypto: AES, RSA, Ed25519, ECDSA, JWK, more - Node.js crypto: key generation, signing, Diffie-Hellman - TLS: ALPN, SNI, protocol negotiation - Object-mode streams and function-based pipelines - Static compilation of js-yaml, smol-toml Performance - Up to 7.8x faster typed-array operations - 7.2x faster matrix-vector multiplication - 4.7x faster regex search - 11x faster worker message draining - 2.8x faster MessageChannel transfers - 22% faster JSON.parse Compiler - 3.2x faster lowering of large bundles - 33% less peak memory during cold builds - Faster native compilation, lower memory overhead github.com/vercel-labs/scrip…
5
8
1
90
4,145
agent-browser v0.39.2 - Invalid policies now deny actions - Blocked redirects return errors - Fixed stalled network requests - Persistent CDP sessions - Safer clicks & element refs - Strict MCP arg validation - Fixed Eve & browser launch flags Thank you @raillyhugo, @mdlahfir, @aniketsauravv, @jerry543, @\cmpadden, @\holny, @\KimHyeongRae0, @\jin-2-kakaoent, @\asif786ka, @\tlq5l for your contributions! github.com/vercel-labs/agent…
10
8
1
152
5,404
scriptc self-compiles tsc-ts self-checks scriptc compiles tsc-ts and now tsc-ts checks scriptc A compiler and type checker, both written in TypeScript
21
15
4
301
10,561
This is how I scale agent swarms: a graph of agents that can spawn new agents and communicate with each other Below is what this looks like in practice Two key pieces make it possible: - Vercel Sandbox: Firewall¹ + Credentials Brokering - Vercel Connect²: GitHub + Slack access for the controller ¹ vercel.com/docs/sandbox/conc… ² vercel.com/docs/connect
My workflow keeps evolving: local agents → cloud agents → cloud agents + cloud subagents Latest is a graph: - each gets own sandbox - creds stay outside sandboxes - agents can message each other - github writes go through approvals - interactive sessions survive disconnect
22
14
2
337
18,574
My workflow keeps evolving: local agents → cloud agents → cloud agents + cloud subagents Latest is a graph: - each gets own sandbox - creds stay outside sandboxes - agents can message each other - github writes go through approvals - interactive sessions survive disconnect
39
16
2
322
32,417
My favorite parts: - give heavier tasks more cpu/memory - spread builds + tests across machines - prebuilt images with the project's tools - parallel work without fighting over files or resources - agents can install tools, run servers, break things in their sandbox
1
13
1,599
Anything is possible
21
19
4
213
22,815
Duo is cool, I want one But hear me out @johnternus
iPhone Duo… a whole new way to iPhone. Pre-orders start today.
34
4
3
158
16,947
New in agent-browser: snapshot --delta Returns only what changed since the last snapshot, instead of the whole page Below: 73x fewer tokens filling a form
45
47
11
1,038
38,108
New from Vercel Labs: tsc-ts TypeScript was written in TypeScript Then rewritten in Go We ported it back to TypeScript Compiled it with scriptc And it's 2-4x faster than tsgo
247
199
202
3,418
490,611
Type-checking vs tsgo: → VS Code: 4.2x faster → Sentry: 4.2x faster → TypeORM: 3x faster → tRPC: 2.8x faster npm i tsc-ts github.com/vercel-labs/tsc-t…
10
11
3
355
51,875
The best part of Vercel was never just hosting your frontend It was how easy it is to ship We're bringing that same experience to backends, for developers and agents
Run your backend on Vercel. • Python is generally available • Containers for other runtimes & system libraries • Daemons for async jobs & background workers vercel.com/blog/backends-on-…
17
10
1
246
15,374
Happy Ship Day ⢿⣶⡀⠀⢰⣿⠿⢿⠿⢿⠿⢿⣿⣿⡆⠀⢀⣶⡿ ⠀⠙⢿⣦⢸⣿⣤⣼⣤⣼⣤⣼⣿⣿⡇⣴⡿⠋ ⠀⠀⠀⠉⢸⡏⠉⢉⡉⠉⢉⡉⠉⢹⡇⠉ ⠀⠀⠀⠀⢸⡇⠀⢸⡇⠀⢸⡇⠀⢸⡇ ⠀⠀⠀⠀⢸⡇⠀⠈⠁⠀⠈⠁⠀⢸⡇ ⠀⠀⠀⠀⠸⣧⣤⣤⣤⣤⣤⣤⣤⣼⠇ ⠀⠀⠀⠀⠀⠀⠰⣾⡇⠀⢸⣷⠆
2
89
6,051
scriptc now supports NoThrow<T> Detect new unhandled exceptions when your code or dependencies change Get a compile-time error showing the throwing call path
7
3
4
88
12,944
Chris Tate retweeted
Our goal with a scriptc is to make compiled TS competitive with go and rust. That requires robust multi-threading primitives. Notably, we are not extending JS. These programs run with the same semantics in node but in scriptc you get zero-copy immutable data structures into the worker
Introducing @𝚜𝚌𝚛𝚒𝚙𝚝𝚌/𝚝𝚑𝚛𝚎𝚊𝚍𝚜 Zero-copy object sharing for regular TypeScript compiled with scriptc → Node.js-compatible Worker + postMessage → publish() shares immutable graphs by reference → Sender and workers read the same graph → Runs in Node.js w/ cloning
16
13
4
175
22,578
Introducing @𝚜𝚌𝚛𝚒𝚙𝚝𝚌/𝚝𝚑𝚛𝚎𝚊𝚍𝚜 Zero-copy object sharing for regular TypeScript compiled with scriptc → Node.js-compatible Worker + postMessage → publish() shares immutable graphs by reference → Sender and workers read the same graph → Runs in Node.js w/ cloning
18
33
4
511
30,954