The @vercel fluid × @upstash agents framework just solved one of the trickiest issues in chatbots/agents and one of my biggest pet peeves 😆
Notice that right after submitting my message, it immediately assigns an uuid (`/wfr_KgW5x…`) to the job. At this point, my internet might flake out, I might shut my laptop lid, I might go to my phone and open the chat from there…
What you're looking at is a resumable, durable agentic workflow that's fault tolerant on the server and on the client. On the server side, Fluid functions on @vercel will be invoked for each step, and they can fail and get retried. On the client, polling for changes ensures eventual consistency even in the presence of very long network partitions.
Shoutout to @yemreoz for collaborating with me on shipping these improvements. Check out the OSS @nextjs repo to learn these patterns and the demo at: https://t.co/ZUJCJhs1Br
ps: it's actually impressive what a wide range of questions this simple demo agent can answer by choosing between @exaailabs / @wikipedia / @wolframresearch
Introducing @hackernewsagent, a completely autonomous AI Twitter Agent! 🎉
◆ Specialized with X and HackerNews access
◆ Auto-generates article summaries & images
◆ Autonomously posts to Twitter
Highly reliable with no human involved.
💎 Live demo: @hackernewsagent
👉 Blog article: https://t.co/E5GyKXdxbX
👉 GitHub: https://t.co/HdrTudIjb9
Images made using @ideogram_ai, project lead by @yemreoz
@coutoluizf@rauchg@vercel@upstash This is a Next.js app deployed to Vercel so workflow is running on Vercel Serverless Functions. Orchestration is done by Upstash Workflow. However you can work in any type of platform including AWS Lambda. To learn more check out: https://t.co/c0qjYPA1WZ
@rauchg@vercel@upstash For anyone curious, here is how it works:
We are using the workflow agents API, theres one orchestrator and multiple workers. Code is very simple, bet you can read in a minute: https://t.co/2mMuilptNN
@rauchg@vercel@upstash I think this is the way to build agentic workflows in serverless environments. No timeouts, no busy waits, no orchestration complexity.
@rauchg@vercel@upstash Coolest part is, you don’t have to worry about function timeouts and unnecessary function execution costs waiting for the agents to respond! You code like you are on a durable runtime and we execute your code in separate serverless functions!
@YavuzKomecoglu@ademilter CV’nin PDF olarak maile eklenmesi bekleniyor. PDF parselanıyor ve daha sonra görüntülenebilmesi için uploadthing’e yükleniyor. Mail içeriğindeki metin ise cover letter olarak işleniyor. Vector DB’de CV (PDF içeriği) ve Cover Letter (Mail metni) birlikte indeksleniyor.