> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/steves-helper-apps/chat-lite.md).

# Chat Lite

Social Stream Ninja Lite is a lightweight social activity overlay UI that can run standalone or embedded inside VDO.Ninja.

Current provider cards include YouTube, Twitch, Kick, and Social Stream WebSocket relay mode.

In plain terms: it lets VDO.Ninja show live chat messages from supported services inside the app, so you can keep chat on screen without opening a separate dashboard.

## Sources

Social Stream Ninja Lite can ingest from native provider cards (YouTube/Twitch/Kick) or from the Social Stream WebSocket relay source:

* `wss://io.socialstream.ninja` with a matching session ID

This relay mode can carry additional platform events through the same activity feed workflow.

## Links

* App: <https://vdo.ninja/chat-lite/>
* Activity/embed mode example: <https://vdo.ninja/chat-lite/index.html?view=activity&embed=1&session=demo>

## VDO.Ninja integration

You can enable Social Stream Ninja Lite integration in VDO.Ninja using URL parameters like:

* `&chatlite=1`
* `&chatlitebutton=1`
* `&chatlitesession=YOURSESSION`
* `&chatlitetts=all`
* `&chatlitetts=donations`

See the full parameter reference:

{% content-ref url="/pages/NBB1gJqxfZ1UxkygHLrF" %}
[\&chatlite](/advanced-settings/settings-parameters/and-chatlite.md)
{% endcontent-ref %}

## What it is good for

* Showing YouTube, Twitch, Kick, or SSN-fed activity directly inside a VDO.Ninja page
* Opening a local pop-out/activity view from the same browser profile
* Keeping chat visible for the director or host without needing the full Social Stream app
* Basic native browser TTS for incoming text messages, or donation/member-style events only

## Current limitations

* The built-in activity overlay is primarily a local browser feature. The copied overlay link is best treated as a same-browser pop-out, not a standalone OBS/browser-source overlay for another machine or browser profile.
* If you need a standalone overlay fed by Social Stream WebSockets, use the Social Stream theme overlays instead.
* Windows opened from the same VDO.Ninja page stay paired together. Standalone Chat Lite pages opened manually still use the default browser-level session behavior.
* This is not a full Social Stream Ninja replacement. Extension-only capture behavior, advanced TTS providers, and full emote-provider support should still use Social Stream Ninja directly.
* Incoming HTML is sanitized before display and before TTS text is built. Executable markup, JavaScript URLs, event handlers, style blocks, and iframe content are removed.

### Control-strip behavior

When enabled inside VDO.Ninja:

* Normal click toggles the Social Stream Ninja Lite activity overlay
* `SHIFT` + click opens Social Stream Ninja Lite setup
* `ALT` / `CTRL` + click toggles native browser TTS

The activity/embed view is intended as display-only output, so overlays do not auto-connect providers in the background.

### TTS notes

Native TTS uses the browser/system `speechSynthesis` voices. This can work on Android, iOS, and desktop browsers, but some browsers require a user gesture before speech can start. OBS Browser Source may not capture native system TTS audio; use the main Social Stream Ninja app if you need a richer OBS-focused TTS pipeline.

## Related

{% content-ref url="/pages/2pGU9TxBaXEy72kvDG33" %}
[Social Stream Ninja](/steves-helper-apps/social-stream-ninja.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vdo.ninja/steves-helper-apps/chat-lite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.