@agentvault/secure-channel 0.5.0 → 0.5.1

package/README.md

@@ -2,28 +2,21 @@
 
 End-to-end encrypted communication channel for AI agents on the [AgentVault](https://agentvault.chat) platform. Connect your agent to its owner with XChaCha20-Poly1305 encryption and Double Ratchet forward secrecy.
 
-## What's New in v0.4.0
+## What's New in v0.5.0
 
-**Webhook Notifications** — Your agent can now receive HTTP webhook callbacks when a new message arrives, even when it's not connected via WebSocket. This is ideal for serverless agents, agents that poll on a schedule, or any agent that isn't always online.
+**Desktop Notifications** — Incoming messages now trigger native OS notifications (macOS Notification Center, Windows Toast, Linux notify-send) when using the CLI. Enabled by default — disable with `--no-notifications`.
 
-### Upgrading from v0.3.x
+**Webhook URL CLI Flag** (v0.4.4) — `--webhook-url` flag and `AGENTVAULT_WEBHOOK_URL` env var for programmatic webhook registration.
 
-```bash
-npm install @agentvault/secure-channel@latest
-```
+**Webhook Notifications** (v0.4.0) — HTTP webhook callbacks when a new message arrives, even when not connected via WebSocket.
 
-Add `webhookUrl` to your config to enable:
+### Upgrading
 
-```js
-const channel = new SecureChannel({
-  inviteToken: "your-token",
-  dataDir: "./agentvault-data",
-  apiUrl: "https://api.agentvault.chat",
-  webhookUrl: "https://your-server.com/webhook/agentvault", // NEW in 0.4.0
-});
+```bash
+npm install @agentvault/secure-channel@latest
 ```
 
-No other code changes required — fully backward-compatible.
+No code changes required — fully backward-compatible.
 
 ---
 
@@ -58,8 +51,10 @@ The CLI will:
 | `--name` | `"CLI Agent"` | Agent display name |
 | `--data-dir` | `./agentvault-data` | Directory for persistent state |
 | `--api-url` | `https://api.agentvault.chat` | API endpoint |
+| `--webhook-url` | (none) | URL for HTTP webhook notifications |
+| `--no-notifications` | (notifications on) | Disable OS desktop notifications |
 
-Environment variables (`AGENTVAULT_INVITE_TOKEN`, `AGENTVAULT_AGENT_NAME`, `AGENTVAULT_DATA_DIR`, `AGENTVAULT_API_URL`) work as alternatives to flags.
+Environment variables (`AGENTVAULT_INVITE_TOKEN`, `AGENTVAULT_AGENT_NAME`, `AGENTVAULT_DATA_DIR`, `AGENTVAULT_API_URL`, `AGENTVAULT_WEBHOOK_URL`, `AGENTVAULT_NO_NOTIFICATIONS`) work as alternatives to flags.
 
 ### Option 2: SDK (Programmatic)
 
@@ -216,6 +211,32 @@ AgentVault supports multiple owner devices (e.g., desktop + mobile). The channel
 
 No additional configuration needed — multi-device is handled transparently.
 
+## Running as a Service
+
+The agent process must stay running to receive messages and desktop notifications. Use [pm2](https://pm2.keymetrics.io/) to keep it alive:
+
+```bash
+# Install pm2 globally
+npm install -g pm2
+
+# Start your agent as a background service
+pm2 start npx --name "my-agent" -- @agentvault/secure-channel \
+  --token=YOUR_TOKEN --name="My Agent"
+
+# View logs
+pm2 logs my-agent
+
+# Auto-restart on crash
+pm2 save
+
+# Stop the agent
+pm2 stop my-agent
+```
+
+pm2 keeps the process running if the terminal closes and auto-restarts on crashes. Desktop notifications continue to work as long as pm2 was started from your desktop session.
+
+For headless servers (no desktop), use `--no-notifications` and configure `--webhook-url` instead.
+
 ## Security
 
 - **XChaCha20-Poly1305** symmetric encryption (192-bit nonces)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentvault/secure-channel",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",