Gateway realtime voice

Klykable now runs realtime voice through Gateway while keeping URL context, memory, tools, and outcomes in Klykable.

Klykable is being designed around URL-native realtime agent sessions.

Gateway direction

The product voice path uses Gateway realtime while Klykable owns the agent surface, session orchestration, memory, and tool policy.

Honest status

The current public shell can run realtime voice where a surface enables it. The proof focuses on URL-addressable sessions, Live Brief updates, transcripts, durable state, and server-authorized tools.

Runtime boundary

Voice should enhance a prepared session. It should not replace the URL, policy, memory, or outcome model that makes the session useful.