跳转到内容
TomoriBot

Status Command

此内容尚不支持你的语言。

/status is the read-only snapshot command for durable personal, server, and persona state.

It exists so users can inspect current configuration without reopening every management command.

Implementation Boundary

Section titled “Implementation Boundary”
  • Slash command registration and routing live in src/commands/status.ts.
  • The status coordinator lives in src/utils/metrics/status/command.ts.
  • Persistent category/page IDs and global interaction routing live in src/utils/discord/statusDashboardCatalog.ts and src/utils/discord/interactions/statusRoutes.ts.
  • src/utils/metrics/status/statusDashboard.ts resolves the same ordered category set for commands and routes.
  • Status page implementation lives under src/utils/metrics/status/:
    • personalPages.ts builds personal settings/provider pages.
    • personaPages.ts builds the five persona detail pages.
    • serverModelPages.ts, serverConfigPages.ts, and serverChannelPages.ts build the server status scopes.
    • channelFormatters.ts, providerConfigFormatters.ts, and sharedFormatters.ts own reusable redaction and display formatting.
  • /compact routing lives in src/commands/compact.ts; the public coordinator lives in src/utils/compaction/compactOrchestrator.ts, with implementation under src/utils/compaction/compact/.

Scope Coverage

Section titled “Scope Coverage”

/status provides five ordered categories: Persona, Behavior, Models, Access, and Personal. Every invocation opens on the main Persona’s Identity page. Every resulting dashboard displays all five category buttons at the top, allowing readers to navigate among every category without re-running the command. Category and page controls use persistent, versioned status:v1 interaction routes, so navigation remains available after the initial command interaction has finished.

Persona is a persistent global dashboard category. Opening it loads the current server roster and displays a bounded String Select with up to 25 persona options. Page choices use only their page name because the selected persona is already identified by the dashboard. Larger rosters use range buttons, and every range remains reachable. Selection and range routes carry only numeric persona IDs and offsets. Category and page routes preserve the selected persona ID, so navigating away and back rebuilds the pages from the fresh roster. These interactions are read-only and never use a collector or write to the database.

Category page counts:

  • Persona: 5 pages (Identity, Attributes, Sample Dialogues, Memories, Prompt and Tags)
  • Behavior: 3 pages (General Behavior, Channels and Automation, Thought Logs & Matrix)
  • Models: 4 pages (Models and Sampling, Overrides, Integrations and Endpoints, NAI Image)
  • Access: 3 pages (System Prompt, Capabilities & Moderation, Quotas)
  • Personal: 2 pages (Personal Status, Providers and Endpoints)

Personal

Section titled “Personal”
  • user nickname
  • language preference
  • privacy mode
  • impersonation prompt
  • reminder count
  • deliberate trigger mode
  • cross-server STM opt-in
  • NovelAI personal character tags/reference
  • global personal memories

Persona

Section titled “Persona”
  • persona identity and trigger words
  • model override
  • avatar / voice / NovelAI reference presence
  • conditioning toggles
  • attributes
  • sample dialogues
  • persona-scoped personal memories
  • persona-lineage server memories
  • persona prompt
  • NovelAI tags and ATTG metadata
  • persona author’s note

Server Categories

Section titled “Server Categories”

Status is rendered as a private Components V2 dashboard. Category buttons are placed above the page selector and page body, so readers can move between categories without re-running the command. The renderer reserves four of Discord’s 40 components for future controls and bounds Text Display output to Discord’s 4,000-codepoint limit.

  • Behavior: general behavior, system prompt, channels, and automation.
  • Models: model and sampling, overrides, NAI image configuration, integrations, and endpoints.
  • Access: capabilities, moderation, member access, and image, text, and video quotas.

Each page identifies the management command that owns its settings, so a status reader can return to the editor.

Privacy Rules

Section titled “Privacy Rules”

/status must not expose raw secrets or private external endpoints.

Redacted surfaces:

  • API keys: show presence or counts only
  • API key rotation: show counts/status only
  • optional API keys: show configured services only
  • saved provider configs: show provider names only
  • MCP auth tokens: never show token contents
  • custom endpoint URLs: show configured/not configured only
  • Matrix room IDs: do not show room IDs; show linked Discord channels/count only
  • welcome/random-trigger custom prompts: show configured/not configured only

Existing prompt preview pages remain intentionally visible because they are first-party editable bot instructions already owned by the requester.

Maintenance Rule

Section titled “Maintenance Rule”

When a new durable config surface is added:

  1. update the owning management command
  2. surface the resulting state in /status
  3. keep this document in sync
  4. preserve the redaction rules above for any secret-bearing fields