Settings
General
Client
The text-generation client to use for narration generation.
Optimize for Prompt Caching
Places volatile context (long term memory, dynamic notes) after the scene history so that the stable part of the prompt can be cached by API backends. May confuse weaker models. Auto defers to the client setting.
Generation
Generation settings for the narrator agent.
Jiggle
The amount of randomness to apply to the generation. This can help to avoid repetitive responses.
Instructions
Extra instructions for the generation. This should be short and generic as it will be applied for all narration.
Generation Length Per Narration Type
Generation length is configurable per narration type. Each type of narration can have its own maximum token length, allowing you to control how verbose different types of narration are:
- Progress Story -- general story progression narration
- Scene Narration -- environment and scene descriptions
- Query Narration -- responses to player queries
- Character Narration -- character-focused narration (look at character)
- Time Passage -- narration during time jumps
- After Dialogue -- automatic narration after character speech
- Character Entry -- narration when a character enters the scene
- Character Exit -- narration when a character leaves the scene
Content
Content settings control what contextual information is included in the prompts sent to the AI when generating narration.
Use Scene Intent
When enabled (default), the scene intent (overall intention) will be included in the narration prompt. This helps the AI generate narrative content that aligns with your story goals and the current scene direction.
Disable this if you want the AI to generate narration without being influenced by the scene direction settings.
Use Writing Style
When enabled (default), the writing style selected in the Scene Settings will be applied to the generated narration.
Disable this if you want the AI to generate narration without following the scene's writing style template.
Narrate time passage
The narrator can automatically narrate the passage of time when you indicate it using the Scene tools.
Guide time narration via prompt
Wheneever you indicate a passage of time using the Scene tools, the narrator will wait for a prompt from you before narrating the passage of time.
This allows you to explain what happens during the passage of time.
Auto Narration
New in 0.37.0
Replaces the Narrate after Dialogue action. The old auto-trigger fired a single, fixed narration type after every character turn; Auto Narration is a probability-gated dispatcher that can fire any one of three narration types — including the same post-dialogue narration that the old action ran.
Container action that fires narration on its own during the scene loop. Disabled by default; quick toggle available next to the agent's General settings.
See Auto Narration for the full description, weights breakdown, and gating rules.
Chance
Master probability that anything fires on a given actor turn. Range 0.0–1.0, step 0.05. 0 never fires; 1 fires every turn. The chance roll is the last gate — feature-disabled, scene-direction suppression, and zero weights all skip the roll entirely.
Action Weights
Relative likelihood of each action when auto narration fires. Three sliders that auto-rebalance to always sum to 1.0:
- Progress Story — moves the story forward (uses
progress_story). - Narrate Scene — visually-focused description of what is currently happening (uses
narrate_scene). - Narrate Environment — post-dialogue ambience and reactions, focused on sensory information (uses
narrate_after_dialogueinternally; the response length budget for it lives under Generation Length Per Narration Type → After dialogue).
Drag any slider to set its weight; the other two redistribute proportionally to make the total stay at 1.0. The slider you released last is "pinned" (a small icon appears next to its label) so you can adjust a third slider without disturbing the value you just set. A weight of 0 removes that action from the pool entirely — the chance roll still happens, but the action is not eligible to be picked.
Disable during scene direction
Default on. When the director's Scene Direction is enabled — either via the agent toggle or a scene-level always-on override — Auto Narration is skipped. Turn this off if you want both systems running at once.
Long Term Memory
If enabled will inject relevant information into the context using relevancy through the Memory Agent.
Context Retrieval Method
What method to use for long term memory selection
Context queries based on recent context- will take the last 3 messages in the scene and select relevant context from them. This is the fastest method, but may not always be the most relevant.Context queries generated by AI- will generate a set of context queries based on the current scene and select relevant context from them. This is slower, but may be more relevant.AI compiled questions and answers- will use the AI to generate a set of questions and answers based on the current scene and select relevant context from them. This is the slowest, and not necessarily better than the other methods.
Number of queries
Only shown for the two AI-assisted retrieval methods. It means different things depending on the method.
- For
Context queries generated by AIthis is the number of queries to generate. - For
AI compiled questions and answersthis is the number of questions to generate.
The default is 5. None (Semantic similarity only) does not use it.
Answer length
The maximum response length of the generated answers.
Cache
Enables the agent-wide cache of long term memory retrieval. Agents that share the same long term memory settings share the cache. AI-assisted retrieval publishes a cached result; character-scoped retrieval in Character perspectives mode can also cache semantic-only results. Standard semantic-only retrieval remains uncached.
Regenerating a reply reuses a published result only when the story before that reply, the memory sources available to the retrieval, and its settings are unchanged. New or edited world entries, character details and archives refresh affected cached results, as do relevant knowledge visibility and memory-collection changes. When retrieval is limited to character knowledge, access rules tied to the reply being regenerated do not count as earlier sources. Without that limit, access rules do not affect retrieval. Changes to older retained access rules still refresh affected results. A retrieval already in progress can finish with its earlier context. A result built before one of those inputs changed is not reused after the change.



