What to map
Apps, shortcuts, system actions, confirmation steps, and the hotkey behavior that opens and submits Command Mode.
fluidvoice command mode
Voice commands feel powerful only when the guardrails are written down.
Use the planner to translate FluidVoice source facts into a concrete setup, privacy, model, and workflow decision.
Unofficial boundary
GPL-3.0 source
v1.6.1 release noted
Workflow
What this page helps decide.
Why it matters
Voice-triggered actions can affect windows, apps, and automation. A plan prevents accidental commands becoming muscle memory.
Planner output
The paid export separates safe commands, confirmation-required commands, blocked commands, and review steps.
Decision matrix
What the planner checks before daily use.
| Area | Question | Planner output |
|---|---|---|
| Voice engine | Does the work need zero-download setup, low latency, multilingual support, Intel compatibility, or high accuracy? | Model recommendation with setup notes and disk expectations. |
| Permissions | Can users explain microphone, accessibility, Apple Events, and speech recognition access before approving prompts? | Onboarding checklist and risk labels. |
| Mode policy | Where should Command Mode, Write Mode, per-app prompts, and direct insertion be allowed? | Mode map with safe, review, and blocked zones. |
| Privacy | Which opt-ins are allowed: cloud enhancement, Fluid Intelligence, analytics, beta builds, local history, and exports? | Privacy boundary and data-retention notes. |