FFractalTerms

Fractal Voice support

Build with confidence.

Setup guidance and troubleshooting for the Fractal Voice macOS app, Fractal CLI, local speech models, and live execution graphs.

Support information updated July 28, 2026

System requirements

Apple Silicon Mac running macOS 15 or later, with about 3 GB available for local voice models.

Required accounts

A Fractal Society account, GitHub CLI authentication, and at least one supported coding-agent CLI.

Voice shortcut

Press Option–Space to start speaking. The conversation remains active through confirmation and naming.

Stop a build

Use the app’s Stop button or run fractal stop. Use fractal stop --all for every build.

First-launch setup

  • Allow microphone access when macOS asks.
  • Let the verified offline voice models finish downloading.
  • Create or connect your Fractal Society account.
  • Install and sign in to Codex, Claude, Cursor, or another supported agent.
  • Install GitHub CLI and confirm that gh auth status succeeds.
  • Complete the readiness check, then press Option–Space.

Common fixes

The shortcut does not respond

Open Fractal Voice from the menu bar, choose Retry Option–Space Shortcut, and verify another app is not using the same shortcut. Fractal Voice does not normally require Accessibility permission for its registered hot key.

The voice model is stuck

Keep the Mac connected to power and the internet, reopen Welcome, and choose Retry. Downloads resume and every file must pass its SHA-256 check before use.

Account verification fails

Run fractal login --status. If it fails, run fractal login, approve the browser code, and return to the app’s setup check.

A build appears stalled

Open the activity log and live execution graph. Stop the build safely, then resume the project from its preserved execution graph after correcting the reported dependency or agent issue.

Contact support

Join the Fractal Society Discord for technical help and community support. Include the app version, macOS version, and a description of the problem. Share only relevant, redacted activity-log lines. Never post passwords, API keys, access tokens, private signing keys, or confidential source code.