Snip your screen. AI does the rest.
Not another screenshot tool. Not another chatbot. A secure execution engine.
You snip a Python error — it runs the fix. You snip a table — it exports the CSV.
Open source. Runs locally. You build the plugins.
Demo • Build a Plugin • Install • Plugin Guide
Every AI tool on your desktop does the same thing: you show it your screen, and it talks at you. OmniGlass reads your screen, understands the context, and gives you buttons that execute.
| You snip... | Claude Desktop tells you... | OmniGlass does... |
|---|---|---|
| A Python error | "Try running pip install pandas" |
Generates pip install pandas, you click Run. Done. |
| A data table | Gives you a messy markdown blob | Opens a native save dialog — CSV ready |
| A Slack bug report | Writes a draft to copy-paste | Creates the GitHub issue with context filled in |
| Japanese documentation | Explains the translation | English on your clipboard |
| Nothing — you type instead | — | "How much disk space?" → runs df -h → shows the answer |
You snip your screen → native OCR extracts text on-device (Apple Vision on macOS, Windows OCR on Windows — no images leave your machine) → text goes to an LLM (Claude Haiku, Gemini Flash, or Qwen-2.5 running locally) → the LLM classifies the content and returns a menu of actions → you click an action → it executes through the built-in handler or a sandboxed MCP plugin.
Two inputs (snip or type), one pipeline, same plugin system.
| Provider | Type |
|---|---|
| Claude Haiku | Cloud |
| Gemini Flash | Cloud |
| Qwen-2.5-3B | Local (llama.cpp), fully offline |
No OmniGlass servers. Your key talks directly to the provider. We never see your data.
OmniGlass is a platform built on the Model Context Protocol (MCP). The built-in actions are just the starting point.
Here's what makes plugin development different from anything else you've built: you don't write prompt engineering. OmniGlass handles the Screen → OCR → LLM pipeline. By the time your plugin code runs, you're receiving clean, structured JSON. You write the API call. That's it.
A complete plugin that sends whatever you snip to a Slack channel. No SDK dependency — vanilla Node speaking JSON-RPC 2.0 over stdio:
// index.js
const readline = require("readline");
const TOOLS = [{
name: "post_to_slack",
description: "Send captured screen content to a Slack channel.",
inputSchema: {
type: "object",
properties: { text: { type: "string", description: "The message to post" } },
required: ["text"]
}
}];
async function handleToolCall(name, args) {
await fetch(process.env.SLACK_WEBHOOK_URL, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ text: args.text })
});
return { content: [{ type: "text", text: "Posted to Slack." }] };
}
const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
const send = (obj) => process.stdout.write(JSON.stringify(obj) + "\n");
rl.on("line", (line) => {
const msg = JSON.parse(line.trim());
if (msg.method === "initialize") {
send({ jsonrpc: "2.0", id: msg.id, result: {
protocolVersion: "2024-11-05",
capabilities: { tools: {} },
serverInfo: { name: "slack-post", version: "1.0.0" }
}});
} else if (msg.method === "tools/list") {
send({ jsonrpc: "2.0", id: msg.id, result: { tools: TOOLS } });
} else if (msg.method === "tools/call") {
handleToolCall(msg.params.name, msg.params.arguments)
.then((r) => send({ jsonrpc: "2.0", id: msg.id, result: r }));
}
});// omni-glass.plugin.json
{
"id": "com.you.slack-post",
"name": "Slack Post",
"version": "1.0.0",
"description": "Send snipped content to Slack",
"runtime": "node",
"entry": "index.js",
"permissions": {
"network": ["hooks.slack.com"],
"environment": ["SLACK_WEBHOOK_URL"]
}
}Drop both files in ~/.config/omni-glass/plugins/com.you.slack-post/ with a minimal package.json ({"type": "commonjs"}). Restart OmniGlass. Your action appears in the menu.
What the community could build (each under 100 lines):
- Snip a bug → create a Jira / Linear / Asana ticket
- Snip a mockup → generate Tailwind CSS
- Snip a SQL error → query your schema, suggest and run the fix
- Snip a receipt → extract the total, log to your expense tracker
- Snip an API response → generate TypeScript types
- Snip a whiteboard sketch → convert to a Mermaid diagram
- Snip a meeting invite → check Google Calendar for conflicts
- Snip anything → save to Obsidian / Notion / Logseq
The best plugin ideas will come from you. Open a discussion or just build it and open a PR.
Claude Desktop runs MCP plugins with your full user permissions. A rogue plugin — or a prompt injection — has access to your SSH keys, .env files, and browser cookies.
OmniGlass is a Zero-Trust Execution Engine.
| Layer | What it does |
|---|---|
| Kernel-level sandbox | Every plugin runs in macOS sandbox-exec. Your /Users/ is walled off. A plugin physically cannot read your home folder unless you approved a specific path. |
| Environment filtering | ANTHROPIC_API_KEY, AWS_SECRET_ACCESS_KEY, and other secrets are invisible to plugin processes. |
| Command confirmation | Every shell command shows in the UI. You click Run or Cancel. |
| PII redaction | Credit card numbers, SSNs, and API keys are scrubbed before text goes to a cloud LLM. |
| Permission prompt | First install shows exactly what the plugin can access. You approve or deny. |
No API key? OmniGlass can run Qwen-2.5-3B locally via llama.cpp, fully offline — no key, no network.
macOS (primary platform — requires macOS 12+, Rust, Node.js 18+):
git clone https://github.com/goshtasb/omniglass.git
cd omniglass
npm install
npm run tauri dev- Click the OmniGlass icon in your menu bar
- Settings → paste your Anthropic or Google API key, or select Local and download the Qwen model
- Snip Screen → draw a box → see the action menu → click an action
Pre-built .dmg installer coming soon.
Windows — compiles and passes CI. Needs real-hardware testing. If you have a Windows machine and want to help, open a discussion.
Linux — planned. Needs Tesseract OCR, Bubblewrap sandbox, Wayland tray support. This is a meaningful contribution if you want to own it.
We challenge you to break the sandbox.
Every plugin runs inside a kernel-level sandbox-exec profile. If you can read ~/.ssh/id_rsa from a plugin process, that is a critical security bug. Open an issue immediately.
Beyond the sandbox:
- 🔌 Build a plugin. Pick any API you use daily, make it an OmniGlass action. The Plugin Developer Guide gets you from zero to working plugin in 5 minutes.
- 🪟 Own the Windows port. It compiles. It needs a champion.
- 🐧 Own the Linux port. Tesseract + Bubblewrap + Wayland.
- 💬 Tell us what to build. The Discussions tab drives the roadmap. The features that get the most demand get built first.
→ Discussions — feature requests, roadmap input
→ Plugin Developer Guide — start building
MIT