Dune vs ZeroID

“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.”

“Infrastructure the agentic ecosystem desperately needs and nobody has properly solved. The RFC 8693 token exchange is the right approach — maps cleanly onto service-to-service auth in microservices. Automatic scope attenuation is the critical safety property: no sub-agent can exceed what its orchestrator was allowed. Apache 2.0, Docker Compose setup, real SDK support.”

“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.”

“This is v0.1 infrastructure for a problem most teams aren't hitting at scale yet. The CLI is 'planned.' Human-in-the-loop approvals are 'planned.' The hosted version at auth.highflame.ai adds a third-party trust dependency for something that's supposed to be about trust. Worth watching, not worth building on in production.”

“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.”

“We're in the window where the identity layer for the agentic era is being defined. ZeroID's bet on existing OAuth/OIDC infrastructure rather than inventing a new protocol is smart — enterprise security teams won't reject it outright. The real-time revocation propagation is the feature that matters most when something goes wrong with an autonomous agent.”

“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.”

“Deep infrastructure — identity tokens, delegation chains, revocation lists. It's solving a real problem but it's not something a non-engineer can evaluate or use directly. If you're a content creator, this is plumbing that will hopefully get embedded into the platforms you use. Check back when it's a managed service with a dashboard you can navigate.”