-
Notifications
You must be signed in to change notification settings - Fork 26
Settings
All extension settings are available through SillyTavern’s Extension Settings panel. This page explains every option so you can tailor the extension to your workflow. After changing a setting click Save and reload the extension to apply changes.
The Show Action Buttons section lets you control which buttons appear next to the send button. You can toggle visibility for first‑, second‑ and third‑person Impersonation, Guided Continue, Guided Response and Guided Swipe. The first‑person Impersonate and Guided Response buttons are enabled by default; others are optional.
Use this section to decide which utilities appear in the tool menu. Options include Simple Send, Recover Input, Edit Intros, Corrections, Spellchecker, Clear Input, Undo Last Addition and Revert to Original. If a button is disabled here it will not appear in the UI.
- Integrate QR bar into GG button area: Moves SillyTavern’s quick‑reply bar into the same area as the Guided Generations buttons for a compact layout.
- Enable Debug Logging: When enabled, additional debug messages are printed to the browser console. This is helpful for troubleshooting but may clutter the console.
- Show Persistent Guides in Chatlog: Adds hidden guide content to the chatlog so you can see what has been injected. These messages are marked as system messages and are not sent to the AI.
Toggle automatic execution of Describe Clothes, Describe State, Describe Thinking and Custom Auto Guide. When enabled the corresponding guide runs after every AI message. Use auto‑triggers to keep descriptive context up to date without manual clicks.
The Send injections as dropdown controls which role the injected instructions use (system, assistant or user). System injections have the highest influence on the model. Assistant injections appear as if the AI is instructing itself. User injections treat guidance as coming from the user. Choose the role that suits your storytelling style.
The extension can run each guide or tool using a specific SillyTavern profile and preset. Profiles define the API/backend (e.g. OpenAI, Kobold) and presets define parameters like temperature or model. In the Preset Usage section you can assign a profile and preset for every guide or tool. Before executing an action the extension switches to the assigned profile and preset; after completion it restores your previous one. This allows you to use different models for different tasks—for example, a summarisation model for the Situational guide and a creative model for Impersonation.
If you suspect the profile system is not working correctly, use the Debug Profiles button in the settings to log diagnostic information to the console. Click Refresh Dropdowns if you recently added new profiles or presets and they do not appear.
For each guide or tool you can override the default prompt. The Prompt Overrides section provides a text area for every feature (Clothes, State, Thinking, Situational, Rules, Custom, Corrections, Spellchecker, Impersonation 1st/2nd/3rd, Guided Response, Guided Swipe, Guided Continue). Use the {{input}} placeholder to insert the content from the input box or other variables supported by SillyTavern. Click Default to restore the built‑in prompt at any time.
Each override has optional Raw and Depth controls:
-
Raw: Sends the prompt exactly as written without wrapping it in brackets. Use this for advanced STScript commands or when your prompt already includes the necessary
[ ]markers. - Depth: Sets how many messages the AI should scan when summarising or reworking content. A higher depth gives the AI more context. Depth is used by summarisation guides like Corrections and Situational.
In addition to {{input}} you can reference variables such as {{char}} (the character’s name) or {{user}} (your name) in your overrides. Consult SillyTavern’s documentation for a full list of available placeholders.
After editing any settings click Save at the top of the panel. Reload the extension if prompted. You can reset all settings to their defaults by deleting the extension’s settings object from the browser’s local storage via the Developer Tools console (advanced users only).