OpenCode is about to get more powerful with remote sandboxes I showed a brief demo before, but here's a much more in-depth demo. it's not hard to add basic support for a remote env, but handling all the edge cases like when a remote env gets deleted is difficult. especially if care about good UX You never want to lose session data. so the choices are: run the session in your env, but run all tool calls remotely. that's too complex and painful. The other way is to just let the full session run remotely, but sync back all the session data in your env. We chose this path: we built a syncing system which logs all events in a way that we can always recreate your entire session. That means the remote env could get destroyed, but we can easily restore it. it also opens up other interesting ideas which we'll be exploring

My kitchen HomePod has developed a life of its own, playing random music throughout the day and night and responding to Siri requests that nobody is making…

I'm thrilled to announce that Koyeb has entered into a definitive agreement to join @MistralAI to build the future of AI infrastructure. Koyeb will bring its platform, technology, and team to accelerate Mistral Compute offering. 🎉 Learn more 🧵👇

Bun v1.2.19 - Fixes 163 issues, addressing 1,043 👍 - `bun install --linker=isolated` : pnpm-style isolated symlink installs - `bun update --interactive` - `bun why <pkg>` - VSCode test explorer integration - Bun.sql gets faster - `--console-depth` bun.sh/blog/bun-v1.2.19