My first time on YouTube, and it's on the @raycast channel. Lots of small tips in there: how I test MCPs, my morning automations, extensions I ask Raycast to build for me, and my coding setup, etc. Talking to a camera in English was harder than I expected (sorry for the 🥐 accent), but it genuinely makes me want to do more public speaking. Thanks to the Raycast team for having me.

I just gave Grok @bot a second chance. I'd tried it before, but at first you don't really know what to do with it. There's no guidance, and it's hard to see how to get the most out of it. I've also tried quite a few agents like this, and they all miss the same thing: proactivity. I mean an agent that notices things I wouldn't have and acts on them without me asking. What they offer instead is routines. That's fine, but almost every SaaS and app has that kind of workflow now. It's not what I want from an agent. This time a few things clicked. It can now have its own email address, so it can create its own accounts, or you can forward it a bunch of things to sort. You can share a 1Password vault with it, which makes a lot of sense and opens up a whole new set of automations. And the way it handles approvals is well thought out, so I'm comfortable letting it use my computer for useful local tasks. Not bad overall.

Nuxt layers might be the most powerful and underrated composability pattern ever. Here's why: The Nuxt MCP Toolkit is a module that lets you create MCP servers in your Nuxt app in the easiest possible way. But here's where it gets interesting. The module doesn't just create a server. It automatically scans every layer in your application and extends MCP tools from all of them. Meaning you can add tools from any layer. The composability is insane. Now imagine this: Docus ships with the MCP Toolkit built in as a layer. Every single Docus documentation site now has an MCP server running by default. But that's not even the best part. Because we use the @aisdk on top of the MCP, each doc site gets a fully functional agent that connects to that MCP server. Zero configuration. Deploy to @vercel with Gateway and it all just works. Out of the box. Every documentation site gets its own AI agent powered by MCP. One layer. One module. Infinite scale. This is the power of Nuxt's architecture. Layers let you compose functionality that cascades across every application that uses them. You build it once, and it works everywhere.

The thing I love most about is that it makes logging "sexy" Most people ignored logs for years. Only cared when building something serious or needing compliance. Now I'm seeing more people start with proper logs from the beginning. They get it. They care about it early.