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

[✨ FEATURE] In macOS, put all models under FluidVoice-specific cache folder

Open
#289 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
macos, swift
Domain
desktop

Research direction

Find the model-download and cache-location entry points, then trace where cohere-transcribe-03-2026-CoreML-6bit and WhisperModels are stored. Check how macOS cache directories are selected. Done means FluidVoice's model folders are saved under ~/Library/Caches/com.FluidApp.app/models rather than directly under ~/Library/Caches.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem?
The problem is that on macOS FluidVoice downloads models into ~/Library/Caches, at the top-level. This makes it harder for me to track huge files that are downloaded on a per-app basis (as I do for other AI apps).

But maybe this is intentional and choosing such a saved location allows for the sharing of model files with apps other than FluidVoice?

Describe the solution you'd like
Download folders such as cohere-transcribe-03-2026-CoreML-6bit and WhisperModels under ~/Library/Caches/com.FluidApp.app/models

Describe alternatives you've considered
I can manually monitor what folders are created by FluidVoice under ~/Library/Caches and keep a growing list of these folders in a script.

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.