SpiritBox settings interactive simulation
Read-only simulation: controls and status values are examples. Changing them does not configure SpiritBox or contact a service.
Preview limits
It shows how local-core and optional-connection settings are organized. It does not prove the state or behavior of an installed system.
Settings
Example controls for models, voice, local storage, and optional connections
AI Model
Active ModelExample local model
ProviderSpiritBox LLM Engine
Context WindowModel dependent
Auto-load on startup
Response styleExample setting
Voice Settings
TTS EnginePiper TTS (Local)
InputTyped messages
Microphone inputNot included
Ready voiceen_US-kathleen-low
Voice Output (TTS)
Security
Egress Firewall
Aegis Sanitizer
Data Sanitizer
Credential controlsExample setting
Outbound connectionsReview by integration
Connectivity
Telegram Bot
MessagingOptional integration
Web SearchOptional configured service
AutomationOptional configured bridge
Memory System
Knowledge GraphExample service label
Vector StoreExample service label
Human Approval Gate
Auto-Detect Facts
Pending factsExample state
Portability
Conversations, memories, guides, voice assets, and settings can have different storage and export paths. Review the documentation for the edition and services you install before relying on a backup or migration workflow.
Connection boundaries
Local model path
A configured local model can handle supported chat work on user-controlled hardware.
A configured local model can handle supported chat work on user-controlled hardware.
Voice controls
Input is typed. Voice output is edition-specific and depends on installed voice assets. Microphone and two-way voice are not included.
Input is typed. Voice output is edition-specific and depends on installed voice assets. Microphone and two-way voice are not included.
Optional connections
Search, messaging, automation, hosted models, and other enabled integrations can send data outside the device.
Search, messaging, automation, hosted models, and other enabled integrations can send data outside the device.
Provider terms
Third-party services, models, and workflow tools retain their own terms, logs, licenses, and data practices.
Third-party services, models, and workflow tools retain their own terms, logs, licenses, and data practices.