Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[✨ FEATURE] Add voice command triggers for punctuation and editing during dictation

Open
#406 3 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #476 by @Kayaba-Attribution — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
swift
Domain
desktop

Research direction

No files, tests, or entry points are named in the issue. Start by reviewing linked pull request #476 and locating where dictation output is handled. Clarify which commands and pause behavior are in scope; done should mean the agreed commands work during dictation and longer pauses do not produce unwanted filler words.

Written by the indexing model from the issue text.

Description

enhancement

FluidVoice has strong local ASR performance and optional Fluid Intelligence post-processing for smart formatting. However, it currently lacks support for common voice commands during dictation.

Users often expect to be able to say things like:

  • “new paragraph” or “new line”
  • “full stop”, “comma”, “question mark”
  • “backspace” or “delete that”
  • “scratch last sentence” or “scratch that”

…and have the app respond in real time.

Requested feature:
Add optional support for voice command / trigger phrase recognition during dictation. This could include:

  • Common punctuation and formatting commands
  • Basic editing commands (“scratch that”, “delete last word”, etc.)
  • Better handling of longer pauses so the model doesn’t hallucinate filler words
  • Configurable or extensible trigger phrases

These features would make natural dictation significantly smoother and more usable.

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 13h
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.