Skip to content
Stellaris CompanionField Manual

Start typing to search the human and agent-readable manual.

ReferenceHumans + agents

How Stellaris Companion works

The local pipeline from save ingestion to campaign briefings, agent tools, and player-authored stories.

Read as MarkdownEdit this page ↗Reviewed 2026-07-31
On this page

The Companion is a local-first interpretation layer between a Stellaris save and the questions a player wants to ask.

The pipeline

flowchart LR
  accTitle: Stellaris Companion campaign data pipeline
  accDescr: A local Stellaris save is parsed into a campaign archive, which produces focused briefings for the Advisor and connected AI clients, plus Chronicle drafts when requested.
  Save["Local .sav file"] --> Parse["Ingest + parse"]
  Parse --> Archive["Campaign archive"]
  Archive --> Brief["Focused briefing"]
  Brief --> Advisor["In-app Advisor"]
  Brief --> MCP["Local MCP server"]
  MCP --> Client["Connected AI client"]
  Archive --> Chronicle["Chronicle draft"]
  1. Ingest: discover or import a local .sav file.
  2. Parse: extract structured campaign facts.
  3. Archive: preserve snapshots so change over time is visible.
  4. Brief: select the facts relevant to a question.
  5. Interpret: let an advisor or connected AI app reason over that briefing.
  6. Narrate: turn selected events into Chronicle drafts when the player asks.

Read the detailed pages on save parsing and history, advisor briefings, and privacy and data flow.