Joined February 2026
11 Photos and videos
Pinned Tweet
Replying to @Adidotdev
i see the complete opposite. literally every problem we've spent past 2-3 decades solving have re-emerged, but in different shape. e.g. security, identity, permissions, scaling, privacy, virtualization, code distribution, orchestration, etc. it's the perfect time to build!
8
1,319
we hit some insane breakthrough yesterday. 🤯
microsandbox about to get a whole lot faster🏎️ more on it later😏
2
102
Jun 13
another reason why open source must win!
1
36
toks retweeted
finally got docker running in a microvm in a single command. our @microsandbox cli api is really coming nicely together. this example creates a microvm with 2gb memory limit, a mounted disk image to store docker containers and a script to start the docker daemon. once in the vm, you can run docker commands: docker run -it --rm ubuntu
1
5
6
333
the MCP specification needs to be baked-in with a search proposal (think rg, grep). the one issue everyone's trying to engineer around today is how to expose data to agents in a native way. data is siloed, and the REST interface is a significant bottleneck imo because most services don't expose native grep-like search for a user's resource. even if they did, there's no consistency, which results in token waste trying to figure it out. every external system should be seen as a file that the agent can grep over, can pipe from one system to the other. this makes agents be more resourceful with data across multiple sources.
42
one of the many important pieces of the microsandbox runtime is metrics collection. it's been design to be crazy fast (shared memory), and extensible from ground up. all sandboxes write their metrics to a uniquely assigned memory slot. as sandboxes get destroyed, slots are re-assigned, and the slot's generation is bumped so readers can distinguish metrics from old vs new sandbox. new metrics entry replace previous ones. even at 1000 sandboxes on a single node (if ambitious), it consume merely 512kb of memory. runtime sampling is fully configurable, with option to switch off. the SDK, CLI and metrics exporter reads these metrics. the exporter provides an interface to register exporters to custom backends, as well as sampling rate. you're in full control. no reads or writes goes to the sqlite db. which means none of this gets in the hot path of starting a sandbox. you should never have to fly blind, whether it's a single or fleet of sandboxes. this is just one of the many optimizations we've done to do give you lightweight sandboxes that are also fast and extensible. i'll be posting more of these internals every now and then. next on my list is how we handle version negotiations with agentd (our custom init), to guarantee our SDKs runtime are backward compatible. p.s: i did a brief into of agentd in a prior post few weeks ag. check microsandbox.dev/blog.
2
3
20
1,501
toks retweeted
🧵microsandbox 0.5.5 is out, and we're grinning. 🎉 you can now stream live per-sandbox metrics to any OTLP backend, offline import images from docker, amongst other things we're excited about. 👇
1
1
16
1,468
toks retweeted
we grouped the cli commands for easy nav
2
13
723
toks retweeted
reminder: if your user can run docker, your user is root. microsandbox has no daemon and runs rootless. nothing on your host is sitting there doing root favors. you get a hardware-isolated microVM, full stop.
Codex just found a “workaround” of not having sudo on my pc…
2
7
597
toks retweeted
⚡ Microsandbox just leveled up (v0.5.x) 🔐 Native SSH & SFTP, no sshd needed 📂 New file commands (copy, mkdir, rm) 🛡️ Hardened mounts env-backed secrets 💾 Configurable OCI upper sizes Faster networking. Tighter security. Same blazing-fast sandboxes. 🚀 docs.microsandbox.dev/change…
1
2
9
540
May 30
native SSH support now in microsandbox@0.5. 🍻 previously, you'd run sshd inside the sandbox and expose a port. well, no more. point your existing ssh/sftp clients straight at it. available in all SDKs and CLI today. 🪅
1
6
16
1,289
toks retweeted
I understand the concern of skills atrophying when using agents. But so far I am not seeing it. Instead I have learned all sorts of dark secrets of linux networking I somehow didn’t learn before agents building a networking product.
51
28
761
72,586
May 29
early usage of opus 4.8, and it tells me: "hey we've been at this for 12 hours. let me add the task to the plan, and call it a night. if i continue, i'll likely introduce bugs due to fatigue". lol, not sure what to think of this. 😂
1
1
3
236
May 29
weirdest part is that it began making reference to "night" several times in a session despite it being mid afternoon my time.
1
1
133
May 27
your sandboxed agent calls OpenAI. its transcript, secret placeholders included, ships to S3 for archival. a prompt injection tries to exfil keys, or at minimum fingerprint which credentials exist. a release pipeline tries to send $NPM_TOKEN somewhere weird. four scenarios, four different right answers. most sandbox providers stop at secret injection. that's 1 of 4. what about the other three? @microsandbox today gives you all 4. i dig into all the details in this article.
2
1
294