Skip to content

Core Concepts

A quick tour of Pyre's vocabulary.

Pyre in one paragraph

Pyre is a local-first, bring-your-own-key roleplay client. It does not host a model or store your library in a Pyre cloud. Native apps talk to your provider directly; browser clients can talk through a desktop or self-host hub you control.

Character

A character is who you talk to. Pyre uses the Tavern chara_card_v2 field set, so characters carry description, personality, scenario, first message, examples, tags, optional lore, and more.

Persona

A persona is who you are. It can include a name, description, avatar, dialogue examples, and bound lorebooks. A chat can use one persona, no persona, or a persona-party roster.

Group chat and Party Mode

A group chat contains multiple characters. With Party Mode off, you pick the next responder. With Party Mode on, the model writes one joint scene where the whole cast reacts together.

Scenario

A scenario is a narrator/Gamemaster card: a world and cast voiced by an omniscient narrator rather than a single character.

Lorebook

A lorebook is keyword-triggered World Info. Entries inject only when relevant, so large worlds do not spend context every turn. Lorebooks can bind to characters, personas, chats, and embedded cards.

Preset

A preset controls the prompt scaffold and optional sampling. Presets can be flat or modular. They can include {{summary}} to place Checkpoints exactly where you want them.

Checkpoints, Live Sheet, and Script

  • Checkpoints summarize what happened.
  • Live Sheet tracks current state.
  • Script points the story toward future beats.

Use them when a long scene needs memory, state, or direction.

Provider

A provider is the model endpoint Pyre calls. Native apps support OpenAI-compatible endpoints, Anthropic-native connections, and local servers. Browser/PWA clients can chat through a paired hub without storing keys.

Import, backup, sync

  • Import/export moves individual cards, presets, lorebooks, regex rules, and supported chats.
  • Backup/restore moves a whole Pyre library as a file.
  • Sync keeps paired devices and browser clients in step through your own hub.

See also