Dune vs smolVM

“The primitive here is dead simple and correct: an HID device whose key mappings are driven by a macOS accessibility API hook watching the frontmost application — the AI layer handles the mapping logic so you don't write profiles by hand. That's the right DX bet. The moment of truth is day two, not day one: does the context inference hold up when you have twelve apps open and you're alt-tabbing between your editor and a Slack thread? If the answer is yes, this is the macro pad I'd actually leave plugged in. The specific decision that earns a ship from me is that they rejected the 'define every profile yourself' pattern that killed every Stream Deck workflow I've ever set up.”

“Sub-200ms fork time is the headline number, and it holds up in testing. The snapshot/restore support is what makes this special — being able to checkpoint an agent mid-task and retry from that point without re-running expensive setup steps saves real money on long agentic workflows.”

“Direct competitor is the Stream Deck Mini plus a $10/yr Keyboard Maestro license, which already does context-aware macro switching with zero AI ambiguity. The specific scenario where Dune breaks is the one that happens constantly: two apps open side-by-side, ambiguous context, and three keys that do the wrong thing because the model guessed wrong — that's worse than a dumb macro pad, not better. What kills this in 12 months is Apple shipping Focus-mode-aware Shortcuts automation natively in macOS 16, at which point the software layer this hardware depends on is commoditized. To earn a ship: show me six months of real-world context accuracy data, not a Product Hunt leaderboard.”

“Self-hosted sandboxing is a sysadmin headache. The isolation model relies on Linux namespaces, which have a long history of escape vulnerabilities — running untrusted agent-generated code here needs careful hardening. Early project, limited docs, and no SOC 2. Not enterprise-ready.”

“The thesis Dune is betting on: within three years, AI context awareness will be accurate enough that zero-configuration physical controls outperform manually-configured ones, and users will pay a hardware premium for that. That's a falsifiable claim riding a specific trend line — on-device app-state inference getting cheap enough to run as a background daemon — and Project Mirage is early, not late, to it. The second-order effect nobody is talking about: if this works, it inverts the macro pad market from a power-user niche into a normie peripheral, because the configuration tax that kept civilians away disappears. The future state where this is infrastructure is a desk where every physical control knows what you're doing without being told.”

“Compute sandboxing is becoming AI's next infrastructure layer — the thing every agentic system needs but nobody wants to build twice. Open-source here is the right call; just as databases and caches became infrastructure commodities, execution sandboxes will too.”

“The job-to-be-done is singular and clear: stop context-switching your hands when your screen context already switched. The meetings use case is the product's sharpest edge — calendar sync plus one-click join plus mic/camera toggles is a complete workflow replacement, not a feature — and that alone justifies the purchase for anyone on four-plus calls a day. The product has a real opinion: it decides your key assignments, you don't. That's brave and almost certainly right. The gap that would turn this ship into a skip is if the broader context-awareness layer — editor vs. browser vs. design tool — turns out to be shallow window-title matching dressed up as AI; ship the meetings story hard and make everything else a bonus.”

“For automated screenshot, design review, and browser-based creative workflows, having isolated browser sandboxes that don't bleed state between runs is genuinely useful. A Figma scraper running in smolVM is cleaner than anything I've cobbled together with Docker.”