Skip to content
Kira LOCAL-FIRST
Stream integrations

Connect OBS avatar and chat by link; keep Stream Admin restricted.

OpenCohost should make stream integration simple without asking for dangerous credentials by default. Avatar and chat-link flows are the safe path; Stream Admin is MVP/testing only.

Plain-language version

There are two normal connections: OBS shows Kira visually, and the chat link lets Kira understand the room. Stream Admin is different: it can touch channel controls, so it stays restricted.

Safe stream connection map

1

OBS avatar

Visual state only: Kira changes image/state inside OBS.

2

Chat URL

Read the live chat from a YouTube/Twitch link.

3

OpenCohost

Shapes signals into safe context for Kira.

4

Stream Admin

Restricted MVP for privileged admin tests, not the default chat flow.

Quick path

  1. 1 For the avatar, enable OBS WebSocket, create an Image source named KiraAvatar, then set host, port, password, source, and scene in the avatar panel or config/avatar.yaml.
  2. 2 Use "Test connection" before going live. The avatar bridge updates OBS image sources when Kira changes state.
  3. 3 For chat, paste the YouTube or Twitch live/chat URL into the chat connection field. This path is link-only and should not request OAuth write permissions.
  4. 4 Keep Stream Admin disabled/restricted unless you are explicitly testing MVP admin flows with throwaway or approved credentials.

Featured features

OBS avatar states

Kira can expose idle, listening, thinking, speaking, and related states through OBS image-source updates.

Chat by URL

The streamer links a YouTube/Twitch live or chat URL; OpenCohost treats it as a chat source, not as channel administration.

Small-stream support

Stream Chico lowers thresholds/cooldowns so smaller rooms can still produce useful co-host moments.

Stream Admin MVP

OAuth/admin operations remain restricted, approval-gated, and test-mode oriented because write scopes are high risk.

Safe vs restricted

Safe default

OBS avatar and chat-by-link are the normal user path.

Restricted

OAuth/admin actions are test-mode only and require explicit approval.

Do not promise

Do not describe Stream Admin as general channel control until it is validated and released.

Limits to document clearly

OBS source requirements
OBS WebSocket v5 image updates require preserving OBS settings and setting both file and local_file on image sources.
Link-only chat is separate from admin
Pasting a chat link should not imply title editing, moderation, chat posting, or OAuth token storage.
Stream Admin is restricted
The MVP can expose YouTube admin capabilities in controlled tests, but public docs must frame it as restricted and approval-gated. Twitch admin remains future/placeholder unless separately validated.