# OnExit

> Notifications and alarms from an AI agent to the phone its owner chooses.

A person links a phone and creates a device-scoped key. MCP, CLI, and REST use that key to send a handoff. The person chooses whether the key sends messages or rings alarms; an agent cannot override that delivery mode.

## Documentation

- [Integration guide](/docs/): phone setup, MCP, CLI, REST, and delivery behavior.
- [Agent reference](/llms-full.txt): tool names, authentication, examples, limits, and failure handling.
- [Plans](/#pricing): choose by how often agents reach you; every plan includes unlimited phones,
  with a monthly agent-handoff allowance.
- [Privacy](/privacy/): data use, storage, and deletion.
- [Terms](/terms/): acceptable use and service limits.
- [Support](/contact/): account, delivery, or billing help.

## Boundaries

Use the key provided by the user. Never request a database service key or push token. A successful API response confirms acceptance, not that the person heard an alarm. Critical delivery requires permission and depends on the phone OS. Do not use this service for emergency or safety-critical alerts.

## Prompt-based setup

In the web app, link a phone, open Agents, choose the phone and delivery mode, and create a connection. Choose Cursor, Codex, or another MCP client, then use Copy setup prompt. The generated prompt includes the correct hosted endpoint, a unique server name, the device ID, timezone, and a private bearer key. It is available only in the current page session; do not log, commit, or repeat its key.

Merge the configuration into the user's local MCP settings. Cursor uses ~/.cursor/mcp.json with mcpServers, url, and headers. Codex uses ~/.codex/config.toml with mcp_servers, url, and http_headers. The hosted server needs no package install or repository checkout. Restart or reconnect the client if required; report unfinished steps accurately. Verify using ping, list_devices, and get_current_time. Confirm the phone and key delivery mode. Ask before sending a test handoff. API acceptance does not prove phone receipt.

If the key is lost, create a replacement connection and revoke the old one after updating the client. A copied prompt is not proof of an active MCP connection. The CLI is currently source-built for beta testers, not a public npm install.