Skip to content

The AI Creator

The Creator is Pyre's conversational workbench for building and editing roleplay assets: character cards, scenario cards, personas, and lorebooks.

What it is

You describe what you want to an architect model, keep talking until the idea is clear, and then ask it to build. The result appears in a live Sheet before anything is saved, so you can read, edit, and approve the fields instead of trusting a hidden generation.

Each in-progress build is its own session. You can keep several going, pin or rename them, retry a turn, and come back later. A session only writes to your library when you choose to save.

The build flow

The old guided flow is gone. The current Creator is freeform conversation plus a deterministic structured build:

  1. Describe the idea in any phrasing or language.
  2. Keep chatting to refine it, attach references, or ask questions.
  3. Say /build or ask the architect to build when you are ready.
  4. Pyre runs a fixed set of build passes. Each pass fills a known batch of fields as structured JSON.
  5. The finished Sheet appears field by field for review and hand edits.

Because every required field belongs to a specific pass, completeness is structural. If a pass comes back short, Pyre continues it a bounded number of times, then surfaces any remaining gap as a note instead of looping forever.

Creator modes

Character architect

Builds a full chara_card_v2 character: description, personality, scenario, first message, example dialogue, system prompt, post-history instructions, tags, alternate greetings when requested, and the rest of the standard fields.

Scenario architect

Builds an omniscient narrator / Gamemaster card that can voice NPCs inside a setting. Scenario cards include structured sections for the narrator, how the persona is read, scene setup, tone, world, and NPC cast, so the result is a playable world instead of a lone narrator.

Persona creator

Builds or edits a persona: your name, description, avatar/reference material, and dialogue examples that teach the model how you speak. Personas made here work with normal chat, Impersonate, Guide my message, and persona-party chats.

Lorebook builder

Builds a lorebook inside the same Sheet. The model emits entries with trigger keys, content, constant flags, and supported selective/probability fields. Each entry is visible and editable before save.

When you build a character or persona, the Sheet can also hold an embedded lorebook draft for that asset. Saving materializes those entries as a hidden bound lorebook, so the card/persona carries its world.

Editing existing assets

Edit with AI opens an existing character, persona, or bound lorebook in a Creator session. Ask for a specific change and the Creator edits only the named field or section, preserving the rest of the card instead of rewriting everything.

You can save back in place or save as copy to fork the asset. This works for imported cards too, including cards with freeform descriptions that were not originally built by Pyre.

References and attachments

You can ground a build with material you already have:

  • Library references: attach an existing character, persona, or lorebook from your Pyre library.
  • Card files: attach a chara_card file and feed its full JSON as context.
  • Documents: attach text, Markdown, or PDF material as source text.
  • Images: attach a reference image for appearance or lore context.

On native platforms, image picking uses the photo gallery for avatars, backgrounds, gallery photos, and references. Card imports still use the file picker so embedded card metadata is preserved.

Vision and image references

For image references, a vision model writes a clinical appearance profile that feeds the build. Vision can use its own provider/model route, separate from normal chat and Creator text calls, and Pyre raises the output-token floor so multi-character or detailed images are less likely to be cut short.

If a vision profile still looks truncated, Pyre shows a non-blocking note so you can regenerate or continue without losing the session. Large images are downscaled before upload.

Alternate greetings

The Creator does not add alternate greetings on its own. Ask for them when you want them. When requested, it writes complete standalone openings in genuinely different situations rather than paraphrases of the first message.

Creator presets

The architect prompts ship as locked Pyre Default Creator presets. Pyre re-seeds the locked defaults on app updates so prompt improvements reach existing installs. Copy a default to make an editable fork.

The Your additions field appends standing instructions to the architect prompts, such as "always reply in Portuguese" or "always include at least three NPCs."

Length and sampling controls

The Creator has controls for:

  • Description size: choose whether the generated description should be compact or long-form.
  • Design chat sampling: for the freeform conversation.
  • Vision analysis sampling: for image understanding.
  • Canvas updater sampling: for the lower-temperature Sheet-writing pass.

That split lets the brainstorm stay creative while the final fields stay stable.

Sessions

Sessions are managed in a drawer:

  • Auto-name from the asset as it fills in.
  • Pin, rename, or delete sessions.
  • Retry a turn to restore the pre-turn Sheet snapshot and rerun.
  • Auto-cleanup empty sessions.
  • Saved badge once the result has been written to your library.

The recommended-models banner points you at models that tend to perform well for structured card building.

The model matters

Creator quality depends heavily on the model. A capable model that follows structure and does not refuse harmless roleplay craft will produce better cards than a weak or overly cautious one.

See also