{"author":"fallais","children":[{"author":"fallais","children":[],"created_at":"2026-07-25T12:51:49.000Z","created_at_i":1784983909,"id":49047202,"options":[],"parent_id":49047201,"points":null,"story_id":49047201,"text":"I got tired of running Python servers for voice agents, so I started porting Pipecat over. The design is Pipecat&#x27;s, frames and processors and all, I just wanted it as one binary with real concurrency instead of a GIL. The models sit behind APIs or in ONNX anyway, so the server side is mostly audio plumbing and WebRTC.<p>Pion for WebRTC, no Daily and no hosted transport. RTVI over the data channel so existing clients work. STT&#x2F;LLM&#x2F;TTS are swappable interfaces. Silero for VAD, Smart Turn v3 for end of turn, both local ONNX, so barge-in works.<p>Early, and I will break the API. Needs cgo (libsoxr, plus libopus if you want speech to sound decent). Dockerfile has everything if you&#x27;d rather not deal with that.<p>Would like opinions on the package layout, some of it is still shaped like the Python it came from.<p><a href=\"https:&#x2F;&#x2F;github.com&#x2F;gojargo&#x2F;jargo\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;gojargo&#x2F;jargo</a>","title":null,"type":"comment","url":null},{"author":"dzonga","children":[],"created_at":"2026-07-25T16:29:03.000Z","created_at_i":1784996943,"id":49048973,"options":[],"parent_id":49047201,"points":null,"story_id":49047201,"text":"dope work.","title":null,"type":"comment","url":null}],"created_at":"2026-07-25T12:51:49.000Z","created_at_i":1784983909,"id":49047201,"options":[],"parent_id":null,"points":10,"story_id":49047201,"text":null,"title":"Show HN: Jargo, a Go port of Pipecat for building realtime voice agents","type":"story","url":"https://github.com/gojargo/jargo"}
