Repository navigation
feat(desktop): remove filler words in the native editor - #2961
Open
thesammykins wants to merge 2 commits into
Open
thesammykins wants to merge 2 commits into
thesammykins wants to merge 2 commits into
Conversation
Contributor
|
@thesammykins is attempting to deploy a commit to the Cap Software Inc Team on Vercel. A member of the Team first needs to authorize it. |
Generate local word captions when needed, then apply reversible source-timed cuts with existing ripple helpers. Preserve media, caption visibility and one-step undo, and skip transition handles and held frames. Closes CapSoftware#2960
thesammykins
force-pushed
the
feat/native-filler-cleanup
branch
from
October 23, 2026 04:24
0299a4c to
cb65c22
Compare
thesammykins
marked this pull request as ready for review
October 23, 2026 04:53
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Remove Filler Words to the native GPUI editor's Captions tab. It generates local word-timed captions when needed, then produces ordinary editable clips in one undo step.
This is a first pass for later Studio editing: trim handles can recover a cut boundary, and the normal split/delete tools can remove a missed hesitation. Source media is preserved.
um,uh,uhm,erandermtokens, including drawn-out forms. Keeps acronyms, lexical substrings and context-dependent phrases.Live editor verification on a copy of a real recording:
These are captures immediately before and after the actual button interaction. Images are PR attachments; no image files are added to the repository. Source media hashes were unchanged and subtitles stayed hidden.
Recovery was also exercised in the live editor: one Undo restored the exact original configuration, including the absence of generated captions; Redo restored the cleanup. Manual split/delete worked, and dragging a trim handle recovered 250ms of removed footage. Undoing those manual edits restored the cleaned configuration exactly.
Validation:
cargo check,cargo build, formatting andgit diff --checkpassed.-D warningsreports the same 9 existing findings in unchanged code; none in the added code. The configured Biome binary was unavailable locally; Markdown links and whitespace were checked.Recognition can omit hesitations or misplace boundaries, so playback review and manual adjustment remain part of the workflow. No new dependencies, schema changes or migrations. Automatic post-recording cleanup is a follow-up; general Studio automation execution is tracked in #2959.
Closes #2960


Confidence Score: 5/5
The PR appears safe to merge; no actionable issues were found.Summary
Adds local filler-word removal to the native editor’s Captions tab.
No actionable issues were found. Review checks were static; no tests or native UI verification were run.
Recognition misses and imperfect cut boundaries were acknowledged by
thesammykinsin the PR description; playback review and manual adjustment are explicitly required. Retaining uppercase tokens and context-dependent phrases is intentional, as documented bythesammykinsin the PR description.Reviews (1) · Last reviewed commit: "feat(desktop): remove filler words in th..." · Reviewed by Greptile