Repository navigation
docs: add ESP32 voice gadget integration boundary - #188
Open
raullenchai wants to merge 1 commit into
Open
raullenchai wants to merge 1 commit into
raullenchai wants to merge 1 commit into
Conversation
Document how an ESP32 voice gadget (esp32-thinks) can sit in front of OpenMuse through an OpenAI-compatible gateway. The page states what is tested and what is not: the firmware and its gateway are exercised on a Seeed SenseCAP Watcher, while the AG-UI bridge to OpenMuse remains a contract.
This branch has not been deployed
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
1 participant
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.
What changed
Adds
docs/ESP32-THINKS.mdand links it fromdocs/README.md.The page describes how an ESP32 voice gadget (esp32-thinks) can sit in front of OpenMuse. The device speaks OpenAI-compatible STT/chat/TTS; OpenMuse's agent transport is AG-UI, so a server-side gateway is required. The page documents that gateway contract, deployment/TLS requirements, and the security boundary.
Scope
Docs-only. No code, tests, or runtime changes. It follows the same integration-boundary pattern as
docs/OPENBOT-INTEGRATION.md.Verification
Notes
Happy to move this under a different docs path or turn it into an
examples/entry if you prefer.