No matter how much they pretend to be, sandboxes are not serverless. Most sandbox providers have a fatal flaw: designing around compute. A storage-first model will be a requirement to meet the demands of agents and truly achieve "serverless intelligence." https://t.co/TzM6oQFiKi
Introducing Gemini API CLI (gemini-api), now available in preview!
Our CLI gives your agent power to generate images, videos, text-to-speech, or music, analyze media, transcribe audio, or manage agents.
No more guessing model strings, throwaway scripts or endless curl.
🧵 👇
SQLite is the most used database in the world, and its biggest weakness has always been the same: it runs on one machine, and if that machine dies, your data is gone. The usual fix is Litestream, but that's a Go binary you have to babysit.
So we (@platformatic) rewrote it in TypeScript.
Been playing with Vercel Drive this week and I keep wondering... did Vercel just ship Durable Objects?
Hear me out -
Create a named drive, attach a sandbox, and you’re guaranteed only one active instance is ever touching that state. Write a program around that and you start tapping into the exact programming model that makes Durable Objects so good.
It's a fun inversion of roles. You stop thinking of a drive as something you attach to a sandbox. Make the drive the main character, and attach a sandbox to bring its state to life.
I tried replicating an agent substrate demo I had built before using Vercel Drive, and really like how it feels.
e.g. take Pi Durable. Pi checkpoints each step to a SQLite file on the drive. When the sandbox stops, even mid-turn, state in the drive is durably stashed away, and you can later attach a new sandbox to pick up the conversation right where it left off.
Reminds me of when I first learned about Durable Objects and how it warped my mind a bit. Can't wait to play around with this more.
@Jacobmalherbe21 Yep cloudflare durable object is the state of the art. On thing I like about agent substrate/durable sandbox here is that it is full linux box and can run most things you want! Not as lightweight as DO but that's a tradeoff that make sense sometimes!
@exectristan One interesting use case I found was that you can mount a read-only drive on a different sandbox and "observe" the state of an working actor. Kinda like a read-only SSH? Was a fun capability to play with!
@RudraAgrawal783 I think I tested this! Vercel will return a 4xx with a clear message saying that drive is already mounted, so I have a small retry code that handles that situation.
Been playing with Vercel Drive this week and I keep wondering... did Vercel just ship Durable Objects?
Hear me out -
Create a named drive, attach a sandbox, and you’re guaranteed only one active instance is ever touching that state. Write a program around that and you start tapping into the exact programming model that makes Durable Objects so good.
It's a fun inversion of roles. You stop thinking of a drive as something you attach to a sandbox. Make the drive the main character, and attach a sandbox to bring its state to life.
I tried replicating an agent substrate demo I had built before using Vercel Drive, and really like how it feels.
e.g. take Pi Durable. Pi checkpoints each step to a SQLite file on the drive. When the sandbox stops, even mid-turn, state in the drive is durably stashed away, and you can later attach a new sandbox to pick up the conversation right where it left off.
Reminds me of when I first learned about Durable Objects and how it warped my mind a bit. Can't wait to play around with this more.
We open sourced a *really fast* HTML artifact builder. It's powered by libfx, making the agent durable.
Building the low-level plumbing for v0 to survive server crashes, flaky LLMs, function limits was a huge pain.
Now it's easy, free, and OSS: https://t.co/aUP1vKeIsP.
PS: I built this floating container in a few minutes… it's delightful, and it's just HTML!
@napi@platformatic If your app is RAM-bound and tight container limits, serverless cold starts, and high memory bills are hitting you, this is the easiest 50% memory win you'll ever test. Two minutes with Docker.
Try it: https://t.co/bAowKUBbkt
Great release from fx.
Between this and Pi Durable few weeks ago, feels like we are getting a glimpse of what agent SDKs and infra are converging towards.
Running fx on Agent Substrate was super smooth. Event streaming in fx in particular was really cool. Excited to see what's coming next.
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
https://t.co/uYJQ5g790g
@MaazChowdhry@rivet_dev This is amazing. Selfishly want to encourage you to blog about it - feels like a lot of folks are trying to figure something like this out themselves! Thanks for sharing your learnings!