Skip to main content
If your Advanced Integration isn’t producing a badge by your cursor, the cause is almost always one of a handful of configuration issues — a wrong platform toggle, a mismatched ID, or a quoting problem introduced when pasting the command into a config file. Work through the checks below one at a time to narrow it down quickly.

​
Checklist

Proximate shows hook commands in two platform-specific formats. Before you copy a command, make sure the toggle on the integration card is set to the correct operating system for the machine where the command will run:
  • macOS commands start with open
  • Windows commands start with start
If you copied the wrong variant, go back to your integration card in Proximate, switch the toggle to the correct platform, and copy the command again — then update your script or config file with the new version.
Each hook command contains a unique private ID. If you have multiple integrations, it’s easy to accidentally paste the ID from one into the config for another. Open your integration card in Proximate and compare the ID shown in the (truncated) hook display against what’s in your script or config file. They must match exactly, including capitalization.If you suspect a mismatch, re-copy the command directly from Proximate rather than editing the ID by hand.
Hook commands are silently ignored when Proximate’s notification system is turned off. To check:
  1. Open Settings from the Proximate menu bar, dock, or taskbar icon.
  2. Select the Notifications tab in the sidebar.
  3. Confirm the toggle at the top of the sidebar is switched on.
If the toggle was off, enable it and try triggering the hook again.
Each hook command is copied to your clipboard as a ready-to-run shell command. If you’re embedding it in a config file (for example, a JSON settings file, a YAML pipeline definition, or a Makefile), the quoting rules of that format may require adjustments:
  • JSON config files: Double quotes inside a JSON string value must be escaped as \". For example, open "proximate://…" becomes "command": "open \"proximate://…\"".
  • YAML files: Watch for characters like : and " that can break YAML parsing. Wrapping the whole value in single quotes is often the safest option.
  • Shell scripts: The command should work as-is. Make sure the script is being executed by a shell that has access to open (macOS) or start (Windows).
When in doubt, refer to the documentation for the tool you’re integrating with — the Claude Code example shows exactly how to handle quoting inside a JSON settings file.
The fastest way to isolate whether the problem is with Proximate or with how your tool is calling the command is to run the hook manually:
  1. Copy a hook command from your integration card in Proximate.
  2. Paste it into a Terminal (macOS/Linux) or Command Prompt / PowerShell (Windows) window.
  3. Press Return or Enter to run it.
You should see the notification icon appear next to your mouse cursor within a second or two. If the badge appears, Proximate is working correctly and the issue is in how your tool invokes the command. If the badge does not appear, please submit a support ticket or contact support@getproximate.app with details about your setup.

​
Still Stuck?

If you’ve worked through all the checks above and notifications still aren’t appearing, the Proximate support team is happy to help. Submit a support ticket or reach out directly at support@getproximate.app. It helps to include your operating system, the tool you’re integrating with, and the result of the terminal test above.