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

[BUG] Incomplete Text Pastes (in VSC)

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

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
desktop

Research direction

Reproduce the issue in the terminal-based Claude Code field in Visual Studio Code using the reported recording and paste steps, then compare with the in-app Codex extension and check whether the complete text remains available in Fluid’s history. The issue names no source files or tests, so first locate the app’s text-pasting entry point; done means long processed dictation pastes completely without missing chunks.

Written by the indexing model from the issue text.

Description

bug stale
Describe the bug

hi! i really love the wispr flow alternative you guys brought out. its just amazing, fast, intuitive, and most of the time really reliable.

there is one thing really bugging me and disturbing my workflows. i work mainly in visual studio code with a claude code and codex cli working there in multiple windows.

often times i monologue quite long into the mic, describing what i need to change in certain scenarios. i do that with fluid now. i can see the live transcript working just fine (wich is great) but then, 2-5 minutes into my monologue, i click the "end/send" button, fluid processes and then pastes the ai corrected text into the message field in vsc. BUT here comes the problem. for short texts, it works fine almost always. longer texts are sometimes completely cut off when pasted, either last 2 sentences or somewhat the earliest sentences and missing the whole rest.
Thats when i need to go into the app --> history and recover and manually copypaste the huge monologue (wich thankfully is there completely) and repaste it into vsc.
so it seems to understand and process just fine, even longer speeches, but pasting into vsc (especially claude code/terminal based, not in-app) often bugs out and leaves me with only traces. one observation: long paste of long text in claude code vsc cli is pasted as for example "[Pasted text #1 +6 lines]". (that was this text up until here).

I observed fluid pasting texts like this  "[Pasted text #1 +1 line]  [Pasted text #2 +3 lines] lorem ispum dolor etc etc etc words words words." Like splicing the processed big text into smaller chunks maybe? Maybe the processing of bigger texts or the paste acceptance of vsc bugs out here.
I had fewer to none issues in the same vsc window but in the "in-app-codex-extension" in vsc, same root. There the pastes of long processed fluid text were often a none issue.

i should mention i have raycast installed and i think it comes with a clipboard history tool, also, i have toggled clipboard pastes off in fluid, so the processed texts from fluid do not land in the clipboard history.
Wispr has had no such issues with the exact same setup, thats why im asking and hoping to contribute to fix it.

hope this helps and is fixed soon.
Best

Reproduction steps

click into the message field in vsc claude code cli (not the claude code in-app-extension, the terminal based one)
press shortcut to start recording (right cmd for me)
talk for more than 1 minute, lets say 3.
(see it working/processing properly in the live mini window)
press right-cmd again to stop recording
let it process, wait for the paste
--> see incomplete pasted text with huge chunks missing

Expected behavior

not chopped pasted texts

Actual behavior

like described above

App Version

1.6.10 beta

macOS Version

macOS 27

Architecture

Apple Silicon

Logs or crash report
Screenshots or screen recording

No response

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

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.