feat(voice): wire flute-gateway → OmniVoice (default provider + URL/token) - #1885
Conversation
…oken) OmniVoice is activated + healthy on the 4090 (:8002, cuda:0); both TTS smokes pass (direct /synthesize + the flute-gateway OmniVoiceProvider against the live server). This persists the deployed wiring so flute-gateway actually uses it. Root docker-compose.yml flute-gateway environment (source of truth; overlays regenerated via `make compose-split`): - DEFAULT_VOICE_PROVIDER default vibevoice → omnivoice (overridable back). - + OMNIVOICE_URL (default host.docker.internal:8002), OMNIVOICE_TOKEN, OMNIVOICE_TIMEOUT_SEC — previously absent, so a deployed flute-gateway hit its own container loopback instead of OmniVoice. Joint-deploy note (in the handoff): bring OmniVoice up with OMNIVOICE_BIND=0.0.0.0 + OMNIVOICE_TOKEN so the flute-gateway container can reach it. Known Road: compose:handoff:flute-omnivoice-wiring-2026-06-26.md (operator-approved). vibevoice is z890's lane — default flip is env-reversible, flagged for awareness. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Docker Hardening ValidationHardening Validation ReportValidated: Fri Jun 26 10:13:49 UTC 2026Services CheckedPMOVES.AI Docker Hardening Validation[INFO] Checking: pmoves/docker-compose.hardened.yml [INFO] Validating: hi-rag-gateway-v2 [INFO] Validating: extract-worker [INFO] Validating: langextract [INFO] Validating: presign [INFO] Validating: render-webhook [INFO] Validating: retrieval-eval [INFO] Validating: pdf-ingest [INFO] Validating: jellyfin-bridge [INFO] Validating: invidious-companion-proxy [INFO] Validating: ffmpeg-whisper [INFO] Validating: media-video [INFO] Validating: media-audio [INFO] Validating: hi-rag-gateway-v2-gpu [INFO] Validating: hi-rag-gateway-gpu [INFO] Validating: deepresearch [INFO] Validating: supaserch [INFO] Validating: publisher-discord [INFO] Validating: mesh-agent [INFO] Validating: nats-echo-req [INFO] Validating: nats-echo-res [INFO] Validating: comfy-watcher [INFO] Validating: grayjay-plugin-host [INFO] Validating: agent-zero [INFO] Validating: archon [INFO] Validating: channel-monitor [INFO] Validating: pmoves-yt [INFO] Validating: notebook-sync [INFO] Validating: supabase_service_role_key [INFO] Validating: supabase_jwt_secret ====================================== |
|
Warning Review limit reached
More reviews will be available in 28 minutes and 58 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdated ChangesOmniVoice gateway wiring
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b94c5f5b7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pmoves/docs/handoffs/flute-omnivoice-wiring-2026-06-26.md`:
- Around line 1-50: This handoff note is missing the required metadata block
fields, so update the document to include graphiti_mark, branch, pr_numbers,
scope, risks, next_actions, chit_artifact_path, and agent_signature in the
handoff section. Place the metadata near the top-level handoff content in the
same file and keep it consistent with the existing wiring note context so the
contract for runtime-wiring handoffs is satisfied.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 44d50b69-0f3e-4798-b522-830c6e8ac6dd
📒 Files selected for processing (3)
pmoves/docker-compose.media.ymlpmoves/docker-compose.ymlpmoves/docs/handoffs/flute-omnivoice-wiring-2026-06-26.md
… metadata
Addresses review:
- Codex P2: the compose ${DEFAULT_VOICE_PROVIDER:-omnivoice} fallback never fired
because env.shared (seeded from env.shared.example) sets the var explicitly.
Flip env.shared.example:291 vibevoice→omnivoice so the default is actually
effective on the Makefile --env-file bring-up path. Env-reversible; z890 flagged.
- CodeRabbit: add the required handoff metadata block (graphiti_mark, branch,
pr_numbers, scope, risks, next_actions, chit_artifact_path, agent_signature).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Docker Hardening ValidationHardening Validation ReportValidated: Fri Jun 26 10:44:53 UTC 2026Services CheckedPMOVES.AI Docker Hardening Validation[INFO] Checking: pmoves/docker-compose.hardened.yml [INFO] Validating: hi-rag-gateway-v2 [INFO] Validating: extract-worker [INFO] Validating: langextract [INFO] Validating: presign [INFO] Validating: render-webhook [INFO] Validating: retrieval-eval [INFO] Validating: pdf-ingest [INFO] Validating: jellyfin-bridge [INFO] Validating: invidious-companion-proxy [INFO] Validating: ffmpeg-whisper [INFO] Validating: media-video [INFO] Validating: media-audio [INFO] Validating: hi-rag-gateway-v2-gpu [INFO] Validating: hi-rag-gateway-gpu [INFO] Validating: deepresearch [INFO] Validating: supaserch [INFO] Validating: publisher-discord [INFO] Validating: mesh-agent [INFO] Validating: nats-echo-req [INFO] Validating: nats-echo-res [INFO] Validating: comfy-watcher [INFO] Validating: grayjay-plugin-host [INFO] Validating: agent-zero [INFO] Validating: archon [INFO] Validating: channel-monitor [INFO] Validating: pmoves-yt [INFO] Validating: notebook-sync [INFO] Validating: supabase_service_role_key [INFO] Validating: supabase_jwt_secret ====================================== |
1 participant
Summary
pmoves-omnivoice:latest, cuda:0,:8002); persists the flute-gateway → OmniVoice deployed wiring.docker-compose.ymlflute-gateway env (source of truth; overlays regenerated viamake compose-split):DEFAULT_VOICE_PROVIDERdefaultvibevoice→omnivoice(overridable back via env).OMNIVOICE_URL(defaulthost.docker.internal:8002),OMNIVOICE_TOKEN,OMNIVOICE_TIMEOUT_SEC— previously absent, so a deployed flute-gateway would hit its own container loopback instead of OmniVoice.docs/handoffs/flute-omnivoice-wiring-2026-06-26.md(decision + joint-deploy note + lane flag).Testing
Required Checks
compose-split) — not hand-editedReview Coordination
compose:handoff:flute-omnivoice-wiring-2026-06-26.md(operator-approved; recorded to known-roads.jsonl; grant removed after)Follow-up Tasks
OMNIVOICE_BIND=0.0.0.0+ setOMNIVOICE_TOKEN(a 127.0.0.1 bind is unreachable from the flute-gateway container). AddOMNIVOICE_TOKENto the secrets pipeline.Reviewer Notes
OmniVoice ran host-only (
127.0.0.1) for the 4090 validation; the provider smoke ran from the host, so no tailnet exposure.media.ymlis generated from the root compose — the edit is in the root, overlays regenerated.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation