Harness durability in fx.sh . The same 𝚌𝚛𝚎𝚊𝚝𝚎𝙵𝚡𝙰𝚐𝚎𝚗𝚝() is now *durable* on your laptop or in the cloud, via files, Postgres, or Vercel Workflows. Node.js or Bun. Agents need long-running compute. But they also need to tolerate restarts, redeploys, timeouts, crashes… Concretely, if a user sends a prompt and then throws their phone into a black hole, we ensure that turn runs to completion. If the process crashes mid-tool-call, it resumes from there. To this end, 𝚕𝚒𝚋𝚏𝚡 introduces a simple durability adapter API. On Vercel, it leverages all the infra we built for durable workflows and queues, giving you reliability with 1LOC. This is a critical aspect of production-grade agents (and something all @eve agents also get out of the box). Next, we'll show you how we bring the same durability to Pi, OpenCode, and even your own custom harnesses. Pranit @fazxes fx v0.0.14 libfx is now durable out of the box. Same API on local, Vercel and DIY. - Sessions survive crashes, redeploys & timeouts - Power cloud agents with ChatGPT & Grok subscriptions - Custom providers & local model support in libfx - Run multiple libfx agents in one app - More control over each libfx session - TypeScript types for libfx's public APIs - Ported to Zig 0.17 - Multiple bug fixes & security improvements fx.sh/changelog#v0.0… 🔗 View on Twitter 🔗 View Quoted Tweet
媒体保存失败:[Errno 104] Connection reset by peer
▶ 打开视频地址