Studio

Build characters, scenarios, events, triggers, and the full scripting layer that drives Voxta conversations.

Studio is where you author the AI side of Voxta — the characters, the scenarios they live in, the actions they take, the events that drive a story, and the JavaScript that ties it all together.

If you've used a chat character platform before, think of Studio as the authoring half of Voxta. The chat interface is for talking with characters; Studio is for building them.

Building blocks

Scenarios

The setting and rules a chat runs under. Defines roles, actions, events, contexts.

Characters

The personality, voice, and profile of an AI persona.

Memory books

Long-form lore the AI can pull from when relevant.

Events

Automatic story moments triggered by time, message count, or flags.

App triggers

Drive the host app — UI, avatar, audio, VAM scene — from a scenario.

Actions

Inference-driven choices the AI can take (smile, sit down, play sound).

Contexts

Conditional sentences injected into the prompt to ground the AI in scene state.

Flags

State bits that filter actions and contexts, settable from scripts and actions.

Messages

The full taxonomy of message types — events, notes, secrets, instructions, story.

Templates

Scriban templating for dynamic strings in characters, scenarios, and prompts.

Packages

Bundle resources for sharing — export, import, distribute.

Scripting

JavaScript event handlers that make scenarios react and adapt.

How the pieces fit

A typical complex chat looks like:

Scenario
  ├─ assigns Characters to Roles
  ├─ defines Events, Actions, Contexts
  ├─ pulls in Memory Books for additional lore
  ├─ uses Flags to track state
  ├─ runs Scripts on init / messages / events
  └─ fires App Triggers to drive the host app (Voxta Talk, VAM, Voxy, custom)

You don't need all of it. A simple "talk to a character" chat just needs a Character. Scenarios start mattering once you want narrative structure, multiple characters, or app-side effects.