Writing surface
Email, notes, terminals, support tools, documents, and browser text fields each need different punctuation and rewrite rules.
fluidvoice write mode
Use the planner to translate FluidVoice source facts into a concrete setup, privacy, model, and workflow decision.
Workflow
Email, notes, terminals, support tools, documents, and browser text fields each need different punctuation and rewrite rules.
FluidVoice supports optional per-app prompt sets, so a plan can define style, cleanup, and rewriting boundaries by context.
Use sample outputs to decide where direct insertion is safe and where a preview/edit step should remain.
Decision matrix
| 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. |