Test-Drive Your Character Before You Publish

The Save-and-Pray Loop

Every character creator knows this loop by heart:

1. Fill in the persona fields
2. Save the character
3. Open a new chat
4. Send a few messages
5. Notice the character says "As an AI language model…" in turn three
6. Go back to the form
7. Tweak the description
8. Save again
9. Open another new chat (the old one is polluted)
10. Repeat

The problem isn't any single step. The problem is that testing is separated from editing by a save and a page navigation. By the time you see the character respond oddly, you've already committed it, your form state is gone, and you need a fresh context to see if the fix landed.

Good creators do this dozens of times per character. Great creators do it a hundred. The whole loop is where craft lives — but most platforms treat it as an afterthought.

We Looked Around. Almost Nobody Ships This.

Before we built this, we surveyed twelve AI character platforms to see how they handle iteration:

Out of the platforms we could verify, only Talkie AI ships a real in-editor preview chat bound to unsaved form data. Everywhere else, iteration means "save, open chat, edit, save again."

That's strange to us. Writing a good character is an iterative craft, and craft without a fast feedback loop is guessing. So we built Debug Chat.

What Debug Chat Is

Debug Chat is a floating button available on every character creation surface in Reverie — the traditional form editor, the conversational Labs builder, and the edit page for characters you've already published.

What it does:

• Click the floating button in the bottom-right corner of any creator page.
• A chat panel appears next to the form on desktop, or slides up from the bottom on mobile.
• Send a message. Your character responds — using the draft data currently in the form.
• Edit a field in the form. Hit retry on the last reply. The new answer reflects your edit immediately.
• Close the panel. Come back later. Your conversation is still there.

No save. No new chat. No credit cost. No polluted chat history in your account.

How It Fits Into Your Workflow

1. Live Iteration

This is the main event. Every field in the form — name, bio, description, personality, appearance, example conversations, custom system prompt, response format, NSFW guidelines — flows into the live preview. Edit any of them, send the next turn, and you'll see how the change played out. If the answer still doesn't land, retry the reply rather than starting over — the previous version stays, and you can swipe between them to compare.

2. Scenario Testing

If your character has multiple scenarios, the panel includes a scenario picker. Switch from "No scenario" to "Coffee shop first date," and the system prompt regenerates with that scenario's context. The conversation resets (scenarios change the character's behavior, so reusing the old turns would be misleading), and if the scenario has its own greeting, that greeting opens the new conversation.

This is genuinely useful. Scenarios are one of the hardest things to get right because their context layers on top of the base character, and layered prompts often surprise you. Flipping between scenarios against the same draft is the fastest way to catch those surprises.

3. Greeting and Suggested Replies

If your character has a starter dialog configured, Debug Chat seeds the conversation with that greeting and turns the suggested user replies into clickable chips. You see what a real user sees on turn zero. If the greeting feels weak or the suggested replies don't fit the persona, you'll know before anyone else does.

4. Regenerate, Edit, Delete

Debug Chat borrows the power tools from the real chat:

• Retry the last assistant reply — old version stays in memory, swipe left/right to compare.
• Edit your last message and re-run (useful when the problem is your phrasing, not the character).
• Delete any message — it and everything after disappears, so you can rewind to a specific fork.
• Clear the whole conversation with one click.

Everything is in-memory. Nothing touches the database.

The Ground Rules

We deliberately kept Debug Chat free, which means we had to cap it somewhere:

• 5 turns per conversation. Long enough to feel the persona, short enough that you don't treat it as a regular chat.
• 1000 characters per message. A debug probe, not a novella.
• 20 messages per day for non-subscribers. Plenty for iterating a couple of characters end-to-end.
• Unlimited for subscribers. If you're actively creating, the limit shouldn't slow you down.
• Free model, no credits consumed. We use our default fast model so the experience is representative and the cost stays on us.
• Nothing persists. No messages saved, no chat history, no credits deducted. Close the panel and the conversation lives only in this session.

These aren't arbitrary — they're the constraints that let us offer this for free without it quietly turning into a second chat surface.

Where to Find It

Look for the floating button in the bottom-right corner of any of these pages:

• The Create Character form
• The Edit Character page (for any character you've already published)
• The Labs conversational character builder

The button activates as soon as you have a name and a description — the minimum needed for a coherent chat. Fill those, click, chat.

Desktop and Mobile

On desktop, Debug Chat opens as a compact floating panel anchored to the bottom-right corner, so it sits next to the form and you can type, watch the stream, and edit the form without switching contexts.

On mobile, it rises from the bottom to fill almost the whole screen — because the whole point is that you're reading character output, and reading needs room. The message toolbar (retry, edit, delete, copy, alternate-response switcher) is always visible on touch devices instead of hidden behind hover, so every action is one tap away.

Either way, the conversation persists when you close and reopen the panel. Changed a field, want to see if the fix took? Open the panel, hit retry on the last reply. Done.

Why This Matters

The quality of a character is determined almost entirely by how many iterations it got before release. Platforms that make iteration expensive don't get bad characters — they get under-iterated characters. Authors who'd happily do twenty rounds of tuning stop at three because the loop is too painful.

We think character creation is craft. Craft needs a tight feedback loop. Debug Chat closes the loop.

Try it on your next character. Edit a field, hit retry, see the difference. Once you've felt it, going back to "save, open, chat, edit, save" will feel like typing through mittens.

---

Debug Chat is live now on character creation, editing, and the Labs builder. No setup required — just click the floating button.