clawd/2026-03-17.md at d86ffffef3afc67bf0b0d13badbaf9b4dad51adb

Mira Discord Bot — Created & Live (Mar 17)

Mac SSH: johanjongsma@192.168.1.14 (key: ~/.ssh/id_ed25519)
OC browser profile "user": driver=existing-session, attachOnly=true
alias chrome-debug on Mac: launches Chrome with --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0
Dock app: ~/Applications/ChromeDebug.app (compiled AppleScript)
Note: Chrome must be launched fresh (not existing instance) for debug port to bind

MC webhook → OC /hooks/messages → mail agent (agentId: mail)
Junk filter prompt: default=PASS, government/official bodies always pass
Removed Kaseya rules from both junk prompt and routing guide
MijnOverheid (Belastingdienst) emails restored to inbox — 2 tax documents pending

MC webhook → OC /hooks/messages → agentId: mail (was missing agentId, now fixed)
Junk filter rules: removed Kaseya-specific rules entirely
Routing rules: "default=PASS" principle added — never archive what you can't confirm is noise
Government/official bodies (Belastingdienst, MijnOverheid) always pass — legal consequences
Two MijnOverheid Belastingdienst emails restored to inbox (Feb 20, Mar 13) — TAX DOCS, Johan must check
208 messages archived from inboxes (tj@ and johan@) since Feb 15
Pipeline verified working end-to-end

Openprovider URGENT Suspension — needs immediate attention
Chase Prime Visa — payment was due Mar 7 (possibly overdue)
Health Link invoice #000061 — $216.90 Sophia blood draw, unpaid, multiple reminders
National Visa Center — immigration reinstatement notice
Venmo $480 outstanding from Diane Murray
Jonathan Hayden — replied to MRI analysis (real human, in inbox)
Macy's statement acct 8097 Feb 26

johanjongsma@192.168.1.14 (key: ~/.ssh/id_ed25519 from forge)
Mac username is johanjongsma (NOT johan — wasted time on wrong username earlier)
SSH enabled via System Settings → General → Sharing → Remote Login
PubkeyAuthentication needed explicit yes in sshd_config

Working command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0
Alias chrome-debug added to ~/.zshrc on Mac
Dock app: ~/Applications/ChromeDebug.app (AppleScript compiled via osacompile — must run in GUI session, not SSH)
OC browser profile "user": driver=existing-session, attachOnly=true, color=#00AA00
cdpUrl was initially set to 127.0.0.1:19222 (SSH tunnel) — corrected to 192.168.1.14:9222 (direct LAN)
Chrome must be launched fresh (kill existing instance first) for debug port to actually bind
--remote-debugging-address=0.0.0.0 required or Chrome only binds to localhost

Created via browser automation (headless OC browser + Johan clicking CAPTCHA)
App ID: 1483483480435458240 | Bot: Mira#7065
Token: MTQ4MzQ4MzQ4MDQzNTQ1ODI0MA.G9zfbb.m9MdxDSgGnGJYz4i4oiR_3FZb8D4FCOK0oFXMo
Guild: vault1984 (1478270766007976009) — added via OAuth2 authorize flow
Intents: all three privileged intents enabled (Presence, Server Members, Message Content)
OC config: channels.discord.accounts.mira, workspace /home/johan/mira
ONLINE as of 12:39 PM ET Mar 17
Error 4014 was the blocker — intents were set via application flags API but NOT in the bot portal UI (separate thing)

profile="user" with driver="existing-session" = Chrome MCP attach, no debug port needed in theory
BUT in practice needs Chrome running with --remote-debugging-port on the same machine as gateway
Gateway is on forge (Linux), Chrome is on Mac — so remote CDP required
Remote CDP profile: cdpUrl pointing at Mac's IP:9222
existing-session driver does NOT accept userDataDir key (config validation error)
SSH tunnel approach works but unnecessary — direct LAN is cleaner

Johan needs to check MijnOverheid for Belastingdienst tax documents
Openprovider suspension needs immediate attention
Chase payment may be overdue
Mac Chrome needs to be re-launched with debug flags for browser automation to work again

Root cause: Missing entry in bindings[] array in openclaw.json
George/Iaso had explicit bindings {agentId: "george", match: {channel: "discord", accountId: "george"}}
Mira only had a telegram binding — Discord messages were never routed to her agent
Fix: Added {agentId: "mira", match: {channel: "discord", accountId: "mira"}} to bindings[]
Also: new bot token issued by Johan (old one may have been compromised/expired)
New token: MTQ4MzQ4MzQ4MDQzNTQ1ODI0MA.GYcXfM.oqWv6C_R2TRNtAZ61fZRAZPtg30L2olIk7zQ_8
Lesson: When adding a new Discord bot account, ALWAYS add a binding entry — account name matching agent ID is NOT sufficient