Demo mode

Demo mode is a shared sample organization. You can look around a full account without sending any data of your own. It is read-only, and your own workspace is never touched.

Switch in and out

Open the workspace switcher and pick Demo (sample data) · Read-only.

While you are in demo mode, a banner at the top says you are viewing demo sample data. To leave, use Exit demo in the banner, or pick your own workspace in the switcher.

If the Demo entry is missing, it has been hidden. The Show Demo workspace in switcher toggle in Workspace settings turns it back on. Hiding it does not force anyone out of demo mode.

What it covers

Demo mode covers Home and the weekly brief, and the Observe, Diagnose, Optimize and Evaluate screens. It also covers Settings › Setup, the setup checklist.

What is in the sample data

The sample is one organization. A daily job moves it forward in time, so the last 30 days always look current. These states are seeded on purpose:

Agents and traces. A fleet of agents with traces across the last 30 days, infrastructure calls inside some traces, and one archived agent. Every span carries a realistic input and output, so a demo run’s span detail shows what the step received and returned rather than “No input captured”.
A weekly brief. A five-agent fleet with labeled and unlabeled runs, a prior-week comparison, and two weeks of brief history for the week picker.
Failing runs. Error groups with several exception patterns, including one that regressed after a deploy.
Alerts and incidents. Firing alerts, a completed investigation, service targets, and an open and a resolved incident.
Budgets. An org budget and an agent budget, one budget waiting for approval, and one past breach that was signed off.
Cost and billing. Provider bills that cover part of the traced spend, customer revenue in three coverage states, and a prompt-cache opportunity.
Change verdicts. Improved, worsened, inconclusive, still-collecting and rolled-back changes.
Outcomes and spot-checks. Inferred outcomes, spot-check questions, a connected GitHub installation, and agents with record keys.
Quality. Rule-based checks, retrieval-quality scores and a replay.
Prompts and context. Hosted prompts, prompt versions tied to outcomes, and context economics for two agents.
Setup checklist. A mix of done, partly done and not started items.

What is outside demo mode

Account pages always show your own workspace: Settings (except Settings › Setup), Profile, Notifications and Billing. If you open one of them while in demo mode, you leave demo mode for your whole account, in every tab, and a toast tells you so.

Three more things never use sample data:

The notifications bell always shows your own account’s notifications.
Your Ask Morse message quota is yours.
Billing and usage are yours.

Why you cannot change anything

Everyone who opens demo mode sees the same data. So creating, editing, deleting, accepting, dismissing, sharing and similar actions are switched off. A disabled control says Read-only in demo when you hover or focus it.

The server enforces the same rule. A write to a demo data path from someone in demo mode is rejected, even if a button were enabled by mistake.

Want to try a write action? Exit demo and use your own workspace.