Skip to content

Phase A: integrate voice web UI into CLI app#213

Draft
eanzhao wants to merge 2 commits intodevfrom
feat/2026-04-15_voice-web-ui-phase-a
Draft

Phase A: integrate voice web UI into CLI app#213
eanzhao wants to merge 2 commits intodevfrom
feat/2026-04-15_voice-web-ui-phase-a

Conversation

@eanzhao
Copy link
Copy Markdown
Contributor

@eanzhao eanzhao commented Apr 15, 2026

Summary

This draft PR implements the Phase A scope of #205 only.

It integrates the browser-based voice UI into the existing CLI web app so aevatar voice --agent <actorId> can ensure the local UI host is running, point it at the selected backend, and open /voice?agent=<actorId>.

What Changed

  • added a new aevatar voice CLI entrypoint for launching the Phase A voice page
  • introduced a shared local app host launcher so chat and voice use the same probe/start/proxy-target flow
  • added a dedicated /voice React page with microphone capture, websocket session handling, playout metrics, and provider/sample-rate controls
  • added AudioWorklet encoder/decoder assets adapted from ChronoAIProject/voice-presence
  • added websocket proxy support in the local CLI host and mapped /ws/voice/{actorId} in both workflow and mainnet hosts
  • updated CLI README and added tests for the new command and websocket proxy path

Why

Issue #205 Phase A requires a browser voice UI first, with the CLI acting as the entrypoint. The Phase A goal is to reuse the existing web UI shell instead of introducing a parallel standalone host, while keeping the voice websocket path available from the backend hosts.

User / Developer Impact

  • users can now run aevatar voice --agent <actorId> to open the browser voice UI directly
  • the local CLI app can proxy /ws/voice/{actorId} traffic to the configured backend
  • backend hosts now expose the voice websocket route needed by the browser client
  • this PR intentionally does not include later phases such as background daemonization or non-browser voice clients

Validation

  • npm run build in tools/Aevatar.Tools.Cli/Frontend
  • dotnet test test/Aevatar.Tools.Cli.Tests/Aevatar.Tools.Cli.Tests.csproj --nologo -m:1 -p:UseSharedCompilation=false --filter 'FullyQualifiedName~VoiceCommandTests'
  • dotnet test test/Aevatar.Tools.Cli.Tests/Aevatar.Tools.Cli.Tests.csproj --nologo -m:1 -p:UseSharedCompilation=false --filter 'FullyQualifiedName~RootCommandFactoryTests'
  • dotnet test test/Aevatar.Tools.Cli.Tests/Aevatar.Tools.Cli.Tests.csproj --nologo -m:1 -p:UseSharedCompilation=false --filter 'FullyQualifiedName~AppPlaygroundHostTests'
  • dotnet build src/workflow/Aevatar.Workflow.Host.Api/Aevatar.Workflow.Host.Api.csproj --nologo -m:1 -p:UseSharedCompilation=false
  • dotnet build src/Aevatar.Mainnet.Host.Api/Aevatar.Mainnet.Host.Api.csproj --nologo -m:1 -p:UseSharedCompilation=false

Notes

  • a pre-existing unrelated test in WorkflowStudioBranchCoverageTests still fails in the full Aevatar.Tools.Cli.Tests project run; it is outside this diff and was not changed here
  • reference implementation source: ChronoAIProject/voice-presence

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.86%. Comparing base (82c0e8b) to head (5bb1fba).

@@            Coverage Diff             @@
##              dev     #213      +/-   ##
==========================================
- Coverage   81.87%   81.86%   -0.02%     
==========================================
  Files         786      786              
  Lines       50533    50533              
  Branches     6642     6642              
==========================================
- Hits        41376    41370       -6     
- Misses       6317     6323       +6     
  Partials     2840     2840              
Flag Coverage Δ
ci 81.86% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant