DEV Community

Cover image for CLI Notification Setup: Configure Push Alerts for Your Self-Hosted AI Wallet
Wallet Guy
Wallet Guy

Posted on

CLI Notification Setup: Configure Push Alerts for Your Self-Hosted AI Wallet

#selfhosted #cli #ai #opensource

CLI notification setup is critical for monitoring your self-hosted AI wallet infrastructure, but most developers skip this step until their first unmonitored transaction goes wrong. Setting up push alerts, Telegram notifications, and WalletConnect approvals through WAIaaS CLI ensures you maintain control over your agent's financial operations without relying on third-party services. Your keys, your server, your notification pipeline.

Why Notification Setup Matters for Self-Hosters

When you're running AI agents with real funds, silent failures aren't just bugs—they're financial risks. Unlike hosted wallet services that handle monitoring for you, self-hosted infrastructure puts you in control of every alert, approval, and security checkpoint. This means configuring notification channels before your agents start executing transactions, not after something goes wrong.

The stakes are straightforward: an unmonitored agent could drain funds through policy violations, failed transactions could leave positions open to liquidation, and manual approvals could timeout without human intervention. Self-hosted notification infrastructure solves this by routing alerts through channels you control—no third-party APIs, no rate limits, no external dependencies.

Setting Up Notification Channels

WAIaaS provides a unified CLI command for configuring all notification channels at once. The daemon supports 3 signing channels: push-relay-signing-channel, telegram-signing-channel, and wallet-notification-channel, each designed for different approval workflows.

Quick Notification Setup 

# Configure all notification channels in one command
waiaas notification setup --all

# Or configure specific channels
waiaas notification setup --push-relay --telegram --walletconnect
Enter fullscreen mode Exit fullscreen mode

The CLI will walk you through each channel configuration, generating the necessary API keys, webhook URLs, and connection tokens. Unlike hosted solutions, all notification routing happens within your infrastructure—the push relay runs in your Docker stack, Telegram bots use your bot tokens, and WalletConnect sessions connect directly to your daemon.

Docker Compose Notification Stack

The complete notification infrastructure deploys alongside your WAIaaS daemon:

services:
  daemon:
    image: ghcr.io/minhoyoo-iotrust/waiaas:latest
    container_name: waiaas-daemon
    ports:
      - "127.0.0.1:3100:3100"
    volumes:
      - waiaas-data:/data
    environment:
      - WAIAAS_DATA_DIR=/data
      - WAIAAS_DAEMON_HOSTNAME=0.0.0.0
    restart: unless-stopped

  push-relay:
    image: ghcr.io/minhoyoo-iotrust/waiaas:push-relay
    container_name: waiaas-push-relay
    environment:
      - PUSH_RELAY_PORT=3200
    depends_on:
      - daemon
    restart: unless-stopped
Enter fullscreen mode Exit fullscreen mode

This gives you 2 Docker images working together: the main WAIaaS daemon handling transactions and policies, plus a dedicated push-relay service for real-time notifications. Everything runs locally without external notification services.

Notification Channel Types

Push Relay for Real-Time Alerts

The push-relay-signing-channel handles instant notifications for policy violations, transaction approvals, and system alerts. It's particularly useful for monitoring agent behavior in development:

# Start daemon with push relay
docker compose up -d

# Test push notifications
curl -X POST http://127.0.0.1:3100/v1/transactions/send \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer wai_sess_<token>" \
  -d '{
    "type": "TRANSFER",
    "to": "test-address",
    "amount": "1000"
  }'
Enter fullscreen mode Exit fullscreen mode

If this transaction hits your SPENDING_LIMIT policy's NOTIFY tier, you'll receive a push notification with transaction details, policy evaluation, and approval options—all routed through your local push relay.

Telegram for Human Approvals

The telegram-signing-channel integrates with Telegram bots for transaction approvals. This is essential when your policies include APPROVAL tier transactions:

# Configure Telegram notifications
waiaas notification setup --telegram
# Follow prompts to create bot token and chat ID
Enter fullscreen mode Exit fullscreen mode

When an agent transaction requires human approval (hits the APPROVAL tier in your SPENDING_LIMIT policy), WAIaaS sends a Telegram message with transaction details and approval buttons. You approve or deny directly in Telegram, maintaining the human-in-the-loop security model while keeping everything under your control.

WalletConnect for Owner Authentication

The wallet-notification-channel handles WalletConnect integration for owner approval of agent transactions:

# Set up WalletConnect notifications
waiaas notification setup --walletconnect

# Check WalletConnect status
waiaas owner status
Enter fullscreen mode Exit fullscreen mode

