#7 [Known limitation] Sandboxed apps (UWP / WSA) block synthetic Ctrl+V

[Anonymous]

Originally created by: phantasmat2018

Status: Known limitation, wontfix.

In certain Windows sandboxed environments - UWP apps (Microsoft Store), WSA (Windows Subsystem for Android), some kiosk-mode apps, and a few games with anti-cheat - CapyBro's synthetic Ctrl+V does not actually trigger paste, even though the AI result is correctly placed in the clipboard.

Cause

Windows UIPI (User Interface Privilege Isolation) blocks SendInput from a normal-integrity process to a higher-integrity or sandboxed process.

Workaround for users

The AI result IS in your clipboard. Just press Ctrl+V manually in the target app. The text will paste normally - only the SYNTHETIC keystroke from CapyBro is blocked, not real user input.

The toast notification stays visible to remind you that the result is ready. Click x on the toast when done.

Why "wontfix"

This isn't a bug - it's intentional Windows security architecture. Solutions would require either:

• Running CapyBro as administrator (degrades security for ALL users)
• UAC manifest with uiAccess=true (requires Authenticode signing + admin install)
• Per-app exceptions via accessibility APIs (different mechanism per host)

None of these are worth the security trade-off for a "convenience layer over Ctrl+V".

Reporting

Documented in the FAQ and the README troubleshooting section. If you encounter this in an app where you think it SHOULDN'T be blocked, please comment with the specific app name + Windows version.