> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.rydhm.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.rydhm.ai/_mcp/server.

# Versions and testing

Changing a live expert is safe in Rydhm for three reasons:

1. **The Test panel runs on your unsaved edits**, so you hear a change before anyone else does.
2. **Your browser keeps a copy of unsaved edits**, so a closed tab or a crash doesn't lose them.
3. **Every save is a version** you can compare and restore.

## Test unsaved changes

Choose **Test** in the expert's header. From wide screens the Test panel is a rail beside the form (choose **Test** again to hide it; Rydhm remembers). On smaller screens it slides over the page.

The panel has two modes:

* **Chat**: type to the expert like a customer.
* **Voice**: choose **Start voice test** and talk through your microphone. The panel shows when the expert is **Listening**, **Thinking…** or **Speaking**.

![The Test panel in Chat mode, with a question about Saturday opening hours and the answer](/_fern-files/_img/dc6cd354f385ff0d0bdc5dd42adc667107ee553ede300b5c1323b02b6fb6e2d0.webp)![The Test panel in Chat mode, with a question about Saturday opening hours and the answer](/_fern-files/_img/ef47b9707c3825453fbed7db33c3bc908c9b53cc78d85ec672dbb239bf351a45.webp)

While you have unsaved edits, the panel says **Testing unsaved changes**: it runs on the name, persona, first message, guardrails and Voice-tab settings on your screen, for this test only. Nothing is saved, and nobody else gets the edits.

> **Info**
>
> Some edits can't travel to a test: tools, the website widget, the avatar and background. The panel names them and offers **Save to test**. On a live expert it asks first, because saving changes the expert on your website and in new meetings too.

If the expert uses [variables](/experts/persona#variables), **Variables for this test** lets you type values for the next message or call. Your defaults are filled in.

Only admins can test unsaved edits.

## Recover unsaved edits

As you edit, your browser keeps a copy of your unsaved changes, for you and this expert only. If you leave without saving (a closed tab, a crash, a lost session), the next time you open the expert you see:

*"You have unsaved edits from 5m ago"*, followed by the fields you changed, with two choices:

* **Restore draft** puts the edits back in the form, still unsaved, so you can review them before choosing **Save changes**.
* **Discard** lets them go.

If a teammate saved the expert in the meantime, the banner says so: restoring lays your edits over theirs.

The copy is removed when you save or discard. It lives only in this browser; a private window may not keep it.

## Version history

Each of these writes a new version of the expert:

* creating it;
* every save that changed something;
* making it live, or changing who can talk to it;
* restoring an older version.

Before an expert's first versioned save, Rydhm also keeps its earlier state, so even the first save can be undone. Rydhm keeps the last 100 versions of each expert.

### Look at a version

#### Open History

In the expert's header, open **⋯** → **History**. The list shows each version (**v1**, **v2**, …) with who saved it, when, and which parts changed. The newest is marked **Current**. **Show older** loads more.

#### Pick a version

Choose a row to see what it holds. Switch between:

* **Changes**: *What this save changed*, compared with the version before it.
* **vs. now**: *What restoring would change*, compared with the expert as it is saved now.

Prompts are shown as a line-by-line diff; settings as before and after.

#### Restore it

Choose **Restore this version** and confirm. The restore is a new save, so nothing is lost: you can restore the version you just left.

### What a version covers

A version records the expert's name, description, persona, first message, photo, background, voice and behavior settings (engine, voice, languages, guardrails, call experience, phone and meeting settings), tools, and website widget.

A restore **does not change**:

* whether the expert is a draft or live, and its link;
* its **Active** switch;
* which websites may embed it.

So bringing back an old persona never takes a live expert offline, or puts a draft online.

> **Warning**
>
> Versions don't include **knowledge**, **outside tool servers (MCP)** or **specialist hand-offs**. Those are saved on their own and aren't changed by a restore.

## Working alongside teammates

* A save sends only the fields you changed. If a teammate saved other fields in the meantime, both changes are kept and you see *"Saved, together with a teammate's changes"*.
* If you both changed the same field, **A teammate changed this expert** asks you to **Keep mine and save** or **Use theirs**.
* Leaving with unsaved edits asks you to **Keep editing**, **Save and leave** or **Discard changes**.
* **Discard** in the header returns the form to the last saved version.

## Gotchas

* **Restore waits for a clean form.** Save or discard your edits before restoring.
* **Only admins restore.** Members can read the history.
* **Tool switches save at once**, outside **Save changes**. See [Tools](/experts/tools).
* **Unsaved edits are too large to test** above about 60 kB. Save first.

## Related

* [Create an expert](/experts/create)
* [Persona and first message](/experts/persona)
* [Test suites](/quality/test-suites)