macOS Limitations
On macOS, Octoclip usually gives a desktop-class experience, but system policy, the sandbox, and security mechanisms still impose some boundaries. Knowing these helps you separate "misconfiguration" from "this is how the system works."
Who this is for
- Users hitting background-monitoring or app-specific paste issues on macOS
- Users who want to tell whether a symptom is a system limit before debugging further
Main limitations
Store version and sandbox
The App Store build is constrained by the sandbox and store policy; some system-level capabilities may be removed or restricted (see the distribution notes in Platform Differences). If a capability you need isn't available in the store build, watch for a distribution channel not bound by store policy [待确认：current status of macOS direct download].
Background monitoring and sleep
Background clip monitoring on macOS is conditionally supported: it depends on the right permissions and a resident process. Behavior during lid-close, sleep, or screen lock may differ from a plugged-in resident state. When it acts up, check permissions and energy settings first.
Pasting into specific apps
Some apps (password fields, secure keyboards, heavily sandboxed apps) block programmatic pasting at the system level, showing as "the clip is in history but won't paste." This is usually the target app/system policy, not a sync problem.
Shortcut conflicts
When a global shortcut shares a combination with the system or another productivity tool, it "appears to do nothing." Check for conflicting keys.
What to do about these
- Won't paste only in certain apps: check that app's sandbox and security policy first — see Cannot Paste.
- Auto paste / global input doesn't work: usually a missing permission — see macOS Permissions.
- Background is intermittent: see Background Monitoring Unstable.
Most macOS issues are actually missing permissions or shortcut conflicts — all solvable. Only genuine hard limits (capabilities the sandbox forbids) require an alternative path.