Boardesa AI is designed around visible learning steps. A useful session starts by choosing the right mode, naming the outcome, adding only the context that changes the work, and reviewing the sample before relying on it.
Supported browsers can install the current Boardesa shell for a focused standalone window and faster access to cached routes. Installation does not activate live AI, accounts, uploads, or billing.
When a new shell is available, Boardesa validates its cached release, waits for browser-controller handoff, and reloads once. A stalled transition stops instead of repeating reloads.
Checking whether this browser exposes a direct install action.
Open the browser menu and choose Install app, Add to Home Screen, or the equivalent option. The wording depends on the browser and device.
You do not need a perfectly engineered prompt. You need enough clarity for the workspace to understand the task, the desired outcome, and the boundaries of useful support.
Use Study when the goal is understanding, Math when the method matters, Write when authorship must remain visible, Quiz when evidence is needed, and Plan when time and priorities must become a realistic sequence.
Compare the modes“Photosynthesis” is a topic. “Help me explain why light intensity changes the rate, then give me one check question” is an outcome. The second request tells the workspace what useful progress looks like.
See prompt anatomyLevel, deadline, source material, allowed methods, lesson duration, and assessment purpose can change the route. Personal identifiers and unrelated private details usually do not help and should be left out.
Use minimum contextThe current output is a local product sample, not a correctness judgement. Choose Quick for the minimum route, Standard for verification and next actions, or Deep for assumptions and likely failure points. In a future live system, the same review rule remains: check reasoning, sources, classroom fit, academic integrity, and the learner’s own understanding.
Keep session controlThe mode should change the shape of support, not merely recolour the interface.
Use it to locate confusion, connect ideas, practise a new example, and check understanding.
Start a study brief ↗Use it to identify knowns and unknowns, choose a method, show transformations, and verify the result.
Start a math brief ↗Use it to diagnose claim, structure, evidence, transitions, and clarity while preserving the writer’s judgement.
Start a writing brief ↗Use it to define the objective, level, question mix, answer evidence, and follow-up after mistakes.
Start a quiz brief ↗Use it to turn deadlines, available time, confidence, energy, spacing, and buffers into a realistic week.
Start a planning brief ↗A clear request combines an outcome, the context that changes the route, and the kind of evidence or response shape you need.
Help me with algebra.
The topic is visible, but the exact obstacle and useful outcome are not.I understand linear equations but get stuck when fractions appear. Show one worked example, explain why each transformation is valid, then give me a similar problem to try.
Depth changes the amount of local scaffolding, not the truth of the result. The current browser sample still does not know whether subject content is correct.
After each completed local sample, choose what should happen next. The choice is stored only with the local session and never sends a request automatically.
The current workspace keeps automatic recovery data only in the browser tab. You can copy or download a readable Markdown version, export an integrity-checked portable Boardesa session file, import that file later, clear the session, change modes, switch response style or depth, or stop local sample generation. Import and validation remain local to the browser. Before a file can replace the tab, Boardesa enforces a 256 KB limit, bounded JSON depth and field counts, duplicate-key and blocked-property checks, schema/date verification, strict session limits, and SHA-256 integrity; the user then reviews metadata without revealing prompt content.
Check the method, assumptions, missing context, and fit for the learner or classroom.
Use a follow-up, choose a learning check, or edit the request instead of accepting the first structure automatically.
Download a readable Markdown copy or an integrity-checked Boardesa recovery file. Import only files you chose, and clear the tab when local work is no longer needed.
The interface, mode switching, prompt-aware local samples, response-depth controls, mode-specific checkpoints, context controls, quota-aware tab recovery, bounded portable session validation, exports, accessibility behaviour, and sample response flow are active. A live AI provider, user accounts, uploads, subscriptions, and payments are not connected yet.
Read the launch boundaries ↗Boardesa remains a readable static site when scripts are blocked or fail to load. The interactive workspace and browser-level controls pause, but product explanations, policies, help routes, direct email links, and a compact navigation path remain available.
Use All Tools, Responsible AI, Security, Privacy, Accessibility, and planned Pricing pages without an interactive runtime.
The Contact page keeps direct mail links available even when its local message builder cannot run.
JavaScript is required for prompt-aware samples, same-tab recovery, portable session validation, browser diagnostics, filters, and PWA install controls.
After creating a local sample, open the Session menu and choose Export settings before copying, downloading Markdown, or printing. Boardesa prepares a clean browser-only learning sheet rather than printing the full workspace interface.
Learning structure, route steps, checkpoint, evidence, next move, and the learning check are included. Prompt-specific topic text is replaced with [learning topic], while the raw request, selected context, unsent drafts, exact time, build data, operation identifiers, and integrity values are omitted.
Choose this profile only when you need request text, selected context, an unsent draft, exact preparation time, and build ID in the copy.
The integrity-checked recovery file is separate from readable exports and contains the complete local session. Review it before sharing and store it as private working data.
Open Session → Storage & retention to view the rolling two-hour expiry, disable snapshots for the current tab, or clear only the saved snapshot.
Back/forward cache can revive an older page instance. Boardesa compares the session lineage and monotonic revision before every save. If the stored revision is newer, saving pauses and you choose whether to load the newer snapshot or keep the visible page as a new lineage.
Duplicated tabs remain separate browser sessions. If two visible tabs restore the same lineage, Boardesa uses ephemeral same-origin signals to select one writer and pauses saves in the other tab. The signal includes only random tab and lineage IDs, revision numbers, visibility, and heartbeat timing — never the request or transcript. You can take control in the current tab or fork the visible work into a separate lineage.
Export a private recovery file when you intentionally need to move a complete session between browsers or devices.
Need to confirm what is active? Open the System Status page.