@zeph-to/cli 1.12.0

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Zeph
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,499 @@
+# @zeph-to/cli
+
+[![npm](https://img.shields.io/npm/v/@zeph-to/cli.svg)](https://www.npmjs.com/package/@zeph-to/cli)
+[![downloads](https://img.shields.io/npm/dm/@zeph-to/cli.svg)](https://www.npmjs.com/package/@zeph-to/cli)
+[![node](https://img.shields.io/node/v/@zeph-to/cli.svg)](https://nodejs.org)
+[![license](https://img.shields.io/npm/l/@zeph-to/cli.svg)](./LICENSE)
+
+Push notification SDK + CLI for [Zeph](https://zeph.to), with an optional
+resident listener that **drives Claude Code / Codex / Gemini sessions
+from your phone** by injecting messages into named tmux sessions.
+
+- `ZephHook` SDK — native `fetch`, no runtime deps. Send/list/dismiss pushes.
+- `zeph` CLI — install Zeph plugins, send pushes, run agents under tmux,
+  and listen for inbound messages from your phone.
+
+## Installation
+
+```bash
+npm install -g @zeph-to/cli
+# or for one-off use
+npx @zeph-to/cli notify --title "Hello"
+```
+
+## Quick Start
+
+```bash
+# Sign in via browser — auto-fetches your API key + hook into
+# ~/.zeph/config.json (no copy-paste)
+npx @zeph-to/cli login
+
+# Install for your AI agents (rules + hooks + MCP). Reuses the saved
+# config; detects Claude Code / Cursor / Windsurf / Gemini / Codex / …
+npx @zeph-to/cli install
+```
+
+`login` opens a browser to the Zeph web app, asks you to confirm "connect
+this computer", then issues a fresh API key (labelled with your hostname)
+and reuses or creates a hook — writing both back to `~/.zeph/config.json`
+over a localhost loopback. No credential ever gets pasted into the
+terminal.
+
+Prefer to paste credentials yourself (or on a headless box with no
+browser)? Skip `login` and pass them to `install` directly:
+
+```bash
+npx @zeph-to/cli install --key ak_... --hook hook_...
+```
+
+Either way it saves to `~/.zeph/config.json`. All Zeph tools (CLI, MCP
+server, plugin hooks, listener) read this file.
+
+To **send** notifications:
+
+```bash
+zeph notify --title "Deploy done" --body "v2.1.0 shipped"
+```
+
+To **drive a Claude Code / Codex / Gemini session from your phone**, see
+[Remote Control](#remote-control) below.
+
+## Remote Control
+
+> Send messages from your phone *into* a live Claude Code / Codex /
+> Gemini session — even after a `zeph_ask` polling window has expired.
+
+The MCP tools `zeph_ask` / `zeph_prompt` / `zeph_input` open a polling
+loop on a fixed timeout (120–600 s). Once that window closes the
+session becomes unaddressable from the phone, even though it's still
+running. The `zeph listener` daemon fixes this by keeping a persistent
+WebSocket open to Zeph and injecting matching messages into a *named*
+tmux session via `tmux send-keys`.
+
+### Architecture
+
+```
+[phone — "Active Agents" picker on Zeph app]
+   │  selects session, types message
+   ▼  POST /pushes/send  { type: 'agent.command',
+   │                       agentSessionName: 'zeph-myapp',
+   │                       body: '리팩토링 마무리해줘' }
+[Zeph backend]
+   │  WebSocket fan-out (push.new)
+   ▼
+[zeph listener — resident daemon, started by `zeph cc` automatically]
+   │  tmux send-keys -l -t zeph-myapp "리팩토링 마무리해줘" + Enter
+   ▼
+[tmux session "zeph-myapp" running claude / codex / gemini]
+```
+
+The listener also reports its tmux session inventory back to the server
+every 5 seconds, so the phone picker stays in sync — no manual
+configuration needed once a session is running.
+
+### Setup
+
+1. **Install tmux.** The listener uses `send-keys`; the wrapper spawns
+   named sessions. `brew install tmux` on macOS, `apt install tmux` on
+   Debian/Ubuntu.
+
+2. **Add `wsUrl` to `~/.zeph/config.json`** (the WebSocket endpoint of
+   your Zeph backend — CDK output `WsApiUrl`):
+
+   ```json
+   {
+     "apiKey": "ak_...",
+     "hookId": "hook_...",
+     "wsUrl": "wss://<api-id>.execute-api.<region>.amazonaws.com/<stage>"
+   }
+   ```
+
+   Alternatively set `ZEPH_WS_URL` in your shell env.
+
+3. **Run agents through the wrapper.** That's it.
+
+   ```bash
+   zeph cc        # claude  → tmux session "zeph-<project>"
+   zeph codex     # codex   → tmux session "zeph-<project>"
+   zeph gemini    # gemini  → tmux session "zeph-<project>"
+   ```
+
+   The first `zeph cc` on a machine **auto-spawns a background
+   listener** (singleton, PID file at `~/.zeph/listener.pid`,
+   stdout/stderr at `~/.zeph/listener.log`). You never run
+   `zeph listener` by hand — every `zeph cc` checks the PID file and
+   skips the spawn when one is already alive, so opening a dozen
+   terminals doesn't create a dozen daemons. The daemon survives
+   between `zeph cc` invocations.
+
+   Project name resolves from `CLAUDE_PROJECT_DIR` /
+   `CURSOR_PROJECT_DIR` / `WINDSURF_PROJECT_DIR` if set, else the git
+   repo root, else the cwd basename. Any extra args after the command
+   pass through to the agent verbatim:
+
+   ```bash
+   zeph cc --resume "abc123"
+   zeph cc --dangerously-skip-permissions
+   zeph codex --model gpt-5-high "fix the failing test"
+   ```
+
+   **Multiple sessions in one project.** Open another terminal in the
+   same folder, run `zeph cc` again, and the wrapper auto-suffixes:
+   first session is `zeph-encl`, the next attached one becomes
+   `zeph-encl-2`, then `zeph-encl-3`, etc. The phone picker shows them
+   as `encl · Claude`, `encl · Claude #2`, `encl · Claude #3`. If
+   `zeph-encl` already exists but is **detached** (no one attached),
+   the wrapper reattaches to it instead of spawning a new one — close
+   the terminal, come back later, pick up where you left off.
+
+   If you're already inside a tmux session (`$TMUX` set) the wrapper
+   skips the outer tmux and runs the agent in the current pane — the
+   listener can't target an unnamed session that way, but you keep your
+   existing multiplexer setup.
+
+### Diagnostics
+
+The auto-spawned listener writes to two files under `~/.zeph/`:
+
+- `listener.pid` — the running daemon's PID. `cat ~/.zeph/listener.pid`
+  + `ps -p <pid>` to confirm it's alive.
+- `listener.log` — stdout + stderr from the daemon. `tail -f` to watch.
+
+A healthy listener log shows one line per cycle:
+
+```
+[xx:xx:xx] reported 2 session(s): zeph-myapp, zeph-otherapp
+[xx:xx:xx] ✓ server persisted 2 session(s)
+```
+
+If you see `! server rejected listener.sessions: ...` instead, the
+message points at the failure (auth, missing device record, etc.) so
+you can fix the actual problem instead of guessing.
+
+To force a restart — e.g. after upgrading `@zeph-to/cli`:
+
+```bash
+kill $(cat ~/.zeph/listener.pid)
+rm ~/.zeph/listener.pid
+zeph cc        # autospawns the new build
+```
+
+To run it in the foreground (for development of the SDK itself):
+
+```bash
+zeph listener
+```
+
+You'll get the same logs you'd otherwise tail from `listener.log`.
+
+### Custom tmux sockets
+
+The listener auto-discovers the tmux socket — it probes the default
+location, walks per-user `$TMPDIR` paths (macOS `/var/folders/.../T/`),
+falls back to `/tmp/tmux-<uid>/`, and finally finds running tmux servers
+via `lsof` so stale socket files don't trip discovery. If your tmux
+uses `tmux -L <name>` or a non-standard `-S <path>`, set the override
+explicitly:
+
+```bash
+export ZEPH_TMUX_SOCKET=/path/to/socket
+```
+
+(The wrapper passes the env to the auto-spawned listener, so setting
+it in your shell rc is enough.)
+
+### Wire format
+
+The listener only acts on pushes with `type='agent.command'` carrying
+the tmux session name in `agentSessionName` and the message in `body`.
+Other pushes (Stop-hook auto-pushes, `zeph_ask` responses, channel
+broadcasts, plain notes) are ignored. End-to-end:
+
+```
+tmux send-keys -l -t <agentSessionName> "<body>"
+tmux send-keys    -t <agentSessionName> Enter
+```
+
+If you need to send one from the command line (debugging, scripting),
+build the structured push directly:
+
+```bash
+curl -X POST "$ZEPH_BASE_URL/pushes/send" \
+  -H "X-API-Key: $ZEPH_API_KEY" \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "type": "agent.command",
+    "targetDeviceId": "dev_listener_<sha8(hostname)>",
+    "agentSessionName": "zeph-myapp",
+    "body": "테스트 통과시키고 PR 올려줘"
+  }'
+```
+
+### Defense
+
+The listener is a remote-code-execution surface by design (it types
+into a shell-adjacent pane). The defense is layered:
+
+1. **Pane guard** — before injecting, the listener checks
+   `tmux display-message -p '#{pane_current_command}'`. If the pane is
+   at an interactive shell (`bash`/`zsh`/`fish`/`sh`/`dash`/`ksh`/
+   `tcsh`/`csh`/`pwsh`), the inject is refused. CC/Codex/Gemini exited
+   ≠ phone gets free shell access.
+2. **Literal injection** — `tmux send-keys -l` takes the payload as
+   data; tmux escape sequences inside a message can't drive other tmux
+   commands.
+3. **Session-name allowlist** — only `[A-Za-z0-9._-]+` is accepted as
+   a session target, so shell metacharacters never reach the tmux argv.
+4. **Per-session rate limit** — 30 injections/minute/session token
+   bucket caps a runaway/compromised sender.
+5. **Agent permission gate stays on** — your CC/Codex/Gemini permission
+   prompt is still in front of every destructive tool call. The phone
+   can *talk* but can't approve `rm -rf` for you.
+
+The transport (WS) is currently authenticated by API key + `push:read`
+scope and is **not** end-to-end encrypted in v1 — your Zeph backend
+sees the message plaintext. If you self-host or trust your backend,
+that's fine. If you don't, hold off until per-device E2E ships.
+
+## CLI Usage
+
+```bash
+# Send a notification
+zeph notify --title "Deploy done" --body "v2.1.0 shipped"
+
+# Send with priority
+zeph notify --title "Build failed" --priority high --url https://ci.example.com/123
+
+# List recent pushes
+zeph list
+zeph list --limit 10 --type note
+
+# Dismiss a push
+zeph dismiss push_01JXY...
+zeph dismiss --all
+
+# Test connection
+zeph test
+
+# Run an agent in a named tmux session (so the listener can reach it)
+zeph cc                       # claude
+zeph codex                    # codex
+zeph gemini                   # gemini
+
+# Run the resident listener (foreground; background it as you like)
+zeph listener
+zeph listener --ws-url wss://...   # override config
+
+# JSON output
+zeph notify --title "Hello" --json
+```
+
+### Commands
+
+| Command | Description |
+|---------|-------------|
+| `login` | Browser sign-in: auto-fetch API key + hook into `~/.zeph/config.json` over a localhost loopback (`--web-url`, `--timeout`). No copy-paste |
+| `install` | One-command setup: detect agents, save config, install rules + hooks + MCP |
+| `uninstall` | Remove Zeph from all detected agents (`--dry-run`, `--purge`) |
+| `verify` | Check installation health across detected agents (`--ping` for a live API call) |
+| `check-update` | Check whether a newer Zeph version is on npm |
+| `notify` | Send a push notification |
+| `list` | List recent push notifications |
+| `dismiss <id>` | Dismiss a push (or `--all`) |
+| `test` | Verify connection and API key |
+| `cc` · `codex` · `gemini` | Run the agent in a `zeph-<project>` tmux session (auto-suffixed `-2`, `-3`, … on attached collisions). Auto-spawns the background listener on first invocation so the phone picker just works. Trailing args pass through to the agent (`zeph cc --resume "..."`) |
+| `listener` | (Usually unnecessary — `zeph cc` autospawns it.) Resident daemon: subscribes via WebSocket, reports tmux session inventory every 5 s, injects `agent.command` pushes into the matching session. Run in the foreground for SDK development; otherwise let `zeph cc` manage it |
+
+### Notify Options
+
+| Flag | Description |
+|------|-------------|
+| `--title <text>` | Push title (default: `"Task done"`) |
+| `--body <text>` | Push body (default: `"<project> · <branch>"` if cwd is a git repo, else `"<project>"`) |
+| `--url <url>` | URL to include |
+| `--type <type>` | Push type: `note`, `link`, `file`, `hook` |
+| `--priority <p>` | Priority: `low`, `normal`, `high`, `urgent` |
+| `--device <id>` | Target device ID |
+
+The defaults are tuned for hook-driven invocations (e.g. Stop hooks
+calling `zeph notify --title "Task done"` without a body) — you'll see
+which project + branch finished without writing per-IDE wrappers. Pass
+`--body ""` explicitly to suppress.
+
+### Listener Options
+
+| Flag | Description |
+|------|-------------|
+| `--ws-url <url>` | WebSocket endpoint (or set `ZEPH_WS_URL` env, or `wsUrl` in `~/.zeph/config.json`) |
+| `--key <api-key>` | API key (or set `ZEPH_API_KEY` env) |
+
+The listener reconnects with exponential backoff + jitter (1 s → 30 s
+cap). Heartbeat is ping every 25 s with a 10 s pong timeout. On an
+authentication failure close (4001/4002/4003) the listener exits with
+code 3 instead of looping forever — fix the key and restart.
+
+### List Options
+
+| Flag | Description |
+|------|-------------|
+| `--limit <n>` | Number of pushes (1-20, default 5) |
+| `--type <type>` | Filter by push type |
+
+### Global Options
+
+| Flag | Description |
+|------|-------------|
+| `--key <api-key>` | API key (or set `ZEPH_API_KEY` env) |
+| `--base-url <url>` | API base URL (or set `ZEPH_BASE_URL` env) |
+| `--json` | Output JSON format |
+| `--version` | Print version |
+
+### Mute
+
+Mute is project-scoped (uses project directory hash). Created by Claude
+Code `/zeph-mute` command.
+
+Notifications are silently skipped when a mute file exists for the
+current project:
+
+```bash
+# Mute (created by /zeph-mute in Claude Code plugin)
+HASH=$(echo -n "$PROJECT_DIR" | cksum | cut -d' ' -f1)
+touch /tmp/zeph-muted-$HASH
+
+# Unmute
+rm /tmp/zeph-muted-$HASH
+```
+
+The CLI checks `CLAUDE_PROJECT_DIR`, `CURSOR_PROJECT_DIR`,
+`WINDSURF_PROJECT_DIR`, and falls back to `cwd`.
+
+### Exit Codes
+
+| Code | Meaning |
+|------|---------|
+| 0 | Success |
+| 1 | General error |
+| 2 | Quota exceeded |
+| 3 | Authentication failed (also: listener auth close 4001/4002/4003) |
+| 127 | A required external binary (e.g. `tmux`, `claude`) was not found on PATH |
+
+### Environment Variables
+
+| Variable | Description |
+|----------|-------------|
+| `ZEPH_API_KEY` | API key (fallback when `--key` not provided) |
+| `ZEPH_BASE_URL` | API base URL (default: `https://api.zeph.to/v1`) |
+| `ZEPH_WS_URL` | WebSocket endpoint for `zeph listener` (no default — required) |
+| `ZEPH_TMUX_SOCKET` | Explicit tmux socket path for the listener (skips auto-discovery — use when your tmux runs with `-L <name>` or a custom `-S <path>`) |
+| `ZEPH_SESSION_ID` | AI session ID (fallback when `--session` not provided) |
+
+## SDK Usage
+
+```typescript
+import { ZephHook } from '@zeph-to/cli';
+
+const hook = new ZephHook({ apiKey: 'ak_...' });
+
+// Notify
+const result = await hook.notify({
+  title: 'Build Complete',
+  body: 'Deploy succeeded',
+  url: 'https://example.com/deploy/123',
+  priority: 'high',
+});
+console.log(result.pushId); // 'push_01JXY...'
+
+// List
+const list = await hook.list({ limit: 5 });
+console.log(list.pushes);
+
+// Dismiss
+await hook.dismiss('push_01JXY...');
+await hook.dismissAll();
+```
+
+### Constructor Options
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `apiKey` | `string` | Required — API key from Zeph settings |
+| `baseUrl` | `string?` | API base URL (default: `https://api.zeph.to/v1`) |
+| `timeout` | `number?` | Request timeout in ms (default: 30000) |
+
+### Notify Payload
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `title` | `string?` | Push title |
+| `body` | `string?` | Push body |
+| `url` | `string?` | URL to include |
+| `type` | `'note' \| 'link' \| 'file' \| 'hook'?` | Push type (default: `hook`) |
+| `priority` | `'low' \| 'normal' \| 'high' \| 'urgent'?` | Priority (default: `normal`) |
+| `targetDeviceId` | `string?` | Send to specific device |
+
+### Error Handling
+
+```typescript
+import { ZephHook, AuthenticationError, QuotaExceededError, ZephError } from '@zeph-to/cli';
+
+try {
+  await hook.notify({ title: 'Hello' });
+} catch (err) {
+  if (err instanceof AuthenticationError) { /* Invalid API key */ }
+  if (err instanceof QuotaExceededError) { /* Monthly limit reached */ }
+  if (err instanceof ZephError) { /* Other API error */ }
+}
+```
+
+## Supported Agents
+
+`zeph install` detects and configures these agents automatically:
+
+| Agent | What gets installed |
+|-------|-------------------|
+| Claude Code | Plugin (hooks + MCP server) |
+| Cursor | MCP server + stop hook + rules |
+| Windsurf | MCP server + response hook |
+| Gemini CLI | MCP server + AfterAgent hook |
+| Codex CLI | Stop hook |
+| Copilot CLI | Session end hook |
+| Cline | Rules file |
+
+For remote-control via `zeph listener` the per-agent setup is the same
+across CC/Codex/Gemini — the wrapper just spawns them in a named tmux
+session.
+
+## Encryption
+
+Push bodies are encrypted with AES-256-GCM. The wrapping key is derived
+via ECDH P-256 and synced across your own devices on first run so every
+device can read the same push. Toggle encryption in the Zeph app
+(Settings → Encryption); when disabled, the CLI sends plaintext. No
+configuration needed.
+
+**Threat model honesty:** keys are persisted on the Zeph backend to
+enable cross-device sync, so this is *device-shared* encryption — not
+true end-to-end. It protects push contents from passive network
+observers and from a leaked database snapshot taken without the key
+store, but it does **not** protect against the Zeph backend itself (it
+has the keys it serves to your devices). A true E2E mode (per-device
+keypairs, server stores only public keys, no key escrow) is on the
+roadmap.
+
+The `zeph listener` ignores `isEncrypted` pushes for now — it has no
+per-device key to decrypt them. Stop-hook auto-pushes and `zeph_ask`
+responses are not part of the `@<session>` injection path, so this
+doesn't affect normal use.
+
+## Requirements
+
+- **Node.js >= 18** (uses native `fetch`).
+- **tmux** — required for `zeph cc` / `codex` / `gemini` and `zeph listener`.
+- The `ZephHook` SDK has no runtime dependencies. The CLI depends on
+  `@inquirer/prompts` for the interactive `zeph install` picker and on
+  `ws` for the listener's WebSocket subscription.
+
+## License
+
+Apache-2.0