# NotiBuddy > A product preview of an iPhone companion for AI assistants, apps, and services. Paired senders can send questions, receive answers, and share progress. MCP is one integration option. ## Availability The Apple app is still in preview with no public app download. Existing testers need a supplied app build. The notibuddy 0.2.9 CLI, Node.js client, and local stdio MCP server are published on npm; Node.js 20 or later is required. Use npx -y notibuddy@^0.2.9 with the app's actual pairing instructions. Package installation does not approve a sender. Never invent or expose pairing credentials. Native iPad, iPhone Duo, and native Apple Watch support are launch requirements still undergoing acceptance testing. The public client does not enable the pending Watch rollout. Do not describe direct Watch delivery or paid purchases as currently available. ## Documentation - [Setup and tool instructions](https://notibuddy.app/setup.md) - [Direct app and service integrations](https://notibuddy.app/setup#connect-an-app-or-service) - [Help](https://notibuddy.app/support) - [Privacy](https://notibuddy.app/privacy) - [Release status and proposed plans](https://notibuddy.app/) - [Published computer package](https://www.npmjs.com/package/notibuddy) - [Computer client and protocol source](https://github.com/yourbit-network/notibuddy) - [Terms and Apple standard EULA](https://notibuddy.app/terms) ## Architecture The notibuddy package includes a TypeScript/JavaScript client for Node.js and a local stdio MCP server. Apps and services can implement the documented protocol without MCP; browser and other runtime compatibility is not implied. Pairing uses the phone's private Share Setup bundle to establish a sender signing identity and file-receiving key. Requests are encrypted and signed; replies must be verified. In a compatible app build, Connect → Add a connection (or Add if already connected) → Create setup code → Share Setup creates a private automatic capability lasting ten minutes. Keep NotiBuddy open and online: the phone must verify the first eligible new sender before accepting it. Later new senders using that setup need manual approval; compare the full Sender Key ID in Terminal and Connect. Repeating setup for an unchanged approved identity is idempotent and does not consume another code. A newer manual pending approval replaces the older pending one, not already approved senders. Older preview builds use Share Setup and manual approval. Installing client 0.2.9 does not add new app controls. Use manual approval instead is available in code-capable builds. Cancel code stops automatic acceptance but does not revoke ordinary credentials in shared copies or disconnect approved senders. Keep every setup copy private. The client normally waits up to 45 seconds for automatic setup. A timeout is not success: keep the app open and retry the same command with the same saved destination and keys. Use Retry setup for interrupted preparation, or Create a new code after expiry/cancellation. Do not silently regenerate sender keys or approve on the user's behalf. The canonical website is https://notibuddy.app; notibuddy.com redirects there. The branded relay is https://notibuddy.app. Keep the relay URL from each actual pairing bundle, including older pairings. Do not edit credentials to migrate a URL or configure the relay as a remote MCP server. ## Destination selection All saved destinations live under ~/.notibuddy. Each CLI send requires --to . MCP startup must select --to or an explicit --allow-to allowlist; every ask, activity, or file call in allowlist mode must include to. Use notibuddy_list_destinations without to to see only exposed destinations. There is no default destination, fallback, or broadcast. The optional --sender display label defaults to the hostname; it is not a separate identity, inbox, permission, or reply address. Status is local configuration only; doctor --to checks the relay and approval. Verify setup by receiving a real response, not merely displaying a notification. ## Tools and limits - notibuddy_ask: send a question, then check pending responses with resume_id. New ordinary requests, including protected approvals, forms and diffs, default to and allow at most 10800 seconds (three hours). timeout_seconds selects a shorter lifetime; wait_seconds is a separate poll budget (default 25, max 55 seconds). CLI equivalents are --timeout and --wait. Resume/retry preserves the original signed deadline, including across client restarts; upgrading does not extend existing requests. Silence or expiry is never approval. - notibuddy_activity: start, update, end, or poll a progress display or timer. The AI must receive and act on phone controls. Activity requests retain their one-hour lifetime; ordinary-request timeout does not change timers. - notibuddy_files_list / notibuddy_files_receive: collect a phone upload for the selected connection. Receiving requires id and returns a saved local path, never file contents in the tool result. There is no automatic background collector. Collect within 24 hours; Delivered means saved, not read. Retry the same ID for saved_pending_receipt. Do not open or execute untrusted files automatically. - The sending application or AI session must remain active on its computer or server and check for responses. NotiBuddy cannot wake a sleeping machine, restart an ended AI session, or replace the host's own approval prompts. - Free use allows five requests in a rolling 24 hours, including activity starts, updates, and ends. Live Activities are also available on the free plan. - Planned launch allowances: one primary iPhone/iPad destination on Free, three per Annual purchase, twelve per Lifetime purchase, with one included paired Watch per iPhone sharing its allowance. Paid plans and direct Watch delivery are not available in the public preview. Family Sharing is off for launch. - Phone file sends are limited to one file of 10,000,000 bytes. Content and filename are encrypted for the approved receiving key; connection labels do not isolate file access. Relay access ends on delivery, cancellation, revocation, or the 24-hour deadline; failed physical deletions are retried. Received local copies remain until deleted. - Replacement devices use fresh keys and pairing. There is no key recovery or restored message history. In-app account deletion and Apple subscription cancellation are separate actions.