Problem
Holaboss currently relies on keyboard / UI-driven interaction. This makes basic usage harder for non-technical users and adds friction for common workflows (e.g. triggering tasks, switching context).
Proposal
Add voice activation (wake word) support so users can trigger actions hands-free.
A reasonable first step would be:
- introduce a lightweight wake word listener (local, low CPU)
- add a speech-to-text (STT) layer and convert voice input into standard runtime requests
- reuse the existing request pipeline so voice input behaves the same as text input
- expose basic controls in the desktop UI (enable/disable voice, push-to-talk fallback)
Keep the implementation modular so STT can be swapped (local vs provider-based).
Alternatives considered
Keep interaction text-only and rely on UI improvements, but that doesn’t address hands-free usage or reduce friction for non-technical users.
Another option is push-to-talk only (no wake word), which is simpler but less seamless and doesn’t enable ambient / continuous interaction.
Impact
This mainly affects the desktop layer.
Problem
Holaboss currently relies on keyboard / UI-driven interaction. This makes basic usage harder for non-technical users and adds friction for common workflows (e.g. triggering tasks, switching context).
Proposal
Add voice activation (wake word) support so users can trigger actions hands-free.
A reasonable first step would be:
Keep the implementation modular so STT can be swapped (local vs provider-based).
Alternatives considered
Keep interaction text-only and rely on UI improvements, but that doesn’t address hands-free usage or reduce friction for non-technical users.
Another option is push-to-talk only (no wake word), which is simpler but less seamless and doesn’t enable ambient / continuous interaction.
Impact
This mainly affects the desktop layer.