CharacterAI to Pygmalion JSON Conversion

The migration from **CharacterAI (c.ai)** to **Pygmalion** JSON is a process of porting modern cloud-based character logic into the foundational "Prefix-Based" schema that helped define the early AI roleplay community. While CharacterAI uses a monolithic definition structure, Pygmalion relies on explicit, flattened keys that provide a clear roadmap for inference models.

1. Deconstructing the Definition Monolith

CharacterAI primarily stores character behavior in its Definition (Advanced) field. This field often contains a mixture of W-style descriptions, roleplay cues, and dialogue examples. To convert this effectively for Pygmalion, our engine performs a "Semantic Scan," identifying the core behavioral traits and mapping them to the explicit char_persona block, while ensuring that world-building elements are correctly placed in the world_scenario field.

2. Key Mapping and Prefix Standardization

The Pygmalion schema is defined by its foundational keys: char_name, char_persona, char_greeting, and world_scenario. Our converter identifies the source fields from CharacterAI and performs a "Deep Remap." This ensures that the character's core identity remains cohesive during the transition, allowing the resulting JSON to be used across a vast array of legacy roleplay frontends and specialized inference tools that adhere to the Pygmalion standard.

3. Dialogue and Greeting Normalization

We extract the "Greeting" from CharacterAI and map it directly to the Pygmalion char_greeting field. Furthermore, we reformat the "Definition" dialogue examples into the standard Pygmalion pattern. This normalization is critical because different model frontends interpret dialogue cues differently. By standardizing the output, we ensure that your character adopts their intended speaking style immediately, without "token leaking" cloud-specific artifacts or proprietary meta-tags.

4. Privacy and Data Sovereignty

Character development represents a significant creative investment. We honor this by performing all extractions and mapping locally. By running the conversion logic entirely in your browser's RAM, we ensure that your proprietary character definitions are never transmitted to our server or any third party. This provides a secure, private bridge for users who want to move their creations to a more self-sovereign, local-first roleplay ecosystem.

5. Identity Integrity and Legacy Compatibility

By outputting a standardized Pygmalion JSON, we ensure that your CharacterAI personas are compatible with the broadest possible range of AI tools. This conversion process isn't just about moving data; it's about future-proofing your digital characters and ensuring they remain accessible, editable, and compatible with the broader community standards, regardless of the evolving landscape of cloud-based AI services.