Universal telemetry, previous-session recovery, and opt-in community reporting across the current NEXT surfaces, while keeping exploit behavior unchanged.
Diagnostics observe firmware, routing, cache, storage, resource failures, JavaScript failures, payload flow, and previous incomplete sessions. Community submission remains opt-in and shows the exact JSON before anything is sent.
Unexpected termination is reported only as suspected when the prior session lacks a normal completion marker. Diagnostics do not automatically label the cause as a kernel panic.
Summary
Loading summary...
Community Report Setup
Submission Target
Checking...
Loading report target details.
Diagnostic Log
Filter the persisted ring buffer without deleting entries. Records keep their session ID so previous-session recovery and current-session flow can be compared locally.
No diagnostic records.
Community Test Report
Reports are never sent automatically. Review the JSON below, confirm explicitly, and then choose submission. If no private endpoint is configured, the fallback opens a public GitHub issue draft.
Only non-sensitive fields are included by design: firmware, backend, payload metadata, stage flow, cache/storage status, tester-supplied notes, and optional User-Agent when you choose to include it.