Repository navigation
[Feature Request]: Customizable "After Capture" behaviors for Screenshots (Toggle Editor, Clipboard, and Auto-Save) #1860
Description
Hi @richiemcilroy,
Currently, whenever an Area Screenshot is captured, Cap automatically forces the Annotation/Editor window to open. While this is great for quick edits, it completely disrupts the workflow when taking multiple screenshots in sequence for documentations or quick clipboard sharing.
I would love to see a highly flexible "After Capture" settings section (similar to tools like CleanShot or native macOS) allowing users to independently toggle behaviors.
Proposed Solution:
Please add the following checkbox/toggle options under the Screenshots settings panel:
- [ ] Open in Editor / Annotation Tool: If turned off, screenshots will bypass the Editor completely, allowing for uninterrupted back-to-back captures.
- [ ] Save to Default Path automatically: Automatically saves the captured file silently to the local directory without opening any UI.
- [ ] Copy to Clipboard automatically: Instantly copies the raw image to the macOS clipboard so it can be pasted straight into Notion, Slack, or GitHub.
Bonus Idea: Show Floating Thumbnail Preview
Alternatively, add a toggle for a temporary floating thumbnail in the bottom corner of the screen (native macOS style).
- If left alone, it vanishes and applies the background auto-save/clipboard rules.
- If clicked, it opens the full Cap Annotation Tool.
This level of customization would make Cap an incredibly versatile tool for both casual users and high-velocity power users who capture dozens of screenshots a day!
Thanks, Denny
Activity
linear commentedon May 21, 2026
CAP-721
tembo commentedon May 21, 2026
Some context from the codebase that should help with implementation:
Current screenshot flow: The editor is unconditionally opened after capture at several points:
apps/desktop/src-tauri/src/hotkeys.rs:215,232- after display/window screenshotsapps/desktop/src-tauri/src/tray.rs:729- from tray menuapps/desktop/src-tauri/src/lib.rs:5684- after image importEach location calls
ShowCapWindow::ScreenshotEditor { path }.show(&app).awaitimmediately aftertake_screenshot()returns.Settings infrastructure already exists: The
GeneralSettingsStoreinapps/desktop/src-tauri/src/general_settings.rshas a similar pattern for recordings withPostStudioRecordingBehaviour(line 16-20), which toggles betweenOpenEditorandShowOverlay. A similar enum could be added for screenshots. The settings are persisted viatauri-plugin-storeand the UI pattern can be found inapps/desktop/src/routes/(window-chrome)/settings/.Clipboard copy is already implemented:
commands.copyScreenshotToClipboard(path)exists and is used in the screenshots settings page (apps/desktop/src/routes/(window-chrome)/settings/screenshots.tsx:113-116). The underlying Rust command should work for auto-copy after capture.Related issues worth coordinating with:
These three issues together would make Cap much more competitive with CleanShot-style workflows for high-velocity screenshot users.
dennyschroeder commentedon Jun 11, 2026
Hi, ist there an update to this topic?
sheeesh3 commentedon Oct 8, 2026
+1 on this, especially the floating thumbnail option.
My flow is: take a screenshot, it's already on the clipboard, paste it. Having the editor open after every capture means closing a window every time, which is the main friction I have with Cap screenshots. A small corner preview that disappears on its own and opens the editor only when clicked (like the native macOS one) would be ideal.
I noticed there's a draft PR from another contributor in #1897. I haven't reviewed its code, so I can't speak to it, but it looks related. If it would help to have more hands on this, I'm happy to contribute.