Decode any cryptic error message with Crade
Error code 0x80070005. Kernel panic. NSURLErrorDomain -1009. Stack trace ten lines deep. Crade reads it on your screen, tells you what it actually means, and whether it is a real problem or you can ignore it.
Cryptic error? Crade tells you what it means.
What does this mean? Is it dangerous?
Site's SSL certificate expired 3 days ago. Not a virus — the owner forgot to renew. • If you typed the URL yourself + recognize the site → safe to proceed (but don't enter passwords) • If you got here from an email link → close the tab. Could be phishing. Wait until they fix the cert before logging in.
Error messages are written for the system, not the user. The result is that 90% of error messages are either incomprehensible ("NSCocoaErrorDomain Code=4") or actively misleading ("Something went wrong"). The standard response is to Google the error code and hope someone with the same problem solved it five years ago. Crade reads the error on your screen and tells you what it actually means, plus whether to act on it or ignore it.
What you put on your screen
- A dialog box with an error and an OK button
- A red banner in software ("Sync failed", "Connection error")
- A stack trace in a developer console or log file
- A blue-screen-style crash report
- A failing CI build with a wall of red output
What you say to Crade
Or shorter: "What is this?", "Fix this for me", "Is this dangerous?". Crade reads the error visible on your screen.
Step-by-step: how to do this in Crade
Make sure the error is visible
If the error dialog is open, keep it open. If the error is in a log file, scroll so the relevant section is in view.
Click the Crade icon
Expand Crade from the ∞ icon. Crade floats above the error dialog so you can see both.
Ask in plain language
"What does this mean?", "Is this serious?", "How do I fix it?". You do not need to know the technical name of the error.
Read the diagnosis
Crade explains the cause in plain language, says whether it is a real problem or noise, and gives concrete next steps. "NSURLErrorDomain -1009 means no internet. Check your Wi-Fi." beats Googling the error code.
Try the fix
If Crade suggests a step (restart the app, change a setting, run a command), try it. If it works, you are done. If not, ask Crade what to try next.
Escalate if needed
If the error persists and Crade has run out of ideas, ask: "Should I report this as a bug?". Crade tells you whether this looks like a known issue or something worth filing with the developer.
What you get back
A plain-English translation of the error, a severity assessment (can-ignore, should-fix, critical), and a step-by-step fix where one exists. For errors that depend on context (your specific app version, OS, network setup), Crade asks for the missing detail before guessing.
Tips for better error decoding
- Make sure the full error is visible. If the error message is truncated, scroll or resize to show all of it before asking.
- Include the context window. The screen around the error often tells Crade what you were doing. That helps a lot.
- Mention what you tried already. "I restarted but it still happens" saves a round of obvious suggestions.
- For developer errors, copy the stack trace into a visible text editor first if it is not already on screen.
- If Crade says "this is safe to ignore", trust it for low-stakes situations but verify for high-stakes ones (banking, encryption, data loss).
Free vs Pro vs Premium
- Free ($0): reads errors, explains them, suggests fixes. Plenty for the occasional cryptic dialog.
- Pro ($7.99/mo or $49.99/yr): higher daily usage, Agent mode (Crade can run diagnostic commands on your machine to dig deeper). Right tier for developers and IT-adjacent roles.
- Premium ($19.99/mo or $149.99/yr): 10x more daily usage. Right tier for IT support, on-call engineers, anyone whose job is debugging.
Frequently asked questions
Can Crade actually fix the error?
Sometimes, on Pro Agent mode. If the fix is a shell command (restart a service, clear a cache, change a permission), Crade can run it for you after you confirm. For UI-level fixes (toggle a setting in System Preferences), Crade tells you where to click, you click yourself.
What if the error is a security alert?
Crade explains what the alert means and what the safe path is. If your bank app is showing a security warning, the safe answer is usually "do not proceed and call your bank". Crade will say so rather than try to talk you through it.
Does Crade replace Stack Overflow?
For common errors yes. For very specific stack-trace debugging in niche frameworks, Crade is comparable to a fast-typing teammate. It will not always be right, especially on bleeding-edge libraries. Verify before applying suggested fixes to production code.
What if I cannot reproduce the error and only see it once?
Take a screenshot of the error when it happens (Cmd+Shift+4 on Mac, Win+Shift+S on Windows), open the screenshot in Preview later, and ask Crade about it. Crade reads the saved screenshot the same way as a live error dialog.
What if Crade tells me to do something I am not comfortable with?
Push back: "Is there a safer way?". Crade will offer a more conservative fix. Never run a command you do not understand. Ask Crade to explain it first.
The whole loop in one sentence
Error on screen, one plain question, a plain answer plus a fix. No Googling the error code, no "works on my machine", no random forum posts from 2017.
Lost in a settings panel, a video editor, a CAD tool, a CRM you used twice last year? Instead of searching for a tutorial, ask Crade what is on screen. It reads the interface and tells you exactly which menu to open or button to press.
Five bars, full Wi-Fi icon, websites do not load. The most maddening tech problem. Crade reads what is on your screen and walks you through the usual culprits in the right order, so you fix it instead of restarting your router seven times.
Storage almost full and you have no idea why. Crade reads your storage breakdown on screen and names the easy wins. Which folders to clean, which apps eat the most, what is safe to delete and what is not.