Browse / Agent tools
siphon-project/pipecat-siphon
A pipecat FrameSerializer for the siphon-rtp media WebSocket: binary L16 audio plus a JSON control envelope, with the negotiated wire rate honoured in both directions.
Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku.
What we checked
Does it run from the README?Yes. Running in 7:44 on a clean Linux box.The run
Tested Oct 27, 2026, rev 725f3f6.
Does it do what the README says?1 of 1 claims held up.Evidence
“The echo bot accepts a media WebSocket and echoes the caller's audio back”
Expected audio frames returned by the bot. Got audio frames in.
Which checks were skipped?3 checks skipped.Reasons
Skipped checks count as neither passes nor failures.
Examples: 3 skipped
- Integration harness: needs Docker (docker not installed in this guest); not run
- Quickstart with a real phone number: needs Docker Compose and three API keys plus a SIP account; not run
- agent_bot example with STT/LLM/TTS: needs three vendor API keys and the pipecat vendor extras; not run
Which setups did we try?Works with Haiku.Setups
Linux / Haiku: works, Oct 27, rev 725f3f6.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?No unexpected network or file activity found in these checksWhat we saw
No problems traced to this repository code in these checks; a short run cannot prove safety. 2 static matches retained as context.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Slow · 44 commits in 90 days · 35 merged PRs in 90 days · 0 open issues · 1 open PRsActivity
slow: last commit 0 days ago; 44 commits and 35 merged PRs in 90 days; 0 open issues, 1 open PRs; 0 of 12 recent threads got a maintainer reply; latest release 2026-10-27
Can I show this on my README?Copy the badge.Badge
The run
Oct 27 · rev 725f3f6Independent test, not endorsed by the project.