Something breaks. An error message appears. A build fails. A setting is wrong. A permission is denied. Your first instinct is to open your browser, copy the error text, paste it into Google, scroll through Stack Overflow threads that are 7 years old, and try to figure out which answer might apply to your specific situation.
" + "Lumini skips all of that. Hold Ctrl+Option, read the error out loud (or just say 'what's wrong here'), and Lumini sees your screen — including the error message, the surrounding interface, and the context of what you were doing. It explains the problem in plain language and tells you what to do. If the fix involves clicking something or typing a command, Lumini can do it for you through Lumini.
Screen-aware error diagnosis
The key advantage Lumini has over Google or Stack Overflow is that it sees the error in context. When you search 'TypeError: Cannot read properties of undefined' on Google, you get hundreds of generic answers. But Lumini sees your actual code, your file structure, your variable names, and your console output. It can tell you that the specific object on line 47 of your index.ts file is returning undefined because the API call on line 32 hasn't resolved yet.
" + "This works for all kinds of errors: Xcode build errors, Python tracebacks, npm install failures, Docker container issues, Photoshop 'scratch disk full' warnings, Final Cut Pro render failures, Logic Pro audio driver problems, and any macOS permission or configuration issue. Lumini sends your screen capture to Claude, which has been trained on millions of error messages and knows how to diagnose them.
Lumini can execute the fix
Diagnosis is one thing — execution is another. If the fix involves clicking a button, opening System Settings, running a terminal command, or editing a configuration file, Lumini can do it. Say 'Lumini, open System Settings and go to the Network panel.' Or 'Lumini, run npm install in my project directory.' Or 'Lumini, read the config file and show me what's on line 47.'
" + "Lumini operates with an approval system. Actions that could change your system (like running shell commands or clicking in apps) require your confirmation first. You see a preview of what Lumini plans to do, and you approve or deny it. This keeps you in control while letting Lumini do the repetitive parts of debugging.
Web search without leaving your debug flow
Sometimes the error is rare enough that Claude doesn't know the exact fix from its training data. In that case, you say 'Lumini, search the web for this error.' Lumini searches the web through your Cloudflare Worker proxy and returns the top results with snippets, all while you stay in your debugging context. You don't open a browser, you don't lose your place, and you don't break flow.
" + "This is particularly useful for framework-specific errors, version-specific bugs, and recently introduced issues that Claude's training data might not cover.
Real examples
- **Xcode** — A build error shows 'No such module.' Hold Ctrl+Option and ask 'why can't it find this module?' Lumini sees your import statements and project structure.
- **VS Code** — An npm install fails with a cryptic error. Ask 'what does this error mean' — Lumini reads your terminal output and explains the dependency conflict.
- **Terminal** — A Docker container won't start. Ask 'why is this container failing' — Lumini sees your docker-compose file and error output.
- **Photoshop** — 'Scratch disk full' error. Ask 'how do I fix this' — Lumini tells you where to clear cache and what settings to change.
- **Final Cut Pro** — 'Render failed' error on export. Lumini sees your project settings and suggests resolution or codec changes.
- **Chrome DevTools** — A CORS error in the console. Lumini reads the exact error and explains what needs to change in your server config.