appcypher

your AI agent just read a webpage and emailed your AWS keys to someone in Moldova. congrats on shipping fast 🙂

What started off as a workflow test, just an idea, quickly had me locked into a flow state. 4 hours total from completely blank slate to finished video. I can’t believe we’re all so lucky to have this at our fingertips. 🔊 sound on 🔊 @runwayml

@iximiuz @hnanacc We can always improve our messaging

@iximiuz @hnanacc what part is confusing?

"A sandbox is an isolated Docker container that runs inside a microVM." Docker couldn't be more confusing in this message. I'm playing with the shiny new `sbx` tool, and what I see is a microVM with a fully-fledged Docker daemon inside that can run any number of containers. ``` sbx run shell ``` The above command is particularly fascinating. It starts a new sandbox (a microVM) and transparently mounts the current folder into it. Looks really handy for ad-hoc experimentation. And the best part - since yesterday, it also works on iximiuz Labs (via the new Cloud Hypervisor backend that supports nested virtualization). You can play with it at labs.iximiuz.com/playgrounds/do…

@hnanacc @iximiuz Awesome. And watch out for 0.4! Some fixes are coming that improve the filesystem perf! OCI image compat and many others.

@theappcypher @iximiuz thanks will test it with our electron app.

@heat_bender lol. what do u expect?

embedded refers to the SDK because we don't require some inital setup or daemon running in the background to run sandboxes. our microvms still run in their own processes. and importing microsandbox into your project is all you need to start spawning them. it makes the experience seamless for your end users.

@theappcypher @iximiuz what are the tradeoffs with microsandbox compared to docker? if it's embedded how does it provide host level isolation?

@seunlanlege “Exploit them” Didn’t age well x.com/seunlanlege/st…

@AndersonAndrue right at your back with @microsandbox

Haven’t seen anyone announce a new Firecracker-based MicroVM startup in a few days.. is everything alright??

⚡️microsandbox filesystem is now 20-62% faster than docker’s! ⚡️ this is from being 100x slower a day ago.

2/ after a week of benchmarking and revisiting the fs implementation, our new benchmarks outperform docker's in quite a number of cases we measured🎉

we rewrote @microsandbox btw

a government controls human labor. foundational ai labs control digital labor. digital labor is accelerating at an incredible pace and will surpass human labore. i just don't see how the relationship between the two sides will last.

at what point do foundational ai companies start realizing they don't have to bow to any country's government? not even the US. the recent scuffle between anthropic and DoD will only accelerate that outcome.

Microsandbox (YC F26) Boots a real VM in under 100ms, no daemon, no server, no root. libkrun microVMs with hardware-level isolation. SDK is three lines of code. Secrets never enter the guest. Apache 2.0. microsandbox.dev Founders: @theappcypher

you don't need sandboxes to give agents posix tools. you need them to make your agents don't do sth else. supply chain attack is real and your agent code could be compromised.

the AI landscape has and will continue changing. but i think one thing that could increase ones chances of winning would be flexibility and speed to adapt to change. one example is the sharp realisation that we can't inject secrets into sandboxes due to prompt injection as a means to exfiltrate keys. same applies to sudden realisation with file system, etc. big ships built without extensibility will be hard to sail the other direction; while the ones baked in with extensibility will adapt, and immediately thrive once they have that network effect. the latter is the stance we're taking @microsandbox. don't try to be smart by predicting the future. be wise in being well positioned. the best we can do is do the hard-work upfront for our ships to be extensible/adaptable. it's the reason most of the sudden realisations lately haven't taken i and @theappcypher by surprise. make every component of the sandbox plug-and-play native ... and i mean, everything! i'm glad we're almost out of the weeds on that initial ground work. better putting us in a position to adapt and steer the ship as the industry realise what works and doesn't. we do have a lot of work to do on the network effect, but we anticipate this will grow as we become known for steering sharply into the right direction and sailing quickly.

this is the core premise around how we rebuilt @microsandbox. expose the file system so devs can write plug-and-play filesystem that abstracts some services. map IAM policies to file permissions, etc. we’ve got the first leg of this landed in core. it should land in our SDK soon ;) it’s the same core principle of foreign data types in postgres.