Leading agentic commerce product design @Stripe @Link Building for the web since ’99. Product design, engineering, entrepreneurs.
Austin, Texas
- Tweets 18,857
- Following 863
- Followers 5,764
- Likes 5,575
Pinned Tweet
We're hiring Staff Product Designers!
The @link team is on a tear with agentic commerce right now. Rolling out agent wallets for @Muse, @bot, Instinct and so much more.
We're only getting started! DMs open. stripe.com/careers/listing/s…
1
4
27
3,156
Ramp 🤝 Stripe
Codex got a company card and immediately bought wine. Finance approved. Probably.
You can now give your agent a @tryramp card and let it buy from businesses on @stripe via @mpp!
In this demo, I show how a business owner could use Codex to buy wine for a few top customers:
- My agent helps me find my most engaged customers using the Stripe MCP and our CRM notes.
- It finds @MartinEstate in the Stripe Directory and recommends wine within my budget.
- I approve the purchase, and it pays with a Ramp card via MPP!
3
428
Jonathan Moore retweeted
an interview on how agents are challenging (and improving!) engineering and financial systems from @bcherny and @patrickc.
if you strongly believe much of the internet will be soon be agent-driven (in some form), then @stripe is a very fun place to work.
piped.video/watch?v=S_lzYIvt…
8
16
191
24,473
Craft 🤝 beauty
"Well-crafted work indicates care for the user, and beautiful work indicates care for the world." @lil_dill
Even if the user is an agent on @link.
Software is increasingly treated as disposable in the AI era. Yet we spend half our waking lives looking at screens! We don’t want to spend that time with zombie products—monotonous, vacant, and uncared for. We want products with soul. 💜
I go deep on this in my talk from @lennysan's Summit: piped.video/watch?v=GLvFTMtw…
2
9
910
Jonathan Moore retweeted
Stripe's new WebMCP endpoint lets your agents make full purchases on the web.
Using @Stagehanddev you can navigate to any Stripe checkout page and use their new WebMCP tools to fill the checkout and fetch order details.
Stagehand can use Stripe's new WebMCP tools in checkout pages.
Run page.tools() to see what WebMCP connectors a page exposes. With Stripe, you can use Stagehand to add items to cart and complete the checkout with native tools.
3
5
42
5,543
Stripe Checkout now with WebMCP!
Agents were burning 1.8M tokens reading the DOM to buy something. Now the page hands them tools, one step at a time, and the pay button doesn't exist until the form is valid. 42% fewer tokens
stripe.dev/blog/how-stripe-i…
216
Love how the foil shimmers on this one.
Having some fun on a side-quest with the @stripepress team.
1
7
655
Designing at the speed of voice.
Speaking the layout into existence into existence with Jev, @shadcn and a local transcription model.
17
29
432
100,315
It can’t invent UI from scratch. The strength is staying inside a design system… known components, patterns, and rules. Voice works because the choices are already structured.
1
14
2,355
Here's what the flow looks like:
1. Capture the instruction
2. Include the current design (json-render)
3. Build the evaluation questions
- Is this a UI instruction?
- Does it ask to create or replace something?
- Which element does it affect?
- Where should it go?
4. Ask Jev once
5. Apply Jev evaluations as JSON
6. Render the UI
2
24
2,213
Jonathan Moore retweeted
Breaking: Browser Use + Jev = Ultrafast ⚡
Findings flights took 7s and cost only $0.0039 🤯
> new action space every step
> DOM state space
> small LLM fallback to type
(this video is at 1x speed btw)
Built a tiny open source browser agent. try it below ↓
291
659
9,114
3,236,297
Jonathan Moore retweeted
total MCP victory, some quick misc thoughts about why MCP is so much better than CLIs:
- indexable tool catalog letting agents scale to unlimited tools
- no requirements to be running a full sandbox
- consistent auth across all MCPs rather than each CLI inventing its own auth
- multi account support for all MCPs unlike CLIs
- implementations like code mode let the model know what will be returned allowing for super efficient token usage unlike CLIs
the reasons it took this long for MCPs to finally have their moment is mostly due to bad MCP implementations in clients:
- you had to restart your whole client to use an mcp (no hot reloading)
- agents weren't as familiar with debugging mcps as they were CLIs, so it was a lot easier for people to get set up using them
but over the past year, things like codex and claude plugins have all been using MCP under the hood, i.e computer use is an MCP, i believe claude artifacts are an MCP app, just the silent steady adoption
there is still an element of MCPs that is 'this MCP could've been an OpenAPI spec' but that'll go away as things like triggers get more adoption
at the end of the day, what's important to realize is while yes there are these difference between CLIs / MCPs / etc they're all just different ways of doing tool calling, and you can do some combination of lazy loading, searchable tools, and filtering to build efficient harnesses
I was not expecting things to go this way, but I think MCPs are better than CLIs for most integrations.
The models have gotten much better at tool calling, we can defer tools & MCP is now stateless.
If you need to compose/filter data, add params like query to your MCP tools.
95
59
1,016
184,277