fix: honor whatsapp mediaMaxMb (#505) (thanks @koala73)

docs/gateway/configuration.md

@@ -265,7 +265,8 @@ For groups, use `whatsapp.groupPolicy` + `whatsapp.groupAllowFrom`.
   whatsapp: {
     dmPolicy: "pairing", // pairing | allowlist | open | disabled
     allowFrom: ["+15555550123", "+447700900123"],
-    textChunkLimit: 4000 // optional outbound chunk size (chars)
+    textChunkLimit: 4000, // optional outbound chunk size (chars)
+    mediaMaxMb: 50 // optional inbound media cap (MB)
   }
 }
 ```

docs/gateway/restart.md

@@ -1,174 +0,0 @@
-# Restarting the Clawdbot Gateway
-
-This guide covers how to properly restart the Clawdbot gateway service on different platforms.
-
-## Linux (systemd)
-
-The gateway runs as a systemd user service on Linux servers.
-
-### Quick Restart
-
-```bash
-systemctl --user restart clawdbot-gateway.service
-```
-
-### Full Reload (after code updates)
-
-When you update the codebase (git pull, rebase, etc.), follow these steps:
-
-```bash
-# 1. Stop the service
-systemctl --user stop clawdbot-gateway.service
-
-# 2. Kill any stray gateway processes
-pkill -f "gateway.*18789"
-
-# 3. Reload systemd configuration (if service file changed)
-systemctl --user daemon-reload
-
-# 4. Start the service
-systemctl --user start clawdbot-gateway.service
-
-# 5. Verify it's running
-systemctl --user status clawdbot-gateway.service
-```
-
-### Reinstall Service (after major updates)
-
-If the gateway command changed or you're having persistent issues:
-
-```bash
-# Uninstall old service
-pnpm clawdbot daemon uninstall
-
-# Reinstall with latest configuration
-pnpm clawdbot daemon install
-
-# Reload and start
-systemctl --user daemon-reload
-systemctl --user start clawdbot-gateway.service
-```
-
-### Check Logs
-
-```bash
-# Follow live logs
-journalctl --user -u clawdbot-gateway.service -f
-
-# View recent logs
-journalctl --user -u clawdbot-gateway.service -n 50
-
-# View logs since last boot
-journalctl --user -u clawdbot-gateway.service --boot
-```
-
-### Common Issues
-
-**Port already in use:**
-```bash
-# Find process using port 18789
-lsof -i :18789
-
-# Kill specific process
-kill -9 <PID>
-```
-
-**Service keeps restarting:**
-```bash
-# Check for error details
-journalctl --user -u clawdbot-gateway.service --since "5 minutes ago" | grep -i error
-
-# Verify service file is correct
-cat ~/.config/systemd/user/clawdbot-gateway.service
-```
-
-## macOS (launchd)
-
-Use the macOS menu app or restart script:
-
-```bash
-./scripts/restart-mac.sh
-```
-
-Or manually:
-
-```bash
-# Stop service
-launchctl unload ~/Library/LaunchAgents/dev.steipete.clawdbot.gateway.plist
-
-# Start service
-launchctl load ~/Library/LaunchAgents/dev.steipete.clawdbot.gateway.plist
-```
-
-## Using Clawdbot CLI
-
-Cross-platform daemon management:
-
-```bash
-# Stop gateway
-pnpm clawdbot daemon stop
-
-# Start gateway
-pnpm clawdbot daemon start
-
-# Check status
-pnpm clawdbot daemon status
-```
-
-## After Configuration Changes
-
-After modifying `~/.clawdbot/clawdbot.json` or auth profiles:
-
-```bash
-# Restart to reload configuration
-systemctl --user restart clawdbot-gateway.service
-
-# Or use CLI
-pnpm clawdbot daemon stop && pnpm clawdbot daemon start
-```
-
-The gateway will automatically reload:
-- Auth profiles
-- Model fallback configuration
-- Gateway settings (port, bind, etc.)
-- Provider configurations
-
-## Verifying Gateway Health
-
-```bash
-# Check gateway is responding
-pnpm clawdbot health
-
-# List auth providers
-pnpm clawdbot providers list
-
-# Test agent connection
-pnpm clawdbot agent --message "hello" --local
-```
-
-## Troubleshooting
-
-**Gateway won't start:**
-1. Check for port conflicts: `lsof -i :18789`
-2. Verify configuration: `pnpm clawdbot doctor`
-3. Check logs for errors
-4. Try reinstalling the service
-
-**Changes not taking effect:**
-- Configuration changes require restart
-- Code changes require rebuild: `pnpm build`
-- Service file changes require daemon-reload
-
-**Multiple gateways running:**
-```bash
-# List all gateway processes
-ps aux | grep gateway
-
-# Kill all gateway processes
-pkill -f "gateway.*18789"
-
-# Clean start
-systemctl --user stop clawdbot-gateway.service
-pkill -f "gateway.*18789"
-systemctl --user start clawdbot-gateway.service
-```

docs/providers/whatsapp.md

@@ -151,7 +151,8 @@ Behavior:
 
 ## Limits
 - Outbound text is chunked to `whatsapp.textChunkLimit` (default 4000).
-- Media items are capped by `agents.defaults.mediaMaxMb` (default 5 MB).
+- Inbound media saves are capped by `whatsapp.mediaMaxMb` (default 50 MB).
+- Outbound media items are capped by `agents.defaults.mediaMaxMb` (default 5 MB).
 
 ## Outbound send (text + media)
 - Uses active web listener; error if gateway not running.
@@ -166,7 +167,7 @@ Behavior:
     - Gateway: `send` params include `gifPlayback: true`
 
 ## Media limits + optimization
-- Default cap: 5 MB (per media item).
+- Default outbound cap: 5 MB (per media item).
 - Override: `agents.defaults.mediaMaxMb`.
 - Images are auto-optimized to JPEG under cap (resize + quality sweep).
 - Oversize media => error; media reply falls back to text warning.
@@ -187,7 +188,9 @@ Behavior:
 - `whatsapp.dmPolicy` (DM policy: pairing/allowlist/open/disabled).
 - `whatsapp.selfChatMode` (same-phone setup; suppress pairing replies for outbound DMs).
 - `whatsapp.allowFrom` (DM allowlist).
+- `whatsapp.mediaMaxMb` (inbound media save cap).
 - `whatsapp.accounts.<accountId>.*` (per-account settings + optional `authDir`).
+- `whatsapp.accounts.<accountId>.mediaMaxMb` (per-account inbound media cap).
 - `whatsapp.groupAllowFrom` (group sender allowlist).
 - `whatsapp.groupPolicy` (group policy).
 - `whatsapp.groups` (group allowlist + mention gating defaults; use `"*"` to allow all)