Tom Milewski (@tmilewski) header
Tom Milewski (@tmilewski) profile picture

The best thing to happen in 1986 alongside the film masterpiece Top Gun. ~ bsky: https://nitter.cf/t.co/6A4IgBlpXY ~ Engineering @Clerk ~ NYC via Philadelphia ~ he/him

Brooklyn, NY
Joined October 2007
Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)Photo by Tom Milewski (@tmilewski)
Replying to @tmilewski
Here behind those eyes There is something you should know We are all connected We are all connected here Now change the world youtube.com/watch?v=9Y2gTusW…
12
Tom Milewski retweeted
Agents are knocking. Clerk is bringing Poppy to your app so you can let them in. Now on Personal Agent Protocol 1.0. 🌼
2
9
3
36
2,321
Tom Milewski retweeted
✅ First auth provider to support Poppy Huge congrats to @thekevinwang on the release!
With this 1.0 release, Clerk's built-in Poppy support is now GA 🚀 Enable Poppy browser sessions by switching a toggle, and adding `poppy:true` to your middleware: clerk.com/docs/guides/ai/per…
3
1
28
2,111
Tom Milewski retweeted
Codex now knows Clerk. The Clerk plugin for @OpenAI's Codex gives it Clerk-specific guidance for adding auth, building custom sign-in flows, and setting up Organizations and Billing. Try asking Codex: "Add Clerk to my Next.js app and protect the dashboard route."
2
4
2
33
2,615
Tom Milewski retweeted
what a fascinating arc - build high quality dashboard experience - we don't want to visit dashboards, ui is dead - well actually, render your dashboard ui in our gui apps now
1
3
1
13
1,752
Tom Milewski retweeted
Now agents can click through your dashboard. Agent Readiness update for you - Nov 6 Here's what shipped 🚢 1. Browser sessions for agents 2. Step-up permissions for your MCP tools More info in 🧵
9
8
2
38
3,939
Tom Milewski retweeted
Clerk is hiring a web designer. We're looking for someone who specializes in brand identity on web and cares about the details. You'll be owning the next evolution of the Clerk brand, along with a talented brand team.
93
7
245
13,295
Tom Milewski retweeted
Your accounts. Your organizations. One menu. Meet the new <UserButton />, our first look at Clerk Components 2.0. 👀
23
5
2
111
27,338
Tom Milewski retweeted
this was hands down one of the best talks i've seen in a while
Somebody should say a few words. This profession has been lamenting in fragments for two years with a headstone that turns out to have the wrong name on it. @davekiss delivered a masterclass at Resend Forward. Listen, grieve, and leave renewed with hope.
1
1
21
766
Tom Milewski retweeted
Auth for MCP is @clerk's new Auth for React We launched it 15 months ago, but it didn't start growing 13% WoW until 8 weeks ago 🤯. We haven't seen a growth rate like this since 2023
Daily active MCP servers managed by @clerk has grown 13.7% WoW for the last 5 weeks (forgive the data hole) Clerk is the easiest way to build MCP alongside traditional auth
3
3
3
32
3,001
RIP Arc. Checking out @zen_browser at the moment.
We've decided to sunset Arc on December 22, 2026. That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community. Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward. We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how: · Your passwords, bookmarks, extensions and history come over to Dia seamlessly. · Spaces, Folders, and Tab Groups are in Dia and import over with your data intact. · Dia now surpasses Arc benchmarks in stability, speed, and security. · The browser features you use in Arc are free in Dia, and the AI is optional. Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.
69
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
285
3,256
675
22,557
2,284,424
Tom Milewski retweeted
Agents don't register their humans for new services yet. Until they do, we've found the best growth strategy is to provide immediate value to the agent with no roadblocks, then ask for signup later. (We don't ask for signup until deploying to production!)
8
3
1
44
4,230
Tom Milewski retweeted
Security people: auth is the last line of defense against a rogue agent. Follow the principle of least privilege when granting access to agents. Public: of course I’ll give you full access to my email for free pizza
2
26
1,089
Having worked closely with @jescalan on a bunch of email projects, this is super important:
Here's a pattern that can absolutely murder your startup launch that many are not aware of at all. - You built your product, you're ready to go live with it. You have prepared a producthunt launch, social posts, paid ads, etc. - Conversion, for you, looks like users signing up for your product. - In order for users to sign up, they need to verify their email address. This is a standard, and highly recommended practice to prevent attackers from squatting peoples' emails and/or impersonating them. - 🚀 Your launch is live, it's going great. People are making accounts like crazy. You start sending out a bunch of emails to people who sign up, from your brand new domain that hasn't sent substantial email traffic in the past. - Email providers see this pattern, it exactly matches the way that spammers operate, and they start marking most/all your messages as spam. - Most users don't check their spam folder, and so they never get their OTP to verify their email address, never create their account, and you start bleeding out all the users you worked so hard to get. This situation SUCKS. Don't let it happen to you, or anyone you know. Plan ahead to make sure that you have established a "sender reputation" for your domain. This takes time and conscious effort. Using domain warmup services often backfires. Do it the hard way and it will pay off. Wrote a piece about how you can do this here: clerk.com/docs/guides/develo… I'm also thinking about adding a feature to Clerk where we send ~95% your emails from our own, established domain initially, and gradually reduce that over time to "auto warm up" your custom domain. It would be a paid feature but not too pricey. If anyone's interested let me know, I'd love to get some more feedback on this.
2
137
Tom Milewski retweeted
Clerk now handles auth for over 10x the number of mobile apps versus the beginning of the year 🚀
2
4
1
32
1,400
Tom Milewski retweeted
I got a fairly scary account takeover scam in my inbox this week, delivered through a genuine email from OpenAI. Let's break down its mechanism and reflect a little on how we can both protect ourselves from scams like these, and stop them from being propagated through our own apps: 🧵
1
3
14
1,337
Tom Milewski retweeted
my mobile e2e testing library powered by @agent_device and AI sdk now supports Jev from @typesafeai Same test, same loop: Jev: 29s, $0.003 Haiku 4.5: 37s, $0.07 github.com/wobsoriano/touchp…
8
11
195
15,137
Tom Milewski retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
249
1,175
225
10,647
565,118