ClawdTalk: Voice Calls for ClawdBots
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
Hey HN, We built ClawdTalk to let AI agents operate over live phone calls.Most agents today live in chat windows. The moment you try to use them over voice, things break: latency matters, interruptions happen, and the agent has to execute tools while the conversation is still live.ClawdTalk connects your Clawdbot to the phone network. The agent gets a real phone number. It can make and receive calls and run the same tools it uses in chat, but under real-time voice constraints.One of the reasons this is hard is infrastructure. Many voice stacks stitch together separate telephony, speech, and model APIs. Each hop adds latency, and people report 8–30 second round trips.We got it under ~3 seconds by running the full voice path ourselves. Telnyx (my employer) is a telecom carrier, and we run PSTN, STT, and TTS on our infrastructure. No middlemen.How it works: 1. Connect your OpenClaw agent to ClawdTalk 2. We provision a phone number 3. Inbound/outbound calls route directly to the agent 4. The agent executes tools mid-conversationLimitations: 1. Latency still depends on your LLM (we control voice, not inference) 2. US numbers only for now (international coming) 3. Not a new agent framework (OpenClaw only today)Demo number: +1-301-MYCLAWD (692-5293) (call to talk to the agent) Happy to answer questions about the architecture or telephony side.
HN · launched Feb 9, 2026 · 20 upvotes (top 31%) · 1 view
Niche: ai voice agents and platforms · 197 launches, 20 in the last 7 days ▲ +25% · Explore this niche →
Category and tags
- Horizontal
- Communication
- Developer
- AI-native
- Commercial product
Visit website ↗ Source listing ↗
More like this: all 197 launches in ai voice agents and platforms →
Could you build this?
Partial Connecting an LLM to telephony can be quickly prototyped using APIs like Twilio and LiveKit, but maintaining low-latency bidirectional streaming, interruptibility (barge-in), and mid-call tool execution requires specialized voice pipeline engineering. Pure vibe coding typically falls short on deterministic real-time audio orchestration and edge latency tuning.
What it would actually take: A viable voice-agent platform uses WebRTC/SIP backends (e.g., LiveKit, Daily, or Asterisk) integrated with low-latency Speech-to-Text (Deepgram), an LLM streaming bridge, and Text-to-Speech (Cartesia, ElevenLabs). The critical challenge is building a high-performance audio arbiter that handles Voice Activity Detection (VAD), instant barge-in cutoffs, and asynchronous tool invocation without causing perceptual pauses or audio stuttering. This requires expertise in real-time media streaming, jitter buffer management, and websocket concurrency.
Discussion
No comments on this launch.
Competitors
Other products that read as similar to this one : 318 launches clear the similarity bar, closest 8 shown.
Attention rank: #121 of 319 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 99 days after the earliest competitor.
- ClawCall · ph · 2026-10-08 · 70 upvotes · similarity 0.59
- Caspian · hn · 2026-08-21 · 6 upvotes · similarity 0.49
- Clawbernetes · hn · 2026-02-20 · 5 upvotes · similarity 0.49
- ClawMem · hn · 2026-03-22 · 5 upvotes · similarity 0.48
- Ava · hn · 2026-03-12 · 7 upvotes · similarity 0.47
- Clawther · ph · 2026-03-12 · 378 upvotes · similarity 0.47
- ClawShell, Process-Level Isolation for OpenClaw Credentials · hn · 2026-02-19 · 10 upvotes · similarity 0.45
- Clawe · hn · 2026-02-10 · 62 upvotes · similarity 0.45
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.