Screen Analysis Actually Sees the Screen Now
The most common report since v3.4.0: pick Groq or NVIDIA as your provider, hit Screen Analysis on a coding problem, and get back "I'm not able to view the screenshot directly. Is it code (and if so, which language)?" — a real, successfully-streamed answer that just wasn't an answer. Neither provider has a vision-capable model, and neither fails loudly enough for the app to notice and retry on its own.
Fixed: if your chosen provider can't see images and you've configured any provider that can (Gemini, OpenAI, Anthropic, OpenRouter, Grok), Screen Analysis now automatically borrows that one for this single screenshot — your regular AI Answer questions still go to your actual chosen provider, completely unaffected. You won't see "I can't view the screenshot" again as long as you've added at least one vision-capable key.
🐛 A real stealth-breaking bug: a failed screenshot could pop the overlay back up
If you'd deliberately hidden the overlay with Ctrl+B and a screenshot capture then failed for any reason, the app used to force the window back to fully visible and focused — right in front of whatever you were sharing at that exact moment. The bug: the recovery code re-checked the window's live opacity instead of remembering whether this specific capture was the one that hid it.
Fixed: the overlay now only comes back if the capture that just failed is the one that hid it in the first place.
🐛 Screenshot failures were completely silent
If a capture failed for any other reason, nothing told you — Ctrl+E just looked like it did nothing, with the real error only ever printed to a terminal window no packaged app user ever sees.
Fixed: a failed capture now shows a clear on-screen message explaining what happened.
✨ Ghostly now tells you when a shortcut is already taken
Windows silently refuses to register a global hotkey that another running app already owns — no error, no dialog, the key combo just never fires. Ctrl+E in particular collides with plenty of browsers, Discord, and IDEs.
Fixed: a dismissible banner now tells you exactly which shortcuts couldn't register, so you know to remap them in Settings → Keyboard Shortcuts instead of assuming the app is broken.
Removed: the "Code Language" / "Interview Type" setting
A good number of people using Ghostly aren't doing coding interviews at all — HR rounds, behavioral rounds, non-technical roles. The old Code Language / Interview Type dropdown assumed every interview was a DSA round and confused everyone who wasn't. It's gone; the app no longer asks.
Safer by default: less time with stealth protection off
Preparing Screen Analysis needs a one-time list of your screen sources from Windows, and getting that list requires briefly turning off Ghostly's anti-capture protection — a short but genuine window where the app could theoretically show up in a recording. This used to be able to repeat every time you toggled your microphone; now it only ever happens once per app session.
📥 Update Now
All of the above is live in v3.4.2.
