Export

AI Supreme Council provides two levels of export: individual chat export (single conversation) and full data export (all bots, sessions, and settings). Both run entirely in your browser with no server involved.

Chat Export

Export the current conversation in one of three formats.

How to Export a Chat

1. In the config panel (right sidebar), find the Export Chat section
2. Select your desired format from the dropdown: JSON, Markdown, or Plain Text
3. Click the Export Chat button
4. The file is downloaded to your device

The downloaded file is named after the bot (e.g., Research Assistant.json, Research Assistant.md, Research Assistant.txt).

note

If the current conversation has no messages, the export button shows an error toast: "Nothing to export."

JSON Format

The most complete format. The JSON export includes the platform version, full bot configuration (provider, model, system prompt, temperature, max tokens), the complete message array with roles, and an export timestamp.

Best for: Archiving, re-importing, programmatic processing.

Markdown Format

Human-readable format with a heading for the bot name, followed by each message labeled with its role in bold (User:, Assistant:, System:). Messages are separated by blank lines. Non-string content (e.g., multipart messages with images) is serialized as JSON.

Best for: Documentation, sharing, reading in any text editor or markdown viewer.

Plain Text Format

Simple text dump with the bot name as a heading (underlined with equals signs), followed by each message prefixed with its role label (User:, Assistant:, System:). No formatting beyond basic labels.

Best for: Copying into emails, pasting into other tools, maximum compatibility.

Full Data Export

Export everything in your AI Supreme Council instance -- all bots, conversations, settings, memories, and add-on manifests.

How to Export All Data

1. Open Settings
2. In the General tab, find Data Management
3. Click Export All Data
4. A file named ais-backup-YYYY-MM-DD.json is downloaded

If you have SQLite blob data (for large binary storage), a separate .db file is also downloaded automatically alongside the JSON backup.

What Is Included

Data	Included
All bot configurations	Yes
All chat histories (every ais-chat-* key)	Yes
Bot memories (every ais-memory-* key)	Yes
Profiles	Yes
Reminders	Yes
Add-on manifests	Yes
Mini-program data	Yes
Settings and preferences	Yes

What Is Excluded

Data	Reason
API keys	Security -- any key containing apikey in the storage key name is filtered out
Profile API keys	Security -- member keys in ais-profiles are stripped during export
Theme preference	Stored in localStorage, auto-detected on import
OAuth tokens	Security -- authentication credentials are never exported

The export function (AIS.Storage.exportData()) iterates over all IndexedDB entries and explicitly filters:

• Any key containing the string apikey is skipped entirely
• The ais-profiles array has its member API keys stripped (only p and m fields are kept per member)

warning

API keys are intentionally excluded from all exports. This is a core security guarantee. When you import data on another device, you will need to re-enter your API keys.

Export File Format

The JSON backup file has this structure:

{
  "bcz_version": "1.0.0",
  "exported": "2026-02-19T12:00:00.000Z",
  "data": {
    "ais-bots": [...],
    "ais-chat-abc123": [...],
    "ais-chat-def456": [...],
    "ais-profiles": [...],
    "ais-reminders": [...],
    "ais-memory-abc123": [...]
  }
}

Import

Importing a Backup

1. Open Settings
2. In the General tab, find Data Management
3. Click Import Data
4. Select a .json backup file or a .db SQLite file

JSON Import

The import function reads the data object from the backup and writes each key-value pair back to IndexedDB. Keys containing apikey are skipped during import for security. After import:

• All bots and conversations from the backup are restored
• The bot list refreshes automatically
• If the backup contains bots, the first one is automatically selected
• A toast shows the count of imported items

SQLite Import

For .db files, the binary data is written directly to OPFS (Origin Private File System) as bcz.db. The app must be reloaded after SQLite import to pick up the new database.

Import Formats

File Type	What It Contains	Post-Import
.json	Full backup from Export All Data	Immediate -- bots reload automatically
.db	SQLite database with blob data	Requires page reload

info

Importing a backup does not delete your existing data -- it merges the imported data with your current bots and conversations. If there are key conflicts, the imported data overwrites existing entries with the same key.

Storage Backend

The export and import system works with the platform's tiered storage:

• IndexedDB (primary) -- all structured data (bots, chats, profiles, memories)
• SQLite WASM (optional) -- large binary blobs, enabled in Settings

You can see the current storage status in Settings > General > Storage Backend, which shows whether IndexedDB is active and whether SQLite is loaded.

Practical Tips

• Regular backups: Export your data periodically, especially before clearing browser data
• Cross-device transfer: Export on one device, import on another to move your conversations
• Version control: The JSON export is text-based and can be stored in version control
• Selective sharing: Export a single chat in Markdown format to share a conversation without exposing your full data
• API key safety: You never need to worry about accidentally sharing API keys through exports -- they are always stripped