Dylan

@zeeg @daniel_levine @rauchg Yes that's true, the root user needs to be in a Workflow DevKit-enabled environment to get the workflow behavior

@dylanjha @daniel_levine @rauchg It’s that the root user app seems to have to transpile the workflow definitions which means it has to trace them. Are they not importing them in the end user app? In my case they would need to have been invisible.

how tf do i successfully package Vercel Workflows up in a third party package? im pretty sure these are just compile time transforms but is there more magic than that?

@zeeg @daniel_levine @rauchg hi y'all, I worked on this > they're still overloading the end-user app with workflow definitions What do you mean by this? Is it the fact that the functions exported by the SDK have the 'use workflow' annotations? (The end-user doesn't have to add them or know about them)

@daniel_levine @rauchg already rewrote it to use different tech. trying out queues since its ~same thing (yall should rename this btw, pubsub isnt a queue!) the mux example isnt what i wanted - they're still overloading the end-user app with workflow definitions afaict and i wanted it more implicit

OpenClaw feels like LangChain. Really powerful and makes WOW demos but ends up being the wrong level of abstraction because eventually you realize you actually want to control the prompts, the flow of data between each step and the context that is being sent to the LLM

@andrew_barba great idea

Got to demo specli to the vercel team today: npx specli compile ./openapi.json Create single file executables for any OpenAPI spec and tell an agent to use it. No need for the API to have its own MCP server and it's much more token efficient. github.com/AndrewBarba/sp…

@pranaygp Thanks for your help on this! 🙌

Great blog post from @dylanjha on why “𝚞𝚜𝚎 𝚠𝚘𝚛𝚔𝚏𝚕𝚘𝚠” was exactly what they needed Essentially: instead of distributing a pile of individual steps and asking you to wire everything together, they can now just publish a package with the directive baked in mux.com/blog/launching…

This is really cool: @MuxHQ is distributing backend logic via npm such thay 1️⃣ Call the functions directly → they run in a single process 2️⃣ Use @WorkflowDevKit + start → the same code becomes durable, observable, resumable, and error-resistant 🤯

See Workflow DevKit here: useworkflow.dev/docs/getting-s… And a longer blog post I wrote that gets into how we made our workflows durable. Thank you @TooTallNate and @vercel folks for helping us figure out the details to make this possible mux.com/blog/launching…

The key thing here is that the functions are isomorphic. You can call them in a normal node environment, and everything works as you expect. OR, if you're using Workflow DevKit, then you can call them with `start` and get all the features of Workflow DevKit

We released the `mux/ai` package -- and shipped it with durable `"use workflow"` functions When I first saw "use workflow" from @vercel I thought. Hmm, that looks weird. I don't know if I like that

@monsieurBoutte @pranaygp @vercel Banger!! @wesbos cameo speaking Spanish

We just publicly released @mux/ai 🎉 An AI SDK for video, with native Vercel Workflows support built in. Plus a demo app showing what’s possible when paired with the Vercel Workflow DevKit. Shout out to @pranaygp and friends at @vercel for their support

@nateliason Same... haven't tried but I keep thinking that iMessage would be tough. A lot of my group chats are still on there

Omarchy FOMO is building. Any apps you miss using it?

@kasvith @karlclement @mikehostetler @MuxHQ Thank you! Send me a DM I'll throw some credits your way

@dylanjha @karlclement @mikehostetler @MuxHQ i was listening to your podcast about mux infra nice selection of techs though, we use mux for one of our projects :) its really nice to work with

Who’s using Elixir in production? What’s the project? What feature made you take this route? You’ve inspired me @mikehostetler

@kasvith @karlclement @mikehostetler @MuxHQ Just API

@dylanjha @karlclement @mikehostetler @MuxHQ is mux using elixir for video processing pipelines too? or just api

@karlclement @mikehostetler @MuxHQ I wasn't there for that decision, probably @matt_mcclure could best answer!

@dylanjha @mikehostetler @MuxHQ That’s incredible. Mux needs reliability and speed. That’s great to hear. How did you know back in 2015?

@davekiss @LaraconUS "You can just do things" - Mark Twain -- Dave Kiss

this time last year, I had never even touched Laravel next week, I'll be speaking at @LaraconUS, the flagship Laravel conference I guess the saying is true: you can just do things

@Stephen_Dolan How is that better/different than using Claude Code in the github action integration?

If you haven’t already set up a mini PC (I like Beelink) with Claude Code to keep research projects rolling while you’re away from your desk, you’re losing out on *so* much of what these agentic workflows can offer. I use Termius and Wispr, which have been working super well!