Emo.Studio

Emo.Studio is the maker surface for the SDK: a creator starts with a sentence, gets an interview-assisted character, and can then edit persona, temperament, lore, emotion dimensions, memories, actions, models, and versions directly.

That makes Emo.Studio a vibe-coding-first way to build agents. The product keeps the creative loop fast for nontechnical creators while still exposing the implementation details engineers need to ship the same character into real apps.

The important pattern is one emotional core across many surfaces. A character can be tested through text, iMessage, WhatsApp, video/reel descriptions, voice notes, game events, and world events while keeping durable relationship memory for each person it meets.

API access turns that same emotional core into infrastructure. External runtimes can send structured context events, receive selected actions, and use signed webhooks so a game can let an agent choose real abilities without letting the model mutate the world directly.

The product story should make implementation feel obvious: create an agent, add its action menu, publish the API surface, mint an emo key, send events, register action webhooks, and report results back to the studio.

That documentation path is what makes videogame use cases legible. A team building with Unity, Unreal, or a browser world should be able to treat Emo.Studio as the authoring, simulation, deployment, and emotional-memory layer for multimodal NPCs.