Describe the bug
Command Mode can look frozen even though FluidVoice is still running. In my case, the model successfully
returned a tool call, but the app then spent a long time inside terminal execution for a broad filesystem
search. The UI becomes unresponsive-looking while the command is still in progress, especially when the command
is broad enough to scan large parts of the home directory or touch slower locations.
To Reproduce
Steps to reproduce the behavior:
- Open FluidVoice Command Mode.
- Ask it to search broadly through folders, for example “look through my vaults” or something similarly recursive.
- Let it run a command that searches a wide part of the filesystem.
- See the app appear frozen while the terminal command is still running.
Expected behavior
The app should remain responsive, show clear progress, or avoid blocking the UI while terminal execution is in progress.
Environment:
- macOS Version: Tahoe 26.5
- App Version: [1.6.0]
- Architecture: Apple Silicon
Additional context
This does not appear to be an LLM failure. The model returns the tool call correctly. The stall happens during command execution, and broad searches make it much more obvious.
Crash Logs
No crash. The app stays alive.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app should remain responsive, show clear progress, or avoid blocking the UI while terminal execution is in progress.
Environment:
Additional context
This does not appear to be an LLM failure. The model returns the tool call correctly. The stall happens during command execution, and broad searches make it much more obvious.
Crash Logs
No crash. The app stays alive.