FluentView evidence
Hands-free Windows use

Hands-free control works better as a layered system.

Use voice for intent, optional gaze for context, and the lowest-cost fallback for correction.

Read the short answer
Short answer

Can Fluent provide hands-free computer control?

Fluent is being built to reduce keyboard and mouse use through voice requests, optional gaze context, and Windows automation. A spoken command can start a task and voice can cancel, but the current preview is not yet a complete no-hands system. Setup, provider credentials, some confirmation paths, gaze recovery, and reliable installed workflows still require keyboard, pointer, or developer assistance.

Build around the signal that costs the least

Hands-free does not need to mean voice-only. Ability, fatigue, pain, speech, privacy, noise, and concentration can change across a day. A resilient setup lets the user alternate between voice, text, keyboard, pointer, switch, head tracking, or gaze without losing the task state.

Fluent currently implements voice, typed fallback, and optional gaze context. Its design goal is one command surface where those inputs contribute to the same request instead of forcing the user into isolated modes.

  • Intent layer: voice or text describes the outcome.
  • Target layer: an explicit name, current focus, or optional gaze identifies the object.
  • Correction layer: editable text and clarification repair recognition or target errors.
  • Consent layer: a deliberate input approves or rejects consequential work.
  • Recovery layer: stop, cancel, undo, or retry remains close to the active task.

A practical Fluent preview workflow

Start with a low-risk task in a familiar app. Arm the microphone with the wake phrase, microphone control, or push-to-talk shortcut. State one observable outcome. Watch the action trace and use cancel if the route diverges. Keep typed input available for private details or precise correction.

If gaze is enabled, use it only to disambiguate a visible target. Name the target aloud when practical. Avoid relying on gaze for activation or as the only route through the interface.

Evaluate the whole loop, not the demo moment

A successful spoken command is only one part of hands-free use. The real test includes installation, microphone and camera permissions, provider setup, wake and sleep behavior, correction, target ambiguity, cancellation, failure recovery, updates, and uninstall.

Measure effort as well as task completion. Count how often another person must help, how often the user must fall back to a costly input, and whether stop behavior is fast and understandable.

  • Can the user reach the first useful task without developer tools?
  • Can every active run be understood and stopped?
  • Can a speech or target error be corrected without restarting everything?
  • Does the baseline still work with the camera off?
  • Can the user inspect and remove stored settings, memory, logs, and credentials?

When to involve an accessibility specialist

People with complex or changing access needs may benefit from an assistive technology professional who can compare voice access, switch access, head tracking, eye tracking, ergonomic hardware, and operating-system tools. Fluent is software documentation, not medical advice.

The best setup is the one that remains reliable on a difficult day, not the one that looks most hands-free in a short demo.

Direct answers

Questions people ask before trying Fluent.

Can I use Fluent with no keyboard or mouse at all?
Not reliably today. The preview can run voice-first tasks, but setup, recovery, and some confirmation paths still need hardening before Fluent can claim complete no-hands use.
Does hands-free control require gaze?
No. Voice and typed fallback are the baseline. Gaze is an optional target signal and should not gate the product.
Can I stop Fluent by voice?
The documented input contract recognizes short cancel phrases and the interface has cancellation controls. Stop latency and installed reliability are explicit research scorecard measurements.
Is Fluent an assistive technology replacement?
No universal replacement claim is appropriate. Fluent is a preview layer that should be compared with built-in Windows tools and each user's established access setup.
Check the record

Sources and product disclosures.

  1. Fluent research methodHands-limited goal, current gaps, and beta outcome gates.
  2. Fluent privacy and safety disclosureWake, cancel, typed fallback, and gaze behavior.
  3. Fluent guide libraryCurrent Windows preview explanations.
Written and maintained byJason Matthew Suhari

Creator of Fluent. Product claims are reviewed against the current implementation and published limits.

GitHub profile
Inspect before you trust

Judge Fluent by the evidence.

Read the method, inspect the limits, and evaluate the current preview against published thresholds.

Read the research method