A Bug-Fix Release, Built From Real Reports
Ghostly AI v3.3.5 doesn't add flashy new features — it fixes exactly what users told us was broken. Every issue below came from an actual bug report, and every one is now fixed and live.
🐛 "Groq API error: model does not exist" / "My API keys aren't working"
Groq quietly removed meta-llama/llama-4-scout-17b-16e-instruct from its entire model catalog — production and preview. That model was also the default Groq option, so any new user who picked Groq hit this error immediately. Worse, the "Test Key" button used a different, still-valid model to verify — so your key would show "Valid ✓" while real usage failed right after, making it look like a broken key when the model itself was the problem.
Fixed: Removed the dead model everywhere, switched the default to llama-3.3-70b-versatile, and added the current gpt-oss models Groq now offers.
🐛 Overlay briefly visible in Google Meet screen share
Reported exactly as: disable audio, re-enable it mid-interview, and the Ghostly window flashes visible in the screen share for 2-3 seconds. Root cause: every audio restart re-negotiated system-audio capture, which briefly dropped the window's screen-capture-exclusion flag to enumerate screens, then restored it ~800ms later — a window of real exposure if you were already screen-sharing.
Fixed: The screen source is now cached after the first successful capture, so re-enabling audio never touches stealth mode again.
🐛 "Microphone is not working, I tried so many things"
The microphone test in Audio Setup only ever showed a bare "No Signal ✗" — no explanation.
Fixed: It now detects the actual cause and tells you exactly what to do — Windows blocking mic access at the OS privacy level (the most common cause, with the exact Settings path to fix it), no microphone detected, or the mic already in use by another app like Zoom or Teams.
🐛 Keyboard shortcuts that didn't actually work
A deep audit found the documented shortcut table didn't match the real app at all:
- Ctrl+Shift+S and Ctrl+Shift+H were documented everywhere but registered nowhere — pressing them did nothing.
- Ctrl+N, Ctrl+0, Ctrl+8, and Ctrl+2 only worked while the invisible overlay window itself had keyboard focus — effectively never during a real interview, where focus stays on Zoom or your IDE.
- Arrow-key question navigation was registered twice, so every press skipped two pages instead of one.
- Ctrl+E was wired up in two conflicting places at once, occasionally double-capturing.
Fixed: Every shortcut in the table below is now a genuine system-wide hotkey — it works no matter which window has focus.
| Shortcut | Action |
|---|---|
| Ctrl + E or Ctrl + Shift + S | Capture screen + solve |
| Ctrl + N | Next Question |
| Ctrl + 0 | Manual Send |
| Ctrl + 8 | Previous Question |
| Ctrl + 2 | Next Question Page |
| Ctrl + B or Ctrl + Shift + H | Toggle Stealth Mode |
| Ctrl + G | Start Over |
👉 See the full keyboard shortcuts guide
🐛 Screen Analysis answer appears, then vanishes
The most confusing one: click Screen, get a full answer, and watch it disappear a moment later with nothing to show for it. Three separate bugs stacked on top of each other:
- Clicking the Screen tab was quietly triggering the capture twice per click, racing two overlapping AI answers against each other.
- The code that "cleared the buffer" after a completed answer was accidentally wiping the entire saved history, not just the screen — deleting the answer it had just saved.
- The Screen tab was hard-locked to a single page instead of building a real history.
Fixed: Screen Analysis now behaves exactly like AI Answer mode — every screenshot you analyze becomes its own Q1, Q2, Q3 page you can flip back through, and nothing disappears.
📥 Update Now
All of the above is live in v3.3.5.