This creates a WalletConnect session between your personal wallet and the WAIaaS daemon. When agent transactions need owner approval, your wallet app receives the signing request directly. No centralized WalletConnect relay—the connection runs through your daemon.

Policy-Driven Notification Triggers

Notifications trigger based on your policy configuration. The 4 security tiers (INSTANT, NOTIFY, DELAY, APPROVAL) determine when and how you receive alerts:

# Create a policy that triggers notifications
curl -X POST http://127.0.0.1:3100/v1/policies \
  -H "Content-Type: application/json" \
  -H "X-Master-Password: my-secret-password" \
  -d '{
    "walletId": "<wallet-uuid>",
    "type": "SPENDING_LIMIT",
    "rules": {
      "instant_max_usd": 10,
      "notify_max_usd": 100,
      "delay_max_usd": 1000,
      "delay_seconds": 300
    }
  }'
Enter fullscreen mode Exit fullscreen mode

With this policy:

  • Transactions ≤ $10: Execute silently (INSTANT)
  • Transactions ≤ $100: Execute + send notification (NOTIFY)
  • Transactions ≤ $1000: Queue for 5 minutes + notification with cancel option (DELAY)
  • Transactions > $1000: Block until human approval (APPROVAL)

Your notification channels receive different message types for each tier, letting you respond appropriately to each situation.

Integration with CLI Workflows

The CLI provides 20 commands for managing your notification infrastructure alongside wallet operations:

# Core notification commands
waiaas notification setup     # Configure notification channels
waiaas status                # Check daemon + notification status
waiaas owner connect         # Connect WalletConnect for approvals
waiaas owner disconnect      # Disconnect WalletConnect
waiaas owner status          # Check owner connection status

# Session management with notifications
waiaas session prompt        # Create session for AI agent
waiaas quickset --mode mainnet  # Create wallets + sessions + notifications
Enter fullscreen mode Exit fullscreen mode

The quickset command is particularly useful for self-hosters—it creates wallets, generates session tokens for your AI agents, configures MCP integration, and sets up notification channels in one step.

Monitoring and Alerting

Once notifications are configured, you can monitor your agent's financial activity in real-time:

# Check recent transactions
curl http://127.0.0.1:3100/v1/transactions \
  -H "Authorization: Bearer wai_sess_<token>"

# Monitor incoming deposits
curl http://127.0.0.1:3100/v1/incoming/summary \
  -H "Authorization: Bearer wai_sess_<token>"

# Check policy violations
curl http://127.0.0.1:3100/v1/policies \
  -H "X-Master-Password: my-secret-password"
Enter fullscreen mode Exit fullscreen mode

Your notification channels will alert you to policy violations, failed transactions, incoming deposits, and approval requests. The Admin Web UI at /admin provides a dashboard view of all this activity, but notifications ensure you catch issues even when you're not actively monitoring.

Quick Start: Complete Notification Setup

Here's the minimal path to get notifications working with your self-hosted WAIaaS instance:

  1. Start WAIaaS with Docker Compose: 
git clone https://github.com/minhoyoo-iotrust/WAIaaS.git
cd WAIaaS
docker compose up -d
Enter fullscreen mode Exit fullscreen mode
  1. Initialize and create wallet: 
npm install -g @waiaas/cli
waiaas init
waiaas start
waiaas quickset --mode mainnet
Enter fullscreen mode Exit fullscreen mode
  1. Configure notifications: 
waiaas notification setup --all
Enter fullscreen mode Exit fullscreen mode
  1. Test notification flow: 
# Create a policy that will trigger notifications
waiaas session prompt  # Get session token for testing
# Use the session token to make a test transaction that hits NOTIFY tier
Enter fullscreen mode Exit fullscreen mode
  1. Verify channels are working: 
waiaas status  # Should show notification channels as "connected"
Enter fullscreen mode Exit fullscreen mode

This gives you a complete self-hosted wallet infrastructure with real-time notifications, human approval workflows, and policy-based alerting—all running on your hardware with your API keys.

What's Next

Your self-hosted AI wallet infrastructure is now equipped with comprehensive notification monitoring. This foundation supports advanced workflows like automated DeFi strategies with human checkpoints, cross-chain bridging with approval gates, and multi-agent coordination with centralized oversight.

Ready to deploy your own notification-enabled AI wallet infrastructure? Clone the repository at https://github.com/minhoyoo-iotrust/WAIaaS and follow the quickstart guide at https://waiaas.ai to get your first agent wallet running with full notification coverage in under 10 minutes.

Top comments (0)