Thanks for the complement.
Yeah, so as the project's readme already explains, this is motivated/influenced by use cases for users who wants lightweight setup for ther openclaw deployment(local VM/VPC) without any complex/heavy setup(TTS/STT) on their openclaw server.
As the project grows and the light-weight path is stable, media-stream support could definitely be a logical next step.
About barge-in/interruptions, we have partial support. You can look at the codebase and/or the documentations we have for architecture, research as well as what's being planned to address etc: https://github.com/ranacseruet/clawphone/tree/main/docs . Feel free to engage on the repo through issue tracking/suggestions etc.
About barge-in/interruptions, we have partial support. You can look at the codebase and/or the documentations we have for architecture, research as well as what's being planned to address etc: https://github.com/ranacseruet/clawphone/tree/main/docs . Feel free to engage on the repo through issue tracking/suggestions etc.
Hope that helps. Thanks!