KoboldAI to Agnai Character Conversion

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 converter reads the fields it recognizes in the KoboldAI data and copies each one to the matching Agnai field, so your text arrives as written.

2. Working with 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. Beyond the changes listed under "What this converter changes", your descriptions and dialogue are carried over exactly as written. Our converter reads the fields it recognizes in the KoboldAI data and copies each one to the matching Agnai field, so your text arrives as written.

3. Dialogue and Tokens

KoboldAI-era files sometimes contain model-specific tokens or artifacts required by legacy backends. Agnai uses a more modern tokenization strategy.

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 Fields

Agnai characters benefit from descriptive tags and versioning info to help manage large libraries. The name, description, personality, scenario, first message and example dialogue are written to the Agnai JSON; tags and version metadata are not generated. This facilitates easier organization and ensures your characters are ready for advanced Agnai features like "Lorebook Sharing" and "Cross-Platform Syncing."