Skip to main content

AI Settings

The page-admin AI screen stores the page-scoped provider configuration used for assisted workflows.

This is separate from Slack app credentials and separate from organization-wide admin authentication.

This guide is based on application/frontend/src/pages/admin/AISettings.jsx.

What the AI screen manages​

The current screen is intentionally narrow. It manages:

  • which provider the page uses
  • an optional model override
  • an optional base URL for compatible providers
  • either the encrypted API key for that page or a platform-provided LiteLLM route

The configuration is page-scoped, so different status pages can use different AI providers or keep AI disabled entirely.

Supported providers​

The current provider choices are:

  • Platform Provided
  • Anthropic
  • OpenAI
  • OpenAI-Compatible

Platform Provided only appears when the current runtime has StatiBeat-managed AI configured. It uses a platform LiteLLM base URL plus a platform virtual key, so the page does not store its own AI key.

When OpenAI-Compatible is selected, the Base URL field becomes required.

For other providers, the base URL field is hidden and the default provider endpoint is used.

Platform controls​

Page admins can choose Platform Provided, but they do not manage the LiteLLM deployment or its upstream provider keys from this screen.

The current platform control points are:

  • the managed LiteLLM model catalog, aliases, and non-secret routing policy
  • the public runtime endpoint distributed to managed environments
  • the shared-runtime in-cluster endpoint used by platform workloads
  • the platform LiteLLM access key supplied to managed runtimes
  • the LiteLLM master key and upstream provider keys handled by platform secret sync

Those implementation files live in the private deployment configuration for StatiBeat operators rather than in public page-admin docs.

In other words, page admins select whether to use platform AI, while operators control the actual LiteLLM endpoint, model policy, and secret material.

Save, rotate, and clear behavior​

The current form supports three common workflows:

  1. enable StatiBeat-managed AI with Platform Provided
  2. create or rotate a BYOK AI configuration
  3. clear the saved AI configuration entirely

A few details matter operationally:

  • the API key is never re-shown after save
  • leaving the API-key field blank keeps the existing saved key
  • changing providers should normally be paired with a new API key
  • stored keys are described in the UI as encrypted at rest
  • Platform Provided does not require or store a page API key

Where AI is used today​

The current screen describes AI as being used for assisted workflows. That now includes:

  • Slack incident drafting
  • Beat AI Info investigations
  • AI-assisted Beat creation in the web UI and in Slack threads
  • AI-assisted hierarchy creation in the web UI and in Slack threads

Those create flows are confirmation-first. The AI provider lives here, while the write itself still happens only after StatiBeat shows a normalized preview and a human confirms it.

The Slack page still controls things such as:

  • app connection
  • channel behavior
  • reminder settings
  • workflow confirmation mode for AI-thread initiated actions

Practical guidance​

Good defaults usually mean:

  1. use Platform Provided when you want StatiBeat to centralize LiteLLM spend and provisioning
  2. keep BYOK page-scoped when a tenant needs its own provider or billing boundary
  3. use the provider default model first unless you have a specific reason to override it
  4. document which page owns the API key and when it should be rotated for BYOK providers
note

The current AI screen is a provider-configuration surface, not a full prompt-management workspace. It enables assisted workflows that exist elsewhere in the product, and AI-planned writes remain preview-and-confirm rather than auto-executed.