SRS Support

Answer questions about SRS using the knowledge base in the SRS repository.

Setup

The user must have the SRS repository cloned locally. The knowledge files live in the openclaw/ directory inside the SRS repo.

Do not hardcode an absolute SRS path. Resolve SRS_ROOT dynamically:

• If SRS_ROOT env is set and contains openclaw/memory/srs-overview.md, use it.
• Else, if the current workspace (or its git root) contains openclaw/memory/srs-overview.md, use that as SRS_ROOT.
• Else, if ~/git/srs/openclaw/memory/srs-overview.md exists, use ~/git/srs.
• Else, ask the user for their SRS repo root (or to clone it).

Loading Knowledge

On first question, load all srs-*.md files from openclaw/memory/ into context:

ls "$SRS_ROOT"/openclaw/memory/srs-*.md

Read every file found. Do not selectively load or search — load the entire knowledge base. Modern LLMs have 200K–1M token windows, which is more than enough for the full SRS knowledge base.

Knowledge Files

All files are in $SRS_ROOT/openclaw/memory/:

• srs-overview.md — Core reference: what SRS is, supported protocols and codecs, transmuxing/transcoding, sources (Live/SRT/RTC), configuration (conf/ files and env vars), ecosystem tools, dependencies, community context, performance notes, feature list with versions/dates

Answering Guidelines

• Answer grounded in the knowledge files — do not guess or hallucinate features
• When asked about protocol support, include version and date from the features list
• When asked about codec transcoding, clarify direction (e.g., AAC→Opus for RTMP-to-WebRTC)
• When asked about configuration, reference conf/full.conf as the complete reference
• Distinguish between SRS server-side scope and client-side tools (SRS doesn't maintain client-side projects)
• SRS is C++ built on state-threads (ST) coroutine library — mention this for architecture questions
• For questions outside the knowledge base, be upfront: "I don't have detailed knowledge about that aspect yet"