Help & recovery
Find the next step.
Find the next step.
Keep your content private.
Choose the problem you are facing, check only the browser signals that matter, and escalate with a privacy-safe support brief when self-service is not enough.
The diagnostics report never includes prompts, transcript text, imported files, or personal identifiers.
SUPPORT BOUNDARYLOCAL PREVIEW
LIVE AINOT ACTIVESUPPORT CHANNELEMAIL
SELF-SERVICE FIRSTNO PROMPT CONTENT IN DIAGNOSTICSEMAIL ESCALATION WHEN NEEDED
Issue finderStart from the friction,
Start from the friction,
not from a generic form.
Each route begins with non-destructive checks and ends with a focused escalation path. Switching routes does not inspect or modify workspace content.
The workspace opens, but the result or control flow is unclear.
- Confirm that the topbar says Local preview.
- Use a mode-specific starter to separate interface behaviour from prompt wording.
- Open Runtime and confirm the transport remains local-preview.
- Refresh only after exporting a portable recovery file when the work matters.
A draft, transcript, duplicate tab, or imported recovery file is not where expected.
- Stay in the same tab while checking automatic recovery.
- If another visible tab owns the same lineage, choose Use this tab or Open as separate copy before editing.
- Use Session → Download recovery file before clearing or switching devices.
- Import only an unchanged
.boardesa.jsonfile generated by Boardesa. - Remember that no account or cloud history exists in the current preview.
A page is stale, unavailable, or not controlled by the offline shell.
- Check whether the browser reports an internet connection.
- Open System Status and inspect the Offline shell, Atomic release, and Update transition rows.
- Use Check for update; activate a waiting shell only after Boardesa reports that its cache gate passed.
- If the transition says Recovery needed, retry once from System Status. Automatic reload has already stopped.
- Clear offline copies only when a stale cache persists; this removes cached pages, not server data.
You want to understand, change, or remove local product data.
- Read the current information map before sharing any support example.
- Change analytics consent from Cookie settings.
- Use device controls to clear offline copies or same-tab recovery.
- For a privacy request, identify the relevant email interaction without adding unnecessary identity data.
A keyboard, screen reader, zoom, contrast, motion, or focus path is blocking the task.
- Record the exact page and action that could not be completed.
- Include browser, device, zoom level, and assistive technology only when relevant.
- Describe the expected focus or reading order.
- Do not include private study content unless it is essential and safely redacted.
A possible vulnerability or unexpected trust boundary needs review.
- Confirm the behaviour affects the current public build and is not a normal local-preview limitation.
- Stop if testing could expose another person’s information, alter data, disrupt availability, or create avoidable cost.
- Record the URL, build ID, minimal steps, observed result, expected result, and a redacted example.
- Do not include passwords, API keys, payment data, private student records, or a full portable session.
- Read the Security page and security.txt.
LOCAL PREVIEW ERROR CODES
- LOCAL_STOPPED
- The user stopped the deterministic sample.
- LOCAL_TIMEOUT
- The browser did not finish within the local time budget.
- LOCAL_INTEGRITY
- Request and response binding did not match.
- LOCAL_UNAVAILABLE
- The browser could not complete the local sample.
Workspace recovery route selected.
Privacy-safe diagnosticsShare capability signals.
Share capability signals.
Never the learning content.
The report is generated in this browser and is useful for technical support. It excludes prompt text, transcript content, session file contents, email addresses, names, and device identifiers.
Checks will run when the page loads.
ConnectionChecking browser signal…CHECKING
Same-tab recoveryChecking session storage…CHECKING
Privacy preference storageChecking local storage…CHECKING
Offline shellChecking service worker state…CHECKING
Secure contextChecking browser context…CHECKING
Workspace transportFixed by this production build.LOCAL ONLY
BUILD
Loading…Recovery playbooks
Use the least destructive action first.
These steps are ordered to protect local work. A reset should not be the first response to a recoverable state.
Protect the session
Stop an active sample, then download a portable recovery file. A normal refresh may use same-tab recovery, but a file is the safer cross-device copy. If recovery reports quota, size, or browser blocking, download the private file before leaving or turn recovery off for the current tab.
Session guide ↗Identify the storage
Offline caches, analytics consent, and workspace recovery are separate. Clear only the layer causing the problem.
Device controls ↗Reduce the example
Reproduce the issue with a non-sensitive prompt when possible. Share the safe diagnostics report instead of a full session transcript.
Name the expected result
Include the page, action, environment, what happened, and what useful next step you expect. Remove credentials and private student records.
Prepare support email ↗Support boundaries
Some routes do not exist yet.
There are no accounts, cloud histories, paid subscriptions, credit purchases, model-provider requests, or file uploads in the current preview.
- AVAILABLE
Product feedback, site problems, accessibility reports, privacy requests, responsible security reports, and education workflow questions.
- NOT AVAILABLE
Charge disputes, account recovery, cloud transcript recovery, model-provider incident review, or upload restoration.
- NOT AN EMERGENCY CHANNEL
Boardesa email is not a crisis, safeguarding, legal, medical, or emergency service.
Help FAQ
Know what the support tools can see.
Does the diagnostics report include my prompt or transcript?+
No. It contains only capability and product-state signals such as build ID, connection, storage availability, service-worker state, consent state, and local-only transport.
Why was a recovery file blocked?+
Boardesa blocks files above 256 KB, deeply nested or oversized JSON, duplicate or dangerous object keys, unsupported schemas, invalid dates, failed SHA-256 integrity, and session fields outside published limits. Validation remains local and does not upload the file.
Should I clear all browser data when something looks stale?+
No. First reconnect, refresh status, and identify whether the issue is a cached page, privacy preference, or same-tab recovery record. Clear only the relevant layer.
What should a useful technical report include?+
Include the affected page, exact action, expected result, actual result, browser and device category, safe diagnostics report, and a redacted reproduction. Never include passwords, payment data, API keys, or private student records.
Still blocked?Prepare a focused support brief.