1. Upload KoboldAI JSON

Technical Documentation: Mapping Legacy Kobold to Agnai

Moving a character from **KoboldAI** to **Agnai** is a process of transitioning from a backend-focused save file to a modern, web-orchestrated platform. While KoboldAI's JSON format is designed primarily to maintain the state of an inference session, Agnai requires a robust structure to support its diverse feature set, including persistent character libraries and group chat dynamics.

1. Overcoming Schema Fragmentation

KoboldAI JSON files typically use a flat structure with field names like description and scenario. Agnai uses a more structured JSON model that separates character identity, behavior, and metadata. Our conversion tool performs a "Semantic Scan" of the source JSON, ensuring that the behavioral goals defined in your Kobold characters are correctly mapped to Agnai's core blocks, maintaining consistency in character responses across different environments.

2. Optimizing for Agnai's Group-Chat Environment

Agnai is specifically built for multi-user interactions. Standard KoboldAI files are often optimized for a 1-on-1 interaction with an LLM. Our converter sanitizes the dialogue and scenario blocks to ensure they work seamlessly within Agnai's group chat interface. We preserve the intent of the character's core persona while formatting it to be compatible with Agnai's advanced "World" and "Campaign" management features.

3. Dialogue and Token Normalization

KoboldAI-era files sometimes contain model-specific tokens or artifacts required by legacy backends. Agnai uses a more modern tokenization strategy. Our conversion engine identifies and removes these artifacts from the first_mes and mes_example fields, resulting in a cleaner, more immersive roleplay experience that doesn't "break character" by outputting raw JSON keys or outdated meta-tags during a session.

4. Privacy and the "Zero-Server" Advantage

Because character development often involves personal creative effort, we prioritize security. Our tool utilizes a "Zero-Server" architecture, where all JSON processing is handled by your browser's local JavaScript. Your character files are never transmitted to our server, cached, or seen by any third party. This ensures that you maintain full ownership and control over your creative digital assets as you move them between platforms.

5. Metadata and Identity Preservation

Agnai characters benefit from descriptive tags and versioning info to help manage large libraries. Our converter automatically generates these metadata elements during the migration, ensuring that your Kobold characters are integrated as high-quality, manageable assets within your Agnai library. This facilitates easier organization and ensures your characters are ready for advanced Agnai features like "Lorebook Sharing" and "Cross-Platform Syncing."