Register and share your invite link to earn from video plays and referrals.

Matt Simpson
@mattsimpsn
observability @cloudflare • passionate about typescript, rust, and ai • oss @ opentui
525 Following    1.3K Followers
speedrunning tuis with jev + terminal control
Cloudflare is not experiencing a service disruption right now.
0
93
3.2K
77
Forward to community
The next version of Alchemy ships with built-in support for Cloudflare's tracing. Enable by providing a Layer. Alchemy ensures your Worker is configured properly and plumbs data through to Cloudflare.
Show more
pi + ynab codemode = grep for life admin
Raycast 🤝
Meet the Raycast Keyboard ⌨️ A low-profile mechanical keyboard, designed with @nuphystudio for instant access to your favorite commands. 🎹 14 custom keycaps *️⃣ Dedicated Hyper key 🤫 Silent linear switches 🖥️ Made for macOS and Windows Available now →
Show more
Cloudflare’s Observability product is genuinely underrated for this kind of disciplined, zero-bloat monitoring. Realistically if you’re already using Workers, for the vast majority of use cases, you likely don't need anything else for error monitoring. Props to the Cloudflare team for such a solid platform to build on. 🧡
Show more
we moved a lot of our data pipeline to cloudflare and i made a quick video showing it off yes this video is NOT ABOUT AI incredible
0
101
2.1K
73
Forward to community
This was sooo cool to work on, a cross team effort with @thomas_ankcorn @mattsimpsn and @nandafyi Agents are here to stay.
announcing cloudflare agent tracing! deploy, observe, and improve your agents one of the coolest things i've built and i got to build it with some awesome people!
Show more
Introducing Flue 2 — Build dynamic agents that evolve over time. Flue is a TypeScript framework for building the next generation of agents, powered by the @pidotdev agent harness. The Flue 1.0 Beta was released last month & has now been downloaded 700,000+ times. And from all of that feedback, we realized something we'd missed. Agents have a familiar problem: composability. How do you compose together different agent capabilities in a way that feels expressive AND maintainable, especially as you scale up complexity? Last week, I teased: “What if React for Agents?” and yes, as you will see, the inspiration here is obvious. But UI devs and agent devs have some things in common, including the same problem that the React team solved almost a decade ago with... Hooks! There are now things that you can do in Flue 2.0 with hooks that are just fundamentally difficult in other frameworks: A Flue agent can enforce a multi-step workflow, earn new tools once certain conditions are met, or trade up to a bigger model when the work gets too hard. Handling metadata and context no longer requires custom framework APIs and configuration. In Flue, you can pass data to a tool the same way you pass arguments to a function. I'm really excited for you to try Flue 2.0 out yourself. It's a big, bold take on what agents could be capable of in the future. Read more:
Show more
a fable + remotion production
base ui + shadcn/ui, but for opentui terminal interfaces is out
been testing this out all week… it’s sooo good! fred cooked 👀
is there really no "React for Agents" yet?
point → annotate → ship any opentui renderable, to any agent. clipboard or mcp.
it's never been easier to ship a tui $ bun create tui