Pygmalion to Agnai Character Conversion

Moving a character from the classic **Pygmalion** standard to **Agnai** is a process of porting historical character data into a modern, web-orchestrated platform. While Pygmalion established the foundational "Prefix-Based" JSON schema, Agnai requires a more robust structure to support its diverse feature set, including group chats and complex model parameters.

1. Remapping Legacy Fields

The Pygmalion schema is known for its explicit key prefixes like char_name, char_persona, and char_greeting. Agnai, however, uses a cleaner, more generalized JSON model. Our conversion tool performs a "Semantic Alignment" of these fields. We identify the behavioral goals defined in the char_persona block and map them to Agnai's core description and personality blocks, ensuring the character's internal logic remains consistent during the transition.

2. Optimizing for Agnai's Group Dynamics

Agnai is specifically built for multi-user and multi-character interactions. Standard Pygmalion files are often optimized for 1-on-1 text completion. 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 world_scenario field, allowing Agnai's engine to correctly place the character within its narrative context, even when multiple actors are involved in the scene.

3. Dialogue and Token Sanitization

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

4. Privacy and Data Security

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 Pygmalion characters aren't just "orphaned data" but are instead 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 "World Sharing" and "Campaign Management."