🚨 EMERGENCY CONTEXT BRIEF

Atlas Infrastructure Brief

Share this page with any AI assistant (Kodee, Claude, ChatGPT, etc.) when you need help with John's Atlas/Cooper setup. It contains full context on the architecture, services, and relationships so you don't have to re-explain everything.

📍 Location: hub.highside-re.com/emergency-context.html  |  Also saved at: /data/.openclaw/workspace/hub/emergency-context.html

Who Is John Atlas (Main AI) Infrastructure Cooper Platform Cooper Agents Fixing Atlas If Down Key Commands Standing Rules

👤 Who Is John Burns

Full nameJohn Burns LocationAustin, TX — Central Time Primary businessCommercial real estate development CompanyHighside Real Estate (HSRE) EntitiesHSRE, BBM 2025 LLC, JAK Development Group Phone512.633.1008 Primary AI contactTelegram (preferred) + web UI at 18789 NoteJohn IS an attorney — never suggest he hire one for legal review

🏗️ Atlas — John's Personal AI Agent

Atlas is John's primary AI agent. It runs inside a Docker container on a Hostinger VPS, powered by OpenClaw (an open-source AI agent framework). Atlas handles email, document creation, deal analysis, project management, and also manages the Cooper platform.

Agent nameAtlas Telegram bot@atlas_hsre_vps_bot Bot token prefix8637904053:AAFMHOS1... (current as of Apr 10 2026) Web UIhttp://127.0.0.1:18789 (local only) | external via Traefik proxy FrameworkOpenClaw v2026.4.9 AI modelClaude Sonnet (Anthropic) via Nexos Workspace/data/.openclaw/workspace/ (inside container) Memory filesMEMORY.md, memory/YYYY-MM-DD.md
⚠️ Telegram inbound rule (CRITICAL): OpenClaw's built-in Telegram plugin handles BOTH inbound and outbound. atlas-telegram PM2 process on the host must stay STOPPED. If both run simultaneously → 409 conflict loop → gateway crash.

🖥️ Infrastructure Overview

VPS (Primary Host)

ProviderHostinger KVM4 VPS — NOT managed OpenClaw — self-managed IP187.124.249.45 SSHssh -i /data/.ssh/id_ed25519 root@187.124.249.45 OSUbuntu Linux Disk193GB total | ~35GB used | healthy RAM15.6GB total | typically ~640MB used by OpenClaw BackupsDaily Hostinger backups, 30-min restore, US location

Docker Setup

Container nameopenclaw-om5j-openclaw-1 Imageghcr.io/hostinger/hvps-openclaw:latest Compose file/docker/openclaw-om5j/docker-compose.yml Data mount/docker/openclaw-om5j/data/data inside container Workspace mount/data/.openclaw/workspace → same inside container Config file/docker/openclaw-om5j/data/.openclaw/openclaw.json (+ .bak through .bak.4) Gateway port18789 (internal) | external via Traefik on port 56274
⚠️ Config revert trap: OpenClaw saves config to openclaw.json AND rotates backups (.bak through .bak.4). If you only fix openclaw.json and the gateway restarts, it may restore an old .bak. Always fix ALL 6 files via SSH, OR use openclaw config set <key> <value> (hot reload — preferred).

Host PM2 Processes (on VPS, not in container)

ProcessStatusPurpose
cooper-telegram-multibotONLINE ✅15 Cooper agent bots (Telegram)
cooper-email-pollerONLINE ✅Polls jburns@highside-re.com for inbound emails
atlas-watchdogONLINE ✅Watchdog for PM2 processes
cooper-oauth-callbackONLINE ✅Google OAuth callback handler
cooper-sms-handlerONLINE ✅Twilio SMS bridge
atlas-telegramSTOPPED ⛔MUST stay stopped — conflicts with OpenClaw

Cloudflare

Accountjohn.bunrs@gmail.com | Account ID: 101074ef1857ad52fc4026209cf8c3f1 Domainsmeetcooper.ai, meetcooper.com, highside-re.com Pages projectshsre-hub (hub.highside-re.com), cooper-ai (meetcooper.ai) Deploy tokencfut_OVzINyK8IuxlAYKtmhJBz5QsQPZT5PpsNF76TxGjca504f1c Workers KVCross-platform memory sync for all Cooper agents

Email (Microsoft 365)

Primaryjburns@highside-re.com (John) | atlas@highside-re.com (Atlas outbound) Cooper supportsupport@highside-re.com → routed to Atlas + John Agent mailboxesrex@, nash@, finn@, delilah@, bibby@, etc. @agent.highside-re.com Graph API creds/data/.openclaw/workspace/credentials/msgraph.json

🐾 The Cooper Platform

Cooper is an AI concierge service that John built and operates. It gives each client their own personal AI agent with a unique name and personality. Cooper agents communicate via Telegram (each has their own bot), email, and a web chat at meetcooper.ai.

Websitemeetcooper.ai Legal entityHighside Real Estate, LLC (John + Kent McNeil) Chat APIhttps://meetcooper.ai/api/chat (POST) AuthMagic link (Cloudflare KV-backed), 30-day sessions Agent config/data/.openclaw/workspace/clients/registry.json Bot config/data/.openclaw/workspace/credentials/telegram-bots.json Core script/data/.openclaw/workspace/scripts/cooper-telegram-handler-multibot.py AI engine/data/.openclaw/workspace/scripts/cooper-ai-engine.py Workspace cmds/data/.openclaw/workspace/scripts/workspace_commands.py (doc creation, email, etc.)

