Hey HN, We’ve reached peak "chat interface." Claude Desktop and OpenAI are amazing at coding, but they are terrible for repetitive, blue-collar, or legacy enterprise workflows. You cannot deploy Claude Desktop to a warehouse floor or an auto repair shop and expect workers to prompt-engineer their way through a proprietary GUI or a locked PDF every 5 minutes. They don't want a conversation; they want a button that does the job. So I built OmniGlass (Rust/Tauri). It is an open-source, local-first runtime that lets developers turn any MCP (Model Context Protocol) tool into a 1-click OS-level visual action. How developers use it: You write a standard MCP server (e.g., a 30-line Node script that queries an internal database). OmniGlass handles the visual pipeline: The Trigger: The user snips a region of their screen. The Vision: Native OS OCR (Apple Vision) extracts the text locally (no screen streaming). The "Brain": An LLM dynamically maps the raw OCR text to your MCP tool’s strict JSON input_schema. The Action: OmniGlass instantly renders a native button on the screen. The user clicks it. The tool executes. Zero prompting. The Real-World Use Case (Why this matters): I found a $1,000 bounty on ProblemHunt from an auto shop. Mechanics are wasting hours looking at informal WhatsApp messages ("left radiator plug, Chery Tiggo") and manually cross-referencing them against messy, unsearchable Chinese auto-part PDFs. A standard AI chat app fails here because of the friction. But with OmniGlass, a developer can build a "Find Auto Part" MCP plugin. You deploy it to the mechanic's Mac. The mechanic just snips the WhatsApp message, clicks the "Find Part" button that pops up, and the plugin queries the supplier API. The mechanic never talks to an AI. It just executes. The Security Sandbox (Why not just use Claude's MCP integration?): Claude Desktop runs MCP tools with raw user permissions. A hallucination or prompt injection can read your ~/.ssh keys. Since OmniGlass is meant to be deployed in businesses, it runs entirely Zero-Trust. Every MCP plugin is locked inside a macOS sandbox-exec kernel profile. The /Users/ directory is default-deny. My Asks for HN: This is infrastructure for developers to build on, and I need help pushing it forward: The Auto Parts Bounty: I want to build the Chinese auto parts plugin to prove the platform. If anyone here has experience scraping or querying B2B auto supplier databases, let's collaborate and claim this bounty. Break my sandbox: If you can write an MCP plugin that escapes my sandbox-exec profile and reads a protected file, please open a GitHub issue immediately. I want this bulletproofed. OS Ports: The Rust core is solid, but if any low-level devs know Windows AppContainer or Linux Bubblewrap, I’d love help porting the security moat. Repo: https://github.com/goshtasb/omniglass Docs/Plugin Guide: https://github.com/goshtasb/omniglass/blob/main/docs/plugin-... What legacy enterprise workflows would you build a visual tool for? |