Skip to content

Admin Settings — Overview

This content was created from codebase analysis. The legacy document Documentation/ADMIN_SETTINGS.md was not found; all information is verified against the current implementation.

What This Module Does

The Admin Settings module provides a superuser-only API for managing Swisper's runtime configuration. It covers three areas:

  • LLM Node Configuration — View which LLM model and provider each graph node uses (intent classification, fact extraction, summarization, etc.)
  • Swisper Studio Integration — Configure and test the connection to Swisper Studio, an external observability and debugging tool that receives real-time event streams from the backend via Redis
  • System Diagnostics — View system configuration (with passwords masked), access backend logs, and check version/build metadata

All endpoints require superuser authentication. The module is read-only for LLM configuration (changes are made via database migrations) and read-write for Swisper Studio configuration.

Who It Serves

Persona Need
Platform Administrators Runtime visibility into LLM configuration and system health
Developers Swisper Studio connection setup for real-time debugging and observability

Key Capabilities

  • LLM node config viewing — See all node configurations: model, provider, temperature, reasoning settings, description
  • Swisper Studio management — Enable/disable, configure Redis connection, test connectivity, check consumer heartbeat
  • System config overview — View all configuration values with automatic password masking
  • Log access — Read and filter backend logs by level and search term; clear log buffer
  • Version info — Build metadata and dependency versions
  • Greeting reset — Reset the greeting timer for a user's avatar (useful for testing)

How It Fits in the Platform

  • API layer: Exposed at /api/v1/admin/settings — protected by superuser authentication
  • Swisper Studio: Connects to an external Redis stream (observability:events) where the backend publishes real-time events (node execution, token usage, state changes). Swisper Studio consumes this stream for live debugging
  • LLM configuration: The llm_node_configuration table controls which model and provider each graph node uses. The admin API provides read-only visibility; changes are applied via migrations or direct DB updates

Limits and Edge Cases

  • LLM config is read-only via API — No endpoint to change node models at runtime. Changes require database updates and a config cache refresh
  • Swisper Studio requires Redis — The Studio connection relies on a Redis stream. If Redis is unavailable, Studio events are lost (not queued)