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

"Learn from my corrections" doesn't work in terminal apps

Open
  • Is something wrong?
#1,032 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing how correction tracking reads the edited text field and how corrections are saved to the Custom Dictionary; the issue does not name files or tests. Clarify with the maintainer whether the goal is terminal support or a manual fallback, then define done as correctly saving the intended spelling without recording a false pair.

Written by the indexing model from the issue text.

Description

help wanted keep-open

In Terminal.app (e.g. typing into Claude Code or a shell prompt), correcting a dictated word isn't learned.

Repro: I dictated "Torrisi", it came out as "Teresi", and I retyped it as "Torrisi" right away. No correction was recorded. Instead, a false pair was stored (Kolja → yeah), probably because the terminal's text area doesn't map cleanly to the inserted range.

Suggestion: either support terminal apps, or add a quick fallback, e.g. a "Fix last dictated word" shortcut / menu-bar action that opens a small field to type the correct spelling and saves it to the Custom Dictionary. That would also help in any other app where correction tracking can't read the text field.

FluidVoice 1.6.9, macOS 27.0 (Apple Silicon).

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

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.