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

2. Working with 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. Beyond the changes listed under "What this converter changes", your descriptions and dialogue are carried over exactly as written. 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 Tokens

Pygmalion-era files sometimes contain model-specific tokens or artifacts that were required by early inference backends. Agnai uses a more modern tokenization strategy.

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 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 "World Sharing" and "Campaign Management."