Trying the demo

The demo is Claudette on made-up projects, with a stand-in for Claude, so you can see what it’s like before you have a Claude subscription, or show it to someone who hasn’t. It needs no account and no Claude Code, works offline, and costs nothing.

Starting it

Choose Try the demo:

on the sign-in screen, beside Sign in (Signing in);
or on the setup screen, when Claude Code isn’t installed or can’t be used (The first launch).

The demo opens in a window of its own, titled Claudette demo. The window you started it from stays as it was: your tabs, or the sign-in screen.

What’s in it

Three game projects, an Unreal one, a Unity one and a Godot one, with seven tabs over them: a long conversation with Claude’s changes, a thread with two sub-threads, a plan and a task list part-way done, subagents and marks. History lists past sessions over seven projects, the usage header shows a session part-way through with its trend and projection, and one project runs on an API-key account, Studio, with a month of its spend.

The projects have no files: their folders are empty, so a diff or the Files tab has nothing to show.

Talking to the stand-in

Send a message in any tab on the Default account and the stand-in answers with the next of a few example turns, so you can see how Claudette shows Claude’s work:

A short answer that says what the demo is.
Thinking, then an answer with a list and a code block.
A file read, then a file it asks your permission to write. Nothing is written, whichever you choose.
A question for you to answer, and a reply that goes by your answer.

Then it starts again. It can’t read your projects or run anything, and nothing you send leaves your computer.

Leaving it

A banner across the top of the demo’s window says it’s a demo. Leave demo, at its right, closes the demo, as closing its window does, and what it made goes with it. Nothing in it touches your settings, your tabs, your History or Claude Code’s own files.