Updating the previous evaluation — the roadmap has changed since the April assessment.

Cycle 314 (Learning Management Modernization, created 2026-05-02, status: in-progress) now explicitly plans voice input as a for the new student hub at and . A voice input button stub already exists in the parent chat input area () but is non-functional — Cycle 314 will deliver the real implementation.

The parent chat UI has a placeholder voice button (toggles recording state but has no MediaRecorder/getUserMedia integration). No STT/TTS services are integrated yet. Cycle 314's scope includes building the actual audio pipeline.

This is covered by Cycle 314: Learning Management Modernization (). Changing status to .

_— Automated evaluation by Claude Code against _

Thanks for the suggestion! Voice chat is interesting but has 1 vote, below our 3+ threshold for active evaluation.

bidirectional voice/audio is explicitly out of scope for the current chat architecture. Cycle 87 (parent chat polish) chose SSE as the streaming transport precisely because WebSocket is only required for realtime bidirectional audio. Cycle 170 (parent UX improvements) references voice input as a composer capability, not an active item. The active investment areas are Wave 6 (First Users — reliability, auth, chat, Cerebe productization) and Wave 7 (The Learning Engine — adaptive mastery-based tutoring); neither currently prioritizes voice.

Needs more signal. We will revisit at higher vote counts or if the product strategy shifts toward multimodal interaction. Leaving status as so others can vote.

_— Automated evaluation by Claude Code against _