Session inputs (draft — not shipped)
Phase 1 already supports opaquemetadata → LiveKit session_context → voice-agent
injection (## Session context block + <session_context:path> placeholders).
This page describes the optional Cockpit layer to declare expected keys on a
scenario version.
Goals
- Authors see which bootstrap keys a scenario expects
- Prompt editor can insert
<session_context:dog.name>from a picker - Live / test runs can fill a form instead of raw JSON
- Soft validation (warn when required keys are missing) without breaking clients
Proposed schema (scenario version content)
key is a dotted path into the client metadata object (same resolution as
placeholders today).
Platform work (when prioritized)
- platform-api — persist
session_inputson scenario versions; optional soft check onPOST /v1/public/session - platform-spa — editor UI + Live form for test values
- voice-agent — already injects placeholders; no change required for lookup
- docs / SDK — point authors at declared inputs when present
metadata map remains valid. Clients (e.g. Lupi)
document their contract in scenario prompts.