LockDown Browser + Grammarly Conflict on Mac (Quit Before Launch)

Last updated 2026-05-02 · LDBypass Editorial

Grammarly's desktop app installs a system-wide service that injects suggestions into every text input field on every macOS app. LDB's kiosk mode treats this as a potential cheat vector. Result: freezes during LDB launch (10-30 seconds while Grammarly's hook attempts to attach), or kiosk-mode-violation events logged in the Monitor recording. Quit Grammarly desktop before launching LDB.

The symptom

LDB launch hangs for 10-30 seconds longer than usual. Or LDB launches but logs "kiosk mode violation" the first time you focus an exam textbox. Or you don't see Grammarly's suggestions in the exam (they're blocked but the attempt at injection is logged).

Why it conflicts with LDB

Grammarly's desktop helper uses macOS Accessibility APIs to monitor text fields system-wide. When LDB enters kiosk mode, it intercepts these injection attempts as part of cheat prevention. The rejection is fast on modern macOS (Sequoia+), slow on older (Sonoma 14.3 and earlier).

The fix - pre-exam procedure

Quit Grammarly desktop. Status menu icon → Settings → Quit Grammarly.
Verify in Activity Monitor that no Grammarly processes remain (search "Grammarly").
If Grammarly relaunched on its own, also disable "Launch Grammarly when my computer starts" in Grammarly Settings.
Launch LDB.

Browser extensions (Safari Grammarly, Chrome Grammarly extension) are NOT running inside LDB anyway - they're browser-process specific. The desktop service is what matters.

Alternative configurations

If you frequently use Grammarly and want a less aggressive setup:

Use only the browser extension (no desktop service).
Set Grammarly desktop to "Auto-disable in specific apps" - add LDB to the disabled list.
Quit only when an LDB exam is imminent; reactivate after.

What NOT to do

Don't try to bypass the conflict mid-exam - LDB's blacklist scan happens before exam launch and re-runs at intervals.
Don't restart the conflicting app DURING the exam - LDB will detect the new process and may flag.
Don't leave the conflicting app paused/disabled long-term outside exam windows; that's overkill for non-LDB use.

Frequently asked questions

Will my essays be auto-corrected?

No - Grammarly is not running during the exam. Your typed text is exactly what you typed, no suggestions, no auto-corrections.

Why does Grammarly trigger a kiosk-mode violation?

Grammarly's service is the most common system-wide accessibility-API user on Mac. LDB's kiosk-mode detector sees something attempting to read its window content; logs as a generic violation. The actual content read by Grammarly is suggestions, not exam answers, but LDB can't differentiate.

Should I uninstall Grammarly to be safe?

No - quitting is enough. Uninstalling is overkill for a tool you presumably use regularly outside exams.