feat(teleop): route operator audio to Go2 - #3268
Draft
ruthwikdasyam wants to merge 4 commits into
Draft
Conversation
# Conflicts: # dimos/teleop/hosted/README.md # dimos/teleop/hosted/blueprints/cloudflare.py
Codecov Report❌ Patch coverage is @@ Coverage Diff @@
## main #3268 +/- ##
==========================================
+ Coverage 74.96% 75.21% +0.24%
==========================================
Files 1117 1130 +13
Lines 106875 108585 +1710
Branches 9699 9998 +299
==========================================
+ Hits 80123 81670 +1547
- Misses 23945 24067 +122
- Partials 2807 2848 +41
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 108 files with indirect coverage changes 🚀 New features to boost your workflow:
|
ruthwikdasyam
commented
Jul 29, 2026
ruthwikdasyam
left a comment
Contributor
Author
There was a problem hiding this comment.
Hermes Agent Review
Found 1 issue worth fixing before marking this ready. CI is green, and the audio transport/blueprint wiring otherwise looks coherent.
⚠️ Warning
dimos/teleop/hosted/go2_audio_bridge.py:170— failed uploads clear_megaphone_activewithout sendingEXIT_MEGAPHONE, so the firmware can be left in megaphone mode after a partial upload failure.
✅ Looks good
- Broker provider singleton config no longer forks on audio-only options.
- Operator-audio transport is subscribe-only and starts the shared provider lazily.
- Tests cover config override, speaker auto-disable, resampling/mixing, queue drop policy, batching, and response-code handling.
Note: I reviewed via GitHub API/diff because the local clone checkout hit filesystem timeout on this large repo; all GitHub checks are passing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution path
Problem
Hosted Go2 teleoperation receives video and control data from the operator, but it does not route the operator's microphone audio to the robot speaker. The Go2 Air also lacks speaker hardware, so the integration must avoid repeatedly calling unsupported firmware APIs.
Solution
auto,enabled, anddisabledspeaker modes so deployments can explicitly handle Go2 Pro and Go2 Air hardware.How to Test
dimos run teleop-hosted-go2-transport -o go2audiobridgemodule.speaker=enabledAI assistance
OpenCode with GPT-5.6 was used to review the implementation, address lifecycle cleanup, and verify the change. The author reviewed and understands the resulting code.
Checklist