Send a one-way push notification to the user's devices. Use this to inform the user about task completion, errors, or status updates. Long bodies are automatically uploaded as a file for full viewing.

Copy text to the user's device clipboard. The text will appear in their clipboard history and can be pasted immediately.

List recent push notifications. Use this to check notification history, avoid duplicates, or reference previous messages.

Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from the user's feed.

Dismiss all push notifications at once. Clears the entire notification feed.

Send a push notification to all subscribers of a channel. Use zeph://channels resource to find available channels.

Send a file to the user's device. Pass filePath to send a file that already exists on disk — images (png/jpg/gif/webp/heic), PDFs, logs, anything. Pass content instead to send text you generated. Images render inline on the device.

Ask the user to choose from predefined options via push notification. The tool blocks until the user responds or the timeout is reached. Requires ZEPH_HOOK_ID environment variable.

Request text input from the user via push notification. The tool blocks until the user responds or the timeout is reached. Requires ZEPH_HOOK_ID environment variable. The user may also attach screenshots or files: those arrive as local absolute paths in the attachments field of the result, and reading them is part of reading the answer.

Ask the user a question with quick-reply buttons and a text input field. Combines prompt (buttons) and input (text) in a single notification. The user can either tap a button or type a response. actions is the steering surface, not decoration: pass 2–4 buttons on nearly every ask — the next-step candidates you would otherwise write as prose (next command, review, stop) plus a safe Done-like fallback. Leave actions out ONLY when the answer is inherently free-form text (a name, a path, a paragraph); a bare text box on a "done — what next?" ask leaves the phone with nothing to tap. Blocks until the user responds or the timeout is reached. Requires ZEPH_HOOK_ID environment variable. The user may also attach screenshots or files to the answer: those arrive as local absolute paths in the attachments field of the result, and reading them is part of reading the answer. NOTE: unlike zeph_notify and zeph_file, this tool is never end-to-end encrypted — the hook route it uses cannot carry the sender key — so do not put secrets in the question or expect a private answer.

Set a custom display name for THIS agent session in the user's Zeph app (the Streams › Agents list). Label what this session is working on — e.g. "Prod deploy" or "Auth refactor" — so the user can tell parallel sessions apart on their phone. Renames the current session; the name persists until changed.