Relationship: Atlas ↔ Cooper

Atlas (John's personal agent) builds and maintains Cooper. Atlas also has its own Cooper agent called "Ace" (for John's personal use as a Cooper client). The Cooper agents (Rex, Finn, etc.) are separate Python processes running on the VPS host — they do NOT run inside the OpenClaw container. Atlas manages them via SSH.

🤖 Cooper Agents (15 total)

AgentClientTelegram BotTier
RexKent McNeil@Rex_Cooper_botProfessional
NashAndy Heard@Nash_Cooper_botProfessional
FinnJeff Turnas@Finn_Cooper_botProfessional
MaverickChase Belew@Maverick_Cooper_botProfessional
RyderMichael Broyles@Ryder_Cooper_botProfessional
RamseyJack Irvine@Ramsey_Cooper_botTrial
WaylonJosh Lackie@Waylon_Cooper_botTrial
RickyWill Ambruzs@Ricky_Cooper_botTrial
DelilahCharlotte Burns@Delilah_Cooper_botPersonal
BibbyJohn Burns IV@Bibby_Cooper_botPersonal
TuckerBrinley Burns@Tucker_Cooper_botPersonal
LucyKylie Calvert@Lucy_Cooper_botPersonal
HoneyStacy Burns@honey_cooper_botPersonal
CharlotteJackson Miller@charlotte_cooperbotProfessional
AceJohn Burns (personal)@ace_cooper_botProfessional

🔧 Fixing Atlas If It Goes Down

Use these steps in order. Each step fixes the most common failure mode.

Step 1 — Check if container is running

ssh root@187.124.249.45
docker ps | grep openclaw

If not running: cd /docker/openclaw-om5j && docker-compose up -d

Step 2 — Check Telegram token (most common crash cause)

ssh root@187.124.249.45
python3 -c "import json; d=json.load(open('/docker/openclaw-om5j/data/.openclaw/openclaw.json')); print(d['channels']['telegram']['botToken'])"

If token is wrong (ends in jEqu6m3NvVyI = OLD/bad), fix it:

# Fix all config files with correct token (replace TOKEN with the real one from BotFather)
TOKEN="8637904053:AAFMHOS1T31WM3NWQ-eWDKyYOlBEahubyGA"
for f in /docker/openclaw-om5j/data/.openclaw/openclaw.json{,.bak,.bak.1,.bak.2,.bak.3,.bak.4}; do
  python3 -c "import json; d=json.load(open('$f')); d['channels']['telegram']['botToken']='$TOKEN'; json.dump(d,open('$f','w'),indent=2)" 2>/dev/null && echo "Fixed $f"
done
# Then recreate container to load fresh config:
cd /docker/openclaw-om5j && docker-compose down && docker-compose up -d

Step 3 — Check atlas-telegram is STOPPED (conflict killer)

ssh root@187.124.249.45 "pm2 list | grep atlas-telegram"
# If status shows 'online' — STOP IT immediately:
ssh root@187.124.249.45 "pm2 stop atlas-telegram && pm2 save"

Step 4 — Check Cooper multibot is running

ssh root@187.124.249.45 "pm2 list"
# Should show: cooper-telegram-multibot ONLINE, cooper-email-poller ONLINE
# If multibot is down:
ssh root@187.124.249.45 "pm2 restart cooper-telegram-multibot"

Step 5 — Verify Telegram token is valid

curl "https://api.telegram.org/bot8637904053:AAFMHOS1T31WM3NWQ-eWDKyYOlBEahubyGA/getMe"
# Should return: {"ok":true,"result":{"username":"atlas_hsre_vps_bot",...}}

Step 6 — Run OpenClaw doctor

ssh root@187.124.249.45 "docker exec openclaw-om5j-openclaw-1 openclaw doctor --non-interactive"
# Look for: Telegram: ok (@atlas_hsre_vps_bot)
⚠️ DO NOT use docker restart mid-session — it kills the OpenClaw gateway while it's talking to you, causing a crash loop. Use docker-compose down && docker-compose up -d instead (clean stop + start).

⌨️ Key Commands Reference

SSH to VPS

ssh -i /data/.ssh/id_ed25519 -o StrictHostKeyChecking=no root@187.124.249.45

Container logs (live)

ssh root@187.124.249.45 "docker logs openclaw-om5j-openclaw-1 --tail 50 -f"

Recreate container (clean restart)

ssh root@187.124.249.45 "cd /docker/openclaw-om5j && docker-compose down && docker-compose up -d"

Update Telegram token (hot reload — preferred)

# Inside the OpenClaw container (via web UI terminal or exec):
openclaw config set channels.telegram.botToken "NEW_TOKEN_HERE"
# Then fix all bak files on host too (see Step 2 above)

Check sessions.json size (should stay under 1MB)

wc -c /data/.openclaw/agents/main/sessions/sessions.json
python3 -c "import json; d=json.load(open('/data/.openclaw/agents/main/sessions/sessions.json')); print(len(d), 'sessions')"

Watch for container restart events

ssh root@187.124.249.45 "docker events --filter container=openclaw-om5j-openclaw-1"

📋 Standing Rules — DO NOT Violate

Last updated: April 10, 2026 — Auto-generated by Atlas 🏗️ | hub.highside-re.com/emergency-context.html