Help with NodCue

Contact support

A verified support email address is pending. No contact address is published in this draft. A working contact channel must be added before this page is used as the App Store Support URL.

When a verified channel becomes available, include the app version, iOS/watchOS/macOS version, agent and Bridge version, approximate time, and the error shown. Remove account and device identifiers from screenshots. Do not send Apple passwords, login tokens, pairing credentials, API keys, private keys, source code, or full terminal logs.

Set up your iPhone

1. Use a release of NodCue configured for the same NodCue service as your Mac Bridge.
2. Open Settings and choose Sign in with Apple. Your Apple credential is exchanged for a NodCue session. A login error means setup has not completed.
3. Allow notifications if you want background approval alerts. Check both NodCue settings and the iPhone system notification settings.
4. After your computer is paired, refresh the approval list. Before allowing anything, check that it matches the action you intended on your computer.

Production login and computer pairing are still awaiting end-to-end verification. Do not treat a demo request or a connected label as proof of a working connection.

Set up Apple Watch

Install NodCue on the Watch paired with your iPhone. Open NodCue on iPhone, complete login, and use the Watch sync action. Then open NodCue on Watch and refresh.

There are two separate paths:

• Background alerts: the service sends a notification to iPhone. Apple’s notification routing may mirror it to Watch. Notification permissions, device state, and system settings affect delivery. NodCue does not promise Watch background alerts when iPhone is powered off.
• Watch app in the foreground: once configured with a valid session and network access, Watch is intended to fetch requests and submit decisions directly over HTTPS. This path still needs real-device verification.

If Watch has no session or its session has expired, open NodCue on iPhone, sign in again, and resync. A refresh or pending state is not confirmation that an approval was accepted.

Set up Mac Bridge

A supported signed installer and production pairing instructions are not available in this draft. Do not download look-alike packages or paste credentials into an unverified installer.

The current development Bridge needs Node.js 22.20.0 or later, a configured NodCue API address, and a stable computer identifier. Pairing saves the computer credential in macOS Keychain; the Hook launcher can read it there. The revised development CLI exchanges a single-use pairing challenge and code without an account header. Installation, upgrade, and uninstall have been tested in an isolated home directory; a packaged runtime and verified real-agent setup are still pending.

Before release, installation and upgrades must preserve existing Codex and Claude Code configuration, and uninstall must restore the prior configuration. Do not replace your existing Hook files wholesale. These operations have only been verified against local fixtures, not a production installer or users’ live agent configurations.

Current adapter scope is limited: Codex PermissionRequest for Bash, and Claude Code PreToolUse for Bash, Write, Edit, and MultiEdit. Other tools are outside this adapter scope. Compatibility with supported real CLI versions still needs verification.

Common questions

Why did my request expire?

Requests have a deadline. An expired or already decided request cannot be approved again. Check the final state and initiate a new action from your computer if needed.

Does “Allowed” mean the command succeeded?

No. Approval and execution are separate. “Allowed” grants permission for that request; check the execution result or your computer to see whether the action ran successfully.

Why did I not receive a notification?

Check notification permissions, Focus settings, and network connectivity. Open the app to read the latest server state. A push accepted by Apple does not prove delivery or that a decision was made.

What happens if I tap twice or lose the network?

The server’s final state determines the result. Refresh after a network error. Do not assume an action was allowed just because you tapped Allow.

What data leaves my computer?

The current adapters send account-linked request metadata, tool identifiers, a reduced summary, and a content fingerprint. Claude file summaries may include the filename. See the privacy draft for the verified scope and remaining gaps.

How do I revoke access or delete my account?

Server-side account deletion and Apple authorization revocation retry logic have been implemented and tested locally. The user-facing deletion flow and live Apple revocation have not yet been verified. Removing the app or stopping Sign in with Apple does not by itself delete NodCue’s stored data. A verified deletion process must be provided before release.