CharacterAI to Backyard AI Migration

The transition from **CharacterAI (c.ai)** to **Backyard AI** (formerly Faraday) represents a significant shift from a managed cloud service to a self-sovereign local roleplay environment. While CharacterAI hides much of its character logic behind proprietary algorithms, Backyard AI gives the user granular control over the character's behavior and the underlying model's parameters. Our tool bridges this gap by performing a technical "decompilation" of the character's personality.

1. Analyzing the Definition Monolith

CharacterAI primarily uses a single "Definition (Advanced)" field to store the character's soul. This field often contains a mixture of W-style descriptions, example dialogues, and context cues. Backyard AI, however, thrives when this data is segregated into distinct fields like personality, scenario, and mes_example.

2. Working with Local Token Limits

CharacterAI supports very large definitions, but local models running in applications like Backyard AI are often more sensitive to context window limits. The converter does not shorten or summarize your character, so long definitions are carried over in full; trim them yourself if your Backyard AI setup has a length limit. This ensures that your character remains coherent and detailed without overwhelming the local LLM's memory, leading to faster inference speeds and more relevant responses.

3. Dialogue and Greeting Fields

Backyard AI utilizes a specific dialogue format to maintain immersion. We extract the "Greeting" from CharacterAI and map it to the first_mes field. This prevents the character from being "confused" by cloud-specific formatting and ensures they immediately adopt their intended speaking style within the Backyard interface.

4. Privacy and the "Zero-Server" Advantage

Moving characters from a cloud platform often involves sharing intimate creative work. We honor this by keeping the entire migration process local. 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 transition their creative assets to a more private, local-first roleplay experience.

5. Identity and Metadata Fields

The name, description, personality, scenario, first message and example dialogue are written to the Backyard AI JSON; tags and version metadata are not generated. This ensures that your character is not just a raw text file, but a "Ready-to-Play" digital asset that integrates perfectly with Backyard AI's library management and model orchestration features.