Troubleshooting
This page collects common problems with ClipboxAI on macOS and how to resolve them.
The app won't start or crashes on launch
- Make sure your macOS version meets the minimum (macOS 14 Sonoma+).
- Quit and relaunch the app.
- Reboot your Mac.
If downloaded from GitHub Releases, try the latest or notarized build.- If problems persist, collect logs (below) and open an issue.
Clipboard history isn't capturing copies
Symptoms: new copies don't appear in the history panel.
Checklist:
- Make sure the app is running and its menu bar icon is visible.
- Confirm Clipboard monitoring is enabled in Settings → Privacy / General.
- The app needs the relevant macOS permission to read the pasteboard in the background — see Permissions.
- Some apps (password managers, secure-input fields) intentionally block clipboard access; this is expected.
Cloud AI actions don't return a result
Symptoms: an AI action fails, hangs, or shows a config error.
Checklist:
- Open Settings → AI and confirm a provider is selected and a key is entered.
- Verify the key is valid for that provider and has quota/credits.
- Check your network connection — cloud AI needs internet access.
- Confirm the selected model name is correct for the provider.
- If the config banner still appears in the AI Tool window, the key isn't saved to the Keychain; re-enter it.
Marketplace install doesn't add the action
Symptoms: clicking Install does nothing, or the app doesn't open.
Checklist:
- The deep link
clipboxai://install?action=<id>must be handled by the installed app — make sure ClipboxAI is installed and running. - If your browser blocks the deep link, copy it and open it manually, or install from inside the app's Marketplace tab.
- Check that the action ID is still published in the marketplace.
Resetting the app
To reset settings and clear local data:
- Quit ClipboxAI.
- Remove the container (this deletes history and settings):
bash
rm -rf ~/Library/Containers/com.w3cub.clipboard- Reopen the app and reconfigure. API keys in the Keychain must be removed separately in Keychain Access if desired.
How to collect debug logs
bash
# Copy logs to Desktop for sharing
cp ~/Library/Containers/com.w3cub.clipboard/Data/Library/Logs/ClipboxAI/*.log ~/Desktop/ 2>/dev/nullThen open an issue on GitHub and attach the logs.
Report an issue
When opening an issue, include:
- macOS version (Apple menu → About This Mac)
- ClipboxAI version (app menu → About)
- Steps to reproduce
- Logs (see above)
This helps maintainers identify and fix the problem faster.
