A log viewer, an alarm, and a fix button — in one plugin.

When a fatal takes a page down, FatalGuard captures it — error type, message, file:line, and the URL that triggered it — instead of leaving a blank white screen. A self-installing must-use drop-in does the watching, without editing wp-config.php and without depending on wp-admin being up.

Read your debug.log and the PHP error log right in wp-admin — no FTP, no SSH. Fatals, PHP warnings, and deprecations (plus JavaScript console errors) are grouped with a count so one noisy warning can't bury a fatal. Search by message, file, or function, and watch new entries land live. Secrets in log lines are auto-redacted before display.

When a plugin crashes the site, the alert carries a secure, single-purpose link: deactivate exactly that plugin and restore the site — from your phone, in one tap. No FTP, no folder renaming. Signed, expiring, and never capped: recovery is unlimited on every plan.

FatalGuard turns on file logging safely, without you touching wp-config.php — so you don't have to hand-set debug constants or risk leaving error output on the front end. There's also a “Show PHP errors on the front end” toggle for local development.

Connect Claude, Cursor, VS Code, or any MCP client and ask what's crashing your site in plain English — answered from your real error history. Read-only, secured by a scoped, revocable API key (never an admin session). Ask “what's the most recurring error this week?” and get the error, file:line, count, and when it started.

The free viewer shows the current tail; log files rotate and truncate. Pro keeps every fatal in a database — grouped, with counts and first/last-seen — so you can answer “when did this start?” and pin an error to the change that caused it. Set a retention window; a daily job prunes the rest. (This history is also what AI access reads.)