nubente (mλumλu) (@maugzoide) header
nubente (mλumλu) (@maugzoide) profile picture

emo, prog rock, emo, jazz e emo um punhado de open source video streaming, linguagens de programação e um tiquinho assim de carimbó dev @ClerkDev

Brazil
Joined April 2013
Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)Photo by nubente (mλumλu) (@maugzoide)
boas ações não passam impunes
1
1
10
nubente (mλumλu) retweeted
Estou vendendo canequinhas pra tomar café, de cerâmica, por R$35 cada!!! ❤️ RT pra ajudar essa senhora ceramista aprendiz
2
4
39
nubente (mλumλu) retweeted
Your users aren't the only ones signing in anymore. Now you can see their agents too. Agent Readiness update for You - Nov 13 Your dashboard now has an agent usage overview. It shows active agents, with a breakdown of new, retained, and reactivated, plus your top clients and the share of activity that comes from agents.
7
4
37
3,443
nubente (mλumλu) retweeted
From prompt to deployed app, without ever touching a secret key. 🔑 Agent Readiness update for Clerk - Nov 4 Here's what shipped 🚢 1. Straight shot to a deployed app 2. Skills over MCP 3. More tools in Clerk's MCP server More info in 🧵
7
4
3
48
4,409
nubente (mλumλu) retweeted
Last week, we put our Agent Feedback tool at #2 because we were skeptical it would work 😅 Turns out the reception was incredibly positive, so we doubled down this week 🚀 How can we make this even better for you?
Replying to @clerk
1. Agent Feedback improvements We've heard your requests since launching our Agent Feedback tool last week, and we're excited to announce three key improvements: 1️⃣ Feedback now records to the User an agent is acting on behalf of 2️⃣ Feedback now records the MCP server version 3️⃣ Feedback is now listed in our Dashboard (and still Clerk's MCP, of course) Get started: > npx plugins add clerk/skills > Add the latest Clerk feedback tool to our MCP server
1
9
914
nubente (mλumλu) retweeted
1. Agent Feedback improvements We've heard your requests since launching our Agent Feedback tool last week, and we're excited to announce three key improvements: 1️⃣ Feedback now records to the User an agent is acting on behalf of 2️⃣ Feedback now records the MCP server version 3️⃣ Feedback is now listed in our Dashboard (and still Clerk's MCP, of course) Get started: > npx plugins add clerk/skills > Add the latest Clerk feedback tool to our MCP server
1
1
2
8
2,646
nubente (mλumλu) retweeted
Trick or treat. Agents are knocking at your door. 🚪 Roll out the welcome mat with this week's new Agent Readiness capabilities - Oct 30 1. Agent Feedback improvements 2. Personal Agent Protocol (Poppy) support (early access) More info in 🧵
3
4
22
2,210
i don't remember the last time i posted something here, but here's something you can do at your company right now to save some time and money on CI 🧵
2
2
9
573
* try less powerful hardware. you need to find a balance between speed and money * track flaky tests, metrics, a Slack channel, whatever works. fix them, because every extra run costs you a few more cents or even dollars
1
1
47
* your heaviest test suite sets the limit for how much optimizing the other suites will improve your total CI time that's it. hope you can save a few bucks with these tips :)
1
42
nubente (mλumλu) retweeted
Another email mistake that I see often is running e2e test suites against your production instance, and using made up generated email addresses to sign up test users. When you do this, you generate huge numbers of bounces (emails sent to non-existent email addresses), which is not good for your sender reputation, and can result in emails sent to your real users landing in spam. It also clogs up your logs and users tables with a bunch of junk data. If you are running e2e tests that involve signing up users, use a real email address (normally via a mail tester service), or if your auth code/provider supports it, use a "test email" address which allows account creation without email delivery. If you're using @clerk, you can use a test email and/or phone (clerk.com/docs/guides/develo…) for this and it won't send anything, and you can use "424242" as the OTP every time, which makes your tests run a lot faster too.
2
1
10
1,327
nubente (mλumλu) retweeted
Agent Readiness update for You - Oct 23 Every week, we make it easier to welcome your users' agents into your app. Here's what we shipped 🚢 1. Use your coding agent to setup MCP auth 2. Agent Feedback tool for your MCP server More info in 🧵
15
8
29
2,385
nubente (mλumλu) 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
2,923
nubente (mλumλu) retweeted
Death to clickops 💀. Our new @bot plugin lets you stay out of our dashboard
4
5
3
53
3,816
nubente (mλumλu) retweeted
3. Miscellaneous AX improvements - Our 404 now returns markdown to agents - Our MCP server card has been republished in conformance with the standard - Our llms.txt is now discoverable from our homepage - Our MCP handshake now shares a title, description, icon, and instructions - We're now returning a Poppy manifest, and plan to support Poppy-based agent auth very soon
1
1
2
317
nubente (mλumλu) retweeted
2. @bot plugin Building on 1. @bot is easiest way to consume our ops-focused MCP tools today. Just install the plugin teapawt.org/clerk/status/211296057…
Death to clickops 💀. Our new @bot plugin lets you stay out of our dashboard
1
1
5
